What is self-healing tests?
Self-healing tests automatically repair broken element locators when the user interface changes, instead of failing.
Most UI test failures after a redesign are not bugs. A button moved, a class name changed or a label was reworded, and the test can no longer find the element. Self-healing tools detect this, find the intended element using other signals and update the locator.
Good self-healing proposes the change as a reviewable diff and distinguishes a moved element from a missing one. Silently passing a test whose target has genuinely disappeared would hide a real bug.
Example
A designer renames the Checkout button to Continue to payment. The self-healing engine matches it by role and position, updates the locator and opens a diff for review.
Best practices
- Prefer stable locators such as roles and labels
- Review healed changes rather than accepting them silently
- Fail when the intended element is truly gone
- Track how often tests heal to spot unstable areas
Ship without fear.
Start testing free in minutes, or let a QAShift engineer deliver your first morning report within 5 days.