Broken locator? Find the intended element instead of losing the test immediately.
TestZombie evaluates more than a new CSS or XPath string. It considers the context of the expected element across Selenium, Playwright and Appium.
Locator drift is maintenance, not a product failure
When an ID, label, structure or attribute changes, the user flow may still work while the automation turns red.
Multiple signals
Attributes, text, roles, hierarchy and other element characteristics can be evaluated together.
Confidence instead of guesswork
Healing is used only when a candidate can be assessed with sufficient confidence.
Permanent fix
Successful healing remains visible and can be applied back to the test code.
How locator healing works
Original locator fails
The known selector no longer returns a suitable element.
Compare candidates
TestZombie searches possible targets and scores their match to the expected element.
Use the strongest candidate
The most robust match can recover the run and is recorded in the healing log.
Locator healing FAQ
Which locator types can be affected?
Typical cases include IDs, CSS, XPath, roles, labels, text or mobile accessibility attributes.
Is every candidate automatically safe?
No. Healing should only be applied with sufficient confidence; otherwise the failure remains visible.
Can I review the healing later?
Yes. A central healing history keeps the cause, replacement and result traceable.
Your tests should survive change.
Add healing, analysis and actionable fix recommendations to existing Selenium, Playwright and Appium tests.