Locator Health: see which locators are brittle
Tags: locator health, locators, self-healing, fallback, xpath, css, flaky tests, maintenance
Pages change. WebSureQTool handles it deterministically, without guessing. FALLBACK, NOT GUESSING Scanned steps carry the locators WebSureQTool recorded for the element: the CSS selector first and its XPath as a fallback. If the CSS selector stops matching, the run tries the recorded XPath, logs that it did, and continues. If no recorded locator matches, the step fails at that exact point with the locator and full evidence, so you re-scan the page and update the step deliberately. WebSureQTool never invents a locator and never rewrites your suite on its own. LOCATOR HEALTH (Pro) Tools > Locator Health... shows every locator your runs used, with uses, successes, failures and heals (times a fallback matched). Locators that keep failing or keep needing their fallback rise to the top, so you fix brittle areas before they break a release. Ranked multi-locator healing with an audit ledger is on the roadmap.
Need the detailed workflow?
The public guide stays intentionally high level. Open the Intelligent Assistant for click-by-click instructions, learning order, and practice ideas.
Open Assistant
