How to run an exploratory testing session that produces useful bug reports

Exploratory testing has a reputation for being unstructured. Done well, it is the opposite: a short, focused session with a clear goal, careful notes and evidence for every finding. The structure is what turns “I clicked around” into bug reports a developer can fix without coming back to ask questions.

Before you start

  • Write a charter: what you are testing, what you are looking for, and what is out of scope. One or two sentences is enough.
  • Set a time box. Sixty to ninety minutes keeps you focused and makes sessions easy to compare.
  • Note the build, browser, device and test account you are using. You will need them in every report.
  • Read the brief or release notes so you know what changed and where the risk is.

During the session

  • Follow the charter, but note anything interesting outside it for a later session rather than chasing it now.
  • Capture evidence as you go: a screenshot or recording at the moment something goes wrong, not ten minutes later.
  • Write down the exact steps while they are fresh, including the data you entered.
  • Try the unhappy paths: empty fields, long names, apostrophes, slow connections, the back button and double clicks.
  • Check the basics a tool can spot quickly, such as missing labels, low contrast and broken links, so you can spend your own time on judgement calls.

Writing it up

  • One bug per report, with a title that says what is wrong and where.
  • Steps to reproduce, the expected result and the actual result.
  • Attach the evidence and the environment details.
  • Rate the impact on a real user, not how interesting the bug was to find.
  • Finish with a short session summary: what you covered, what you did not reach, and what you would test next.

Make it repeatable

The more of this happens in one place, the less you lose between sessions. Keep your charter, notes, evidence and findings together, and the report almost writes itself. That is the idea behind Holstr: one workspace for the whole session, from charter to exported report.

Bring your next test session into one place

Get Holstr, or book a demo and see the whole workspace in action.