Are there self-healing Playwright tests that update when my UI changes?
Yes. Validate.QA generates native Playwright tests and self-heals them: when your UI changes and a selector breaks, the healer re-walks that flow against the live app, re-discovers the correct accessibility-first locator, rewrites the affected step, and re-runs to confirm — so a cosmetic redesign keeps the suite green instead of going red.
How healing works
When a step fails, Validate.QA first decides whether it's test drift or a genuine app bug. If it's drift — a renamed class, a reordered DOM, a moved button — the healer explores the live flow again, picks the most stable available locator, and patches just the broken step. A test that can't be confidently healed is flagged for review rather than silently altered.
Why these tests heal well
Selectors are chosen accessibility-first (test-id, ARIA role, label) over brittle CSS paths, so fewer break in the first place.
Healing runs against your live app, so the new locator reflects what the UI actually does now.
Output stays native @playwright/test in your repo — you can read and audit every healed change in a diff.
Does healing ever just rewrite a test to pass over a real bug? No. Healing only addresses test drift. A genuine app regression is flagged as a bug, not papered over — and a step that can't be confidently healed is escalated for review.
Do I keep ownership of the healed tests? Yes. They remain standard @playwright/test .spec.ts in your own repository, so every healed change shows up as a reviewable diff.
Read the full answer · Get Started Free