Use what a pull request changed to choose which browser tests to run. Your team picks the tests, and Zerocheck runs them.
An author changes an account-settings form and assumes the existing smoke suite covers it. A file diff alone doesn't capture every affected user outcome, and new behavior needs a new expectation even if existing tests pass.
So a reviewer identifies the changed outcome, runs the related saved tests and adds a new test if the checklist misses it. Zerocheck makes that quick to do, but the choice of tests stays with you.
Write down the user-visible behavior affected by the change.
Choose existing tests in the web app, or select YAML paths with the CLI.
Draft another test when the expected outcome is new.
Run the broader regression suite according to your 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 test, its step screenshots and its errors 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 a CI job and act on its exit code.
No. You select tests in the web app, or by file path with the CLI.
Describe the user flow and expected outcome, or paste checklist items. Zerocheck drafts and runs browser steps from that.
US$500 in credits at sign up, with a dedicated instance and hands-on onboarding.
Book a setup call