# See why a browser test failed before rerunning it

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.

## How to do it in Zerocheck

1. Read the failing step and the steps around it.
2. Check the screenshot, console output and failure type.
3. Fix the product, test data or test description based on what you find.
4. Use --fail-on-flaky in CI if a flaky blocking test should fail the job.

## Frequently asked questions

### Does Zerocheck rerun every failed test?

No. A temporary service error can be retried once. A failed check isn't retried.

### Does Zerocheck automatically classify every product bug?

No. It shows you failure details and what the browser saw. Engineers decide the cause and the fix.

---
Canonical: https://tryzerocheck.com/use-cases/flaky-test-triage/
Updated: 2026-11-01