What is exploratory testing, and how is it structured so it isn't just random clicking?
- Exploratory testing is unscripted but not random — it's goal-driven, using a stated charter and a fixed time box, typically 60–90 minutes.
- The formal name is session-based test management, SBTM.
- It complements scripted automation — automation catches known regressions, exploratory catches the unknown unknowns a script was never written to check.
The long answer
Exploratory testing is often misunderstood as “randomly clicking around.” The correct, disciplined version is session-based test management (SBTM), developed by James and Jonathan Bach.
The structure: before starting, you write a charter — a one-line mission statement for the session, like “explore the checkout flow for edge cases around payment failures” or “probe the forget-password flow for anything scripted tests wouldn’t catch.” You then work within a fixed time box, typically 60–90 minutes, actively testing without a pre-written script — following your instincts, reacting to what you see, chasing anomalies.
This is heuristic-driven rather than scripted. A tester uses mental shortcuts to generate test ideas on the fly — things like “if it looks weird, poke it,” or more formal heuristic sets like HICCUPPS. You don’t need to memorize the full heuristic list; knowing the term and that exploratory testing is heuristic-driven is sufficient at this depth.
Why it matters alongside automation: scripted tests, including your Playwright suites, only catch what someone already thought to write down. Exploratory testing finds the unknown unknowns — a human actively reacting to the live application catches things a script never anticipated. The two are complementary, not competing: automation for fast, repeatable regression coverage; exploratory for discovery, especially right after a new feature lands or right before a release.
Describing exploratory testing as "unstructured" or "just clicking around" — the discipline is the charter and time box; without those it's not exploratory testing, it's just aimless poking.
