Skip to main content

​
Follow the evidence

A review combines change context, a generated plan, browser execution, and analysis. Open a finding’s evidence and select the recorded browser and viewport to understand the affected user experience.
  • Steps and checkpoints describe what the run attempted and verified.
  • DOM replay shows historical events captured during that target’s execution.
  • Screenshots preserve appearance at recorded moments.
  • Playwright traces help inspect the execution in detail.
  • Console, network, and layout evidence provide diagnostic context.
  • Reproduction evidence, when available, shows the result of repeating an affected flow.
Available artifacts depend on the execution path and whether capture completed. Missing evidence must remain visible as missing rather than being replaced with a simulated recording.

​
A replay is a recording

Each browser and viewport has its own execution and recording. Resizing a replay does not demonstrate how the application would respond at a new viewport. That requires another execution or a live preview.

​
Interpret results

An aberration describes unexpected behavior or appearance, grounded in evidence. An inconclusive reproduction is still inconclusive. Incomplete requested coverage cannot produce a successful production Check, and a score does not prove coverage of flows that were never executed. Hosted evidence links require workspace authorization and are subject to artifact expiration and deletion. PostHog is used for product diagnostics, not as the store for customer review evidence. The local workflow records evidence in the local dashboard and does not publish results to GitHub.