VeriFlow tester guides

How to write a website test report

A useful report tells the reviewer what you tried, what you expected and what appeared on your screen. Write it as soon as you finish the step, while you can still remember which button you used and what changed.

A simple template for each step

  1. Step: Name the screen and the action you took.
  2. Setup: Record the device and browser if they matter to the result or the brief asks for them.
  3. Expected: Describe what you thought would happen after the action.
  4. Observed: Describe what actually happened. Quote the visible error text if you can safely share it.
  5. Impact: Say whether you could continue, needed to try something else, or were blocked.
  6. Evidence: Attach the screenshot requested in the brief, if applicable. Describe what it shows.

Turn a vague comment into a useful finding

Too vague: “The delivery page doesn’t work.”

Useful: “On Safari on my phone, I selected a Saturday delivery slot and tapped Continue. I expected the review screen. The page stayed on the slot picker and the selected time disappeared. There was no error message, and I could not tell whether the slot was still available.”

Write down what you can verify. A button that appears to do nothing is a useful observation. You do not need to guess why it happened.

If the step worked or you had to stop

Before you submit

Check the brief for required steps and screenshots. Use evidence from your own run. Keep passwords, verification codes, card details and identity documents out of your notes and screenshots. Crop or cover sensitive information while leaving the relevant message visible.

If you want to see the whole process, read the sample brief and worked report. For more about joining VeriFlow, see the guide to paid user testing in Ireland.