A layout change can break a target while leaving the user journey intact. Resolving that target again can save maintenance work. The risk is accepting a different control or a weaker outcome just to keep the test passing.
When evaluating healing, ask to inspect the original target, replacement, reason and evidence. Test a harmless layout change separately from a real product regression. A failed outcome should stay failed.
Zerocheck checks whether the target’s semantic identity is preserved. A moved control can be resolved again; a renamed control is not treated as the same target. The run exposes the change in healing history.
A heal is saved only when the complete unchanged test passes with independent evidence for the target, action and outcome. Missing evidence leaves it pending, and a failed test rejects its candidates. There is no automatic second full run to confirm the repair.
Your team still reviews the test’s intended outcome. Healing cannot make an irrelevant assertion useful.
Run your customer flows before merging, then inspect the failed step, screenshots and exact test revision.
Get a demo