Glossary
A self-healing test can recover a target after a UI change while preserving the original interaction and expected outcome. The category describes target maintenance, not permission to change the requirement.
A moved control can break a stored target without changing behavior. A plausible replacement can also be wrong. The useful question is whether the intended target, action and outcome remain demonstrably the same.
Teams use meaningful target descriptions, stable labels and explicit assertions. When evaluating healing, they inspect a harmless layout change separately from a changed requirement or real regression.
When a target moves, Zerocheck resolves it again from the step description and records the old target, new target, reason and validation state. A heal is saved only when the full unchanged test passes with independent evidence. Insufficient evidence leaves it pending; a failed test rejects its candidates.
A layout refactor can leave the target’s identity and user outcome unchanged. A renamed control or new flow may change that identity. In Zerocheck, the replacement must preserve the intended target and the full unchanged test must pass with independent evidence. There is no automatic full-test confirmation rerun.
Inspect the step, previous target, replacement target, reason and validation state alongside the screenshots. Pending means the required evidence is not sufficient to persist the repair as verified. A failed test rejects its healing candidates rather than turning the failed outcome into a pass.