A useful before-and-after comparison repeats the same task under comparable conditions. A changed score or a nicer screenshot does not establish that the obstacle disappeared.
What to record
- Save the original URL, date, device context, selections, expected result, and actual outcome.
- Describe the specific change and whether it is deployed or still a local preview.
- Repeat the original steps after release. Record success, continued failure, or an inconclusive result.
- Keep unrelated changes visible so they do not get credited to the repair without evidence.
If the original failure involved a mobile visitor shipping to Alaska, a desktop test with a California address answers a different question. Keep the inputs.
A check you can run
Keep a small record: task, inputs, original result, change, deployment state, and retest result. If the second run uses a different product or destination, label it a different test rather than treating it as confirmation.
Download preview image