QA Evidence Pack

Identify the issue and acceptance criteria, then map each criterion to automated, manual, contract/mock, external verification, or deferred status. Capture observable outcomes like screenshots, traces, and command outputs, and summarize them in a compact evidence report.

Capture visible state screenshots, Playwright traces, and videos for failures or critical flows, along with viewport and device context. Store large artifacts as files and reference their paths from the evidence report.

Use concise overlays: red rectangles for clipped or overlapping elements, orange arrows for wrong connectors, yellow translucent areas for spacing defects, blue guide lines for alignment, and short labels naming each defect.

No. A passing test without observable-result validation is not sufficient evidence, and a report without acceptance-criteria mapping is incomplete for release. External integrations also need receiver-side evidence or explicit deferral.

Capture request shape, response and error contracts, idempotency behavior, and side effects. For integrations, record sandbox or mock receiver results, webhook events, correlation IDs, and database evidence, or defer with an owner and rationale.