Read the evidence behind a launch decision.

Start with coverage, reproduce the observation, then compare the same steps after a fix.

For a worked example with direct before and retest screenshots, read How to read a website QA report. The example is our owned synthetic fixture, not a customer result.

Start with coverage

A report lists pages, journeys, browser versions, screen sizes, timestamps and untested areas. The verdict applies to that coverage. Zero findings is a valid result.

Reproduce a finding

Each finding has an ID, severity, expected and observed behavior, exact steps, a browser and screen size, and a screenshot. Open the evidence to see what was observed rather than inferring a defect from a tool flag.

Verify the fix

A retest records the same finding ID and steps against the deployed correction. Resolved, still present and untested are distinct outcomes. Up to five reported fixes are included in each eligible retest.

See the owned synthetic Chrome and WebKit sample · Prepare a retest request