Zerocheck shows the failing step, screenshots and console errors. A pass after a transient retry stays labelled flaky.
A developer sees a red job, reruns it and loses the context needed to understand why it failed. A locator change, a failed assertion and a service error need different responses, and it's hard to tell them apart after the fact.
In Zerocheck, you open the run, look at the failing action and expected outcome, and compare the step screenshots. If a test only passed after a retry, it stays labelled flaky.
Read the failing step and the steps around it.
Check the screenshot, console output and failure type.
Fix the product, test data or test description based on what you find.
Use --fail-on-flaky in CI if a flaky blocking test should fail the job.
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. A temporary service error can be retried once. A failed check isn't retried.
No. It shows you failure details and what the browser saw. Engineers decide the cause and the fix.
US$500 in credits at sign up, with a dedicated instance and hands-on onboarding.
Book a setup call