[KULRICE-7298] Selenium Test Infrastructure Created: 15/May/12  Updated: 21/May/15  Resolved: 17/Feb/14

Status: Closed
Project: Kuali Rice Development
Component/s: Development, Testing
Affects Version/s: 2.2
Fix Version/s: Not version specific
Security Level: Public (Public: Anyone can view)

Type: Task Priority: Major
Reporter: Jerry Neal (Inactive) Assignee: Erik Meade
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
cloned from KULRICE-7208 Template Closed
Similar issues:
KULRICE-7302Selenium tests for Travel Maintenance Document
KULRICE-7152Selenium tests for Attribute Definition Lookup
KULRICE-13838KRAD Kitchen Sink Selenium Smoke tests
KULRICE-7681Selenium Test for sampleapp PeopleFlow
KULRICE-5613Integrate Selenium Tests into CI environment
KULRICE-13454Selenium test configurations
KULRICE-8150Upgrade Selenium 1 Smoke Tests to Selenium 2 (WebDriver)
KULRICE-8071Setup smoke tests for Selenium Grid
KULRICE-13101Test git with infrastructure
Rice Module:
KAI Review Status: Not Required
KTI Review Status: Not Required


Work on KRAD testing infrastructure using Selenium and Page Objects, including:

1) Creating test harnesses and other infrastructure
2) Bringing in necessary libraries
3) Documenting testing (setup, best practices, ...)

Comment by Martin Taylor (Inactive) [ 31/May/12 ]

1) Test Harnesses

  • Reviewing nexus and atlassian selenium test-harnesses for ideas/best practices:
  • 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)
Comment by Jessica Coltrin (Inactive) [ 16/Oct/12 ]

moving non-blocker and non-critical m4 Jiras to 2.2-backlog

Comment by Erik Meade [ 29/Nov/13 ]


Comment by Jessica Coltrin (Inactive) [ 17/Feb/14 ]

We have a test infrastructure in place using selenium for the automated functional tests (AFTs). Closing.

Generated at Thu Apr 02 13:36:37 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.