When a target moves, Zerocheck resolves it again from the step description and records the change. A heal is saved only after the full test passes with independent evidence.
Old and new targets are recorded
The original outcome stays unchanged
Saved heals need independent evidence
A changed locator does not always mean changed behavior.
A replacement target must preserve the intended interaction.
A passing outcome needs evidence beyond a plausible match.
A layout refactor breaks a stored target. Someone updates it without being able to see whether the test still exercises the same action.
The run records the old target, replacement, reason and validation state. If the required evidence is missing, the repair stays pending; failed tests do not save it as verified.
Describe the intended control and a specific observable outcome.
Run the saved test as the UI changes.
Inspect healing history alongside the step screenshots.
Review changed product behavior separately; a renamed control is not treated as the same target.
Paste your QA checklist. Zerocheck drafts editable browser tests, runs them in your app, and shows the result of each item before you save it.
Zerocheck keeps the exact test revision, step screenshots, errors and attempts together so an engineer can explain a browser test result.
Start with a browser test in the web app, then use the optional CLI to run repository YAML in GitHub Actions and post a result on the pull request.
An assertion failure remains a failure. A heal is saved only when the complete unchanged test passes with independent evidence for the target, action and outcome.
There is no automatic confirmation rerun. Validation uses evidence from the complete passing test; insufficient evidence leaves the repair pending.
When a target moves, Zerocheck resolves it again from the step description and records the change. A heal is saved only after the full test passes with independent evidence.
Get a demo