Use IDs in Selenium Tests When Possible
Bug #1353628 reported by
Michael Jackson
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Wishlist
|
Martin Pavlásek |
Bug Description
IDs are typically the most stable and fastest locators when using Selenium. The current Selenium integration tests are using CSS locators, even when unique IDs are available. We should consider using IDs as the standard, and switching the current CSS locators to IDs where possible. We may also consider adding IDs to the templates where it makes sense to help facilitate this in the testing.
Changed in horizon: | |
assignee: | nobody → Michael Jackson (rebelagentm) |
tags: |
added: integration-tests removed: integration-test |
Changed in horizon: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Sounds like a reasonable change. Since id's must be unique, it may require some care in order to ensure that re-usable components generate unique ids.