Q19 of 38 · Manual & exploratory
Explain ad-hoc testing and how it differs from exploratory testing.
Short answer
Short answer: Ad-hoc testing is unstructured — no plan, no charter, just 'use the product and see what happens.' Exploratory testing is structured exploration — explicit charter, time-box, notes, debrief. Both are unscripted, but exploratory is disciplined and ad-hoc is opportunistic.
Detail
The two get conflated because both involve a tester using the product without a written test script. The crucial difference is structure.
Ad-hoc testing has no preparation. A tester clicks around for 20 minutes, finds a bug or two, and stops. There's no written record of what was covered, no goal to validate, and no way to know if the same path was tested last week. Useful for very early dev builds, demo-prep checks, or "I have 10 minutes between meetings, let me look around."
Exploratory testing is structured: a written charter ("explore the checkout flow's error handling, looking for state inconsistency"), a time-box (60–90 minutes), notes captured during the session, and a debrief afterwards. The Session-Based Test Management literature formalises this approach.
Why the distinction matters: ad-hoc is fine occasionally, but if your team's testing strategy relies on ad-hoc, you have no way to know what's been tested or to defend the testing in audits. Exploratory testing gives you the same flexibility as ad-hoc but adds the documentation needed to scale and to coordinate across testers.
The two work well in sequence: ad-hoc to get a feel for the product, then exploratory sessions when you have a goal in mind.