Browser Automation and Selectors That Last
Good selectors describe what a person is trying to use. Build browser workflows around meaning, clear scope, and evidence that the intended action worked.
Read the guideFIELD NOTES / TOPIC
Selectors, in practice.
Read focused selectors articles and connect the ideas to the rest of your tools API workflow.
A selector expresses which interface element a workflow intends to use. Good selection makes that intent understandable and keeps repeated controls from becoming ambiguous targets. A maintained semantic identity or test hook can be more useful than a long path through incidental layout.
Read the related guide for concrete locator decisions, then apply the selector checklist in your own interface. Inspect how many elements match, scope the target to the intended region, and verify the outcome after the action. When the application changes, fix the assumption behind the locator instead of simply choosing a different matching position. Review question: Does the locator identify the intended control for a meaningful reason, and what would happen if a second matching control appeared?