Demo
Self-healing test locators
A UI update breaks a locator and the test fails for the wrong reason. Paste the old locator and the current HTML, and get a replacement with a confidence score.
Demo - live AI, real open-source project
A UI update broke your locator. Paste the old locator and a snippet of the page's current HTML, and the AI proposes a replacement with a confidence score. This calls a real model, not a script.
Inputs are logged to improve this demo. Do not paste secrets, customer data or confidential code.
Self-healing runs inside the open-source framework in CI, where the healed locator is applied and the test is re-run. This page shows the AI step on its own. View the framework on GitHub.
We checked every suggestion in a real browser
We wrote 12 broken-locator cases with page HTML. For 10 of them a correct element exists; for 2 there is nothing to heal to. Each suggested locator was run in headless Chrome to confirm it finds the right element, instead of taking the AI's word for it.
The cases are hand-written, so this is an early test, not proof. In a real suite, the healed locator should still be reviewed and the test re-run, which is what the open-source framework does.
Related reading
About this demo
What this demo shows
This demo fixes one of the most common reasons UI tests fail: a locator that no longer matches the page after a design change. You paste the old Selenium, Cypress or Playwright locator and the page's current HTML. A live AI looks for the element the locator was meant to find and proposes a replacement, with a confidence score and a short explanation.
How it works
- Step 1Paste the broken locator, or use the sample.
- Step 2Paste the current HTML of the page, or the part around the element.
- Step 3The AI compares the old locator with the new markup and finds the closest match.
- Step 4You get a replacement locator, a confidence score and a short explanation.
- Step 5A person reviews the suggestion before it goes into the test suite.
Who it is for
It is for QA and automation engineers maintaining large UI suites, where small front-end changes break dozens of tests that are not really failing.
About the data
The sample locator and HTML are made up for the demo. The AI call is live, and inputs are kept in a private sheet so we can improve the demo. Do not paste secrets or customer data.
Questions
Does it change my tests automatically?
No. It suggests a replacement with a confidence score, and a person decides whether to use it.
Which frameworks does it support?
It accepts locators written for Selenium, Cypress or Playwright. Paste the locator the way it appears in your test.
What does the confidence score mean?
It is the AI's estimate of how sure it is that the new locator points to the same element. Low scores deserve a closer look.
Next step
Want this running on your test suite?
A 20-minute call is enough to know if we can help. No pitch deck, no pressure.