Martin Taylor (Inactive) added a comment - 31/May/12 12:08 PM 1) Test Harnesses Reviewing nexus and atlassian selenium test-harnesses for ideas/best practices: Nexus Good breakdown, has jmeter testing included https://github.com/sonatype/nexus/blob/master/nexus/nexus-test-harness/ Selenium xvfb-friendly selenium framework strong use of page objects, webdriverelements have implicit timeouttypes includes firefox/chrome instances that include in target/tmp directory, no need for selenium-server startup https://studio.atlassian.com/source/browse/SELENIUM Begin building out page object structure, abstract classes Need to determine if KRAD is good for page object. Much of the current testing is limited to isolated tests and wouldnt benefit from reuse that pageObjects provide (besides login) see if burpsuite can be used to create site map for page objects initial layout run some tests on atlassian to see if remotewebdriver can be used with it for saucelab testing see if we can integrate browsermob (again, RemoteWebDriver, needs a bit more research and talk to Matt) 2) Update to 2.21 selenium, add atlassian 2.1-m14 framework (waiting on 2.1 release) 3) Begin building out documentation on how to make sure your KRAD project can be made easier to test (use of id tags, etc..) start building page elements for different types of objects in KRAD (could help with reuse) figure out how to balance between developer/QA in testing process (developer to build the page object, QA to use it in their tests)

Jessica Coltrin (Inactive) added a comment - 16/Oct/12 10:57 PM moving non-blocker and non-critical m4 Jiras to 2.2-backlog

Erik Meade added a comment - 29/Nov/13 12:45 PM https://wiki.kuali.org/display/KULRICE/Selenium+Testing

Jessica Coltrin (Inactive) added a comment - 17/Feb/14 2:37 AM We have a test infrastructure in place using selenium for the automated functional tests (AFTs). Closing.