
Observation notes
Expectation
Copy the observable result from the relevant criterion or scenario.
Observation record ↗Observation
Describe the visible result in the same test context. Do not replace the observation with a guess at the cause.
Observation record ↗Environment
Browser, device, build and date can change how useful the record is; add only known details.
Observation record ↗Reference
A reference is a pointer supplied by the tester. This page does not upload or validate the underlying file.
Observation record ↗Difference
A side-by-side note helps a person decide whether the observed result meets the criterion.
Observation record ↗Private details
Do not paste customer records, access tokens or account data into a shareable result.
Observation record ↗Do not fill the second column first
What should appear?
OBSERVEDWhat did appear?
The comparison belongs to a person who saw the product.
Observation record
Keep expected and observed text in separate fields. The page formats your note and marks an unreviewed difference, not an automated verdict.
Follow the work

Make A Failed Path Reproducible
Defect packet ↗
Review Evidence Before A Release Decision
Release board ↗Expectation distinct?
A drafted test, an observed result and a release decision are different events. Keep each one tied to the product you actually checked.