Log in
← Blog

Exploratory Testing That Isn’t Just Clicking Around

Exploratory testing finds the bugs scripts never will, but only with structure. Charters, time boxes, notes and debriefs, with example charters you can use tomorrow.

Vihari Panyam

September 1, 2026 · 4 min read

Two people at a laptop, one pointing at a line of code while the other types

In short

  • Exploratory testing means designing and running tests at the same time, using what you learn to decide what to try next.
  • It works best in short, focused sessions with a written charter: what to explore, with what, to find out what.
  • Notes and a short debrief turn a session into evidence the team can use, instead of "I had a look around".
On this page

Every scripted test passed. Then a tester spent forty minutes trying to break the new booking form and found four bugs: it accepted a check-out date before the check-in date, it double-booked when you pressed Back and resubmitted, the confirmation email used the wrong time zone, and pasting a name with an emoji crashed the PDF receipt. None of those were in the test cases, because nobody imagined them until they were looking at the real thing.

That is exploratory testing at its best. The risk is that it turns into "I clicked around for a bit and it seemed fine", which tells nobody anything. The difference is structure.

01What exploratory testing is

In scripted testing, you design tests first and run them later. In exploratory testing, you do both at once: each thing you try teaches you something about the software, and that shapes the next thing you try. It relies on the tester’s skill and curiosity, which is exactly why it finds what scripts miss.

It is not random, and it is not unplanned. The planning just happens in a different shape: a charter instead of a script.

02Write a charter

A charter is one or two sentences that say what to explore, with what, and what you hope to find out. A popular template is: Explore (target) with (resources) to discover (information).

AreaExample charter
Booking formExplore date selection with past dates, same-day, leap years and other time zones, to discover how the form handles impossible or edge-case stays.
CheckoutExplore checkout with Back, Refresh and two open tabs, to discover whether an order can be duplicated or lost.
SearchExplore product search with misspellings, symbols, very long text and other languages, to discover how results and errors behave.
Account settingsExplore changing email and password while logged in on two devices, to discover what happens to the other session.
File uploadExplore receipt upload with large, empty, renamed and unusual files, to discover where validation is missing.

03Run it as a time-boxed session

Session-based test management, described by Jonathan and James Bach, gives exploration a simple rhythm: an uninterrupted session of 60 to 90 minutes, one charter, notes as you go, and a short debrief at the end.

  • Protect the time. No messages, no meetings. Interrupted exploration loses its thread.
  • Stay near the charter. If you find something interesting outside it, note it as a new charter for later rather than chasing it now.
  • Take notes continuously. What you tried, what happened, questions, and anything odd, even if you’re not sure it’s a bug.
  • File bugs as you go for anything clear, with the usual steps and evidence.

04Heuristics: where to poke

When you run out of ideas, short memorable prompts help. A few that work almost everywhere:

  • Zero, one, many: no items, exactly one, lots.
  • Too big, too small, wrong type: lengths, amounts and formats at and past their limits.
  • Interrupt it: Back, Refresh, close the tab, lose the connection, half-way through.
  • Do it twice: double-click, submit twice, open two tabs.
  • Change the context: another browser, a phone, another language, another time zone, another user role.
  • Follow the data: where does what you entered end up? Emails, PDFs, reports, exports.

05Debrief: turn the session into information

Spend ten minutes at the end with a lead or teammate. What did you cover? What did you find? What didn’t you get to? What new charters came out of it? This is what makes exploration visible: instead of "looked fine", the team hears "covered dates and time zones, two bugs, one open question, didn’t get to currency".

06Where it fits with automation

Automation is good at confirming what you already know should work, again and again. Exploration is good at discovering what nobody thought of. Use exploration on new features, risky changes and anything users have complained about, and turn the important findings into automated tests so they stay fixed.

Exploratory session checklist

  • One written charter: explore, with, to discover
  • A protected 60 to 90 minute time box
  • Notes taken throughout, including questions
  • Clear bugs filed during the session
  • A ten-minute debrief: covered, found, not covered, new charters
  • Important findings turned into automated tests

Frequently asked questions

What is exploratory testing?

An approach where test design and test execution happen at the same time, with the tester using what they learn to decide what to try next. It is structured with charters and time boxes rather than step-by-step scripts.

What is a test charter?

A short statement of the mission for an exploratory session, often written as "Explore (target) with (resources) to discover (information)".

Is exploratory testing the same as ad hoc testing?

No. Ad hoc testing is unplanned and usually unrecorded. Exploratory testing has a charter, a time box, notes and a debrief, so its coverage and findings can be reported.

How long should an exploratory session be?

Commonly 60 to 90 minutes. Long enough to get deep into an area, short enough to stay focused.

Can exploratory testing be automated?

Not the exploring itself, which depends on human judgement. But tools can help, and anything important it finds should become an automated regression test.

Written by

Vihari Panyam

QualityAIQ

Sources and further reading

  1. Satisfice: Session-Based Test Management
  2. Satisfice: Exploratory testing
  3. ISTQB Glossary: exploratory testing, test charter

More in Testing Fundamentals