Screen recordings that actually prove a bug
Timestamp + marked moment + form field — not a 20-minute tour. Reviewable evidence beats narration every time.
Screen recording is cheap to require and expensive to review badly. A tester uploads twenty minutes of clicking while talking. You scrub for the stall. You never find a clean moment. You approve out of fatigue or reject without a crisp reason. Neither is QA.
A recording that proves a bug is short in attention, even if the file is longer: you can jump to the failure, see the UI state, and match it to a form field.
What “proof” means on a ship gate
- Observable failure — error, wrong screen, missing control, data that did not save — not “felt confusing.”
- Jumpable timestamp — minute:second (or marker) where the stall starts.
- Form agreement — finished / blocked / step name matches what the video shows.
- Environment honesty — same start URL and credentials from the brief.
If those four are missing, you do not have a settleable submission. You have a movie.
What to ask for in the brief
Write it once so every slot produces the same shape:
- Record from start URL through success or hard stop.
- Mark the first stall (or note the timestamp in the form).
- Fill severity + where it broke using your step labels.
- Do not narrate the whole product — talk only if it clarifies the stall.
Optional narration is fine. Mandatory essays over video are not. Related craft: what a good tester submission looks like.
How developers should review
- Open the form first. Jump to the timestamp. Confirm the claim.
- If form and video disagree, reject with that mismatch named.
- If three recordings stall at the same step, you have a pattern — fix, then re-run the same brief.
- Do not treat a polished walkthrough of happy path as stronger than a messy blocked clip with a clear failure.
Review workflow tips: review submissions.
Common recording failures
| Recording | Problem | Fix in brief or reject reason |
|---|---|---|
| Starts mid-flow | No cold start | Require start URL on camera |
| No stall marked | Review takes forever | Timestamp field required |
| Tour of unrelated screens | Off-mission | Reject; restate mission steps |
| “It broke” with blank screen | No UI evidence | Need error text / network / last click visible |
On QATested
Structured QA on QATested pairs recordings with your custom form so approve/reject is about evidence, not vibes. Post the path, require the mark, review in minutes: post a Structured QA test.
Related: custom report forms · how many testers before you ship · paid testing without wasting time.