+ Start a Discussion

How to handle non-Visualforce field ids in Selenium tests?

This old post Selenium Testing Best Practices describes the problem that the id values generated by the Force.com platform on default (layout-based) UI fields vary between orgs. So the normal practice of using field ids to match page elements to stop Selenium tests being fragile (when elements are added or removed) looks impractical unless you can guarantee to only ever need to test in one org.


Can anyone offer advice on how to work around this problem?