Interface outcome
Capture the decisive state, message, value, or control with identifying context.
05 · Evidence
Evidence
Build a decision record that is sufficient, contextual, proportionate, and safe to retain.
Decision-grade proof
Enough to understand. No more than needed.
Screenshots alone are often weak evidence. Combine the visible result with the context required to interpret it: role, data, time, candidate version, expected outcome, and any downstream record.
Transaction trace
Reference the resulting record, event, document, status, or reconciliation point.
Tester observation
Use concise notes for usability, comprehension, sequence, and operational consequence.
Decision lineage
Keep the case, run, defect, fix, retest, and sign-off connected.
Privacy by practice
Preserve proof without preserving unnecessary data.
01
Use synthetic data
Prefer representative, non-personal test records wherever the journey permits.
02
Crop deliberately
Exclude unrelated panels, notifications, tabs, and background content.
03
Redact before upload
Remove identifiers, credentials, financial details, and secrets in the source artifact.
04
Set retention
Keep evidence only as long as the release, regulatory, and audit need requires.
Index the record
Make completeness visible.
Identify
Give every evidence item a stable reference tied to case and run.
Classify
Mark result proof, defect proof, retest proof, control proof, or decision proof.
Validate
Confirm readability, context, redaction, ownership, and storage location.
Close gaps
Resolve missing or ambiguous proof before the release room.
The test
Could an informed reviewer understand what happened, why it matters, and which decision it supports—without asking the tester?