Use the behavior changed by a pull request to choose browser tests. Zerocheck runs the tests you select; it does not infer coverage from the code diff.
Your team chooses the affected flows
Select saved tests or YAML paths
Add an assertion for new behavior
A file diff alone does not capture every affected user outcome.
A fast subset is useful only when the selection is appropriate.
New behavior needs a new expectation, even if existing tests pass.
The author changes an account-settings form and assumes the existing smoke suite covers it.
The reviewer identifies the changed outcome, runs the related saved tests and adds a new test when the checklist misses it.
Write down the user-visible behavior affected by the change.
Choose existing tests from the web app, or select YAML paths in the CLI.
Draft an additional test when the expected outcome is new.
Run the broader regression suite according to the team’s release policy.
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.
No. Selection is manual in the web app or by file path in the CLI.
Describe the user flow and expected outcome, or paste checklist items. Zerocheck drafts and runs browser steps for that input.
Use the behavior changed by a pull request to choose browser tests. Zerocheck runs the tests you select; it does not infer coverage from the code diff.
Get a demo