Glossary · Testing fundamentals
Exploratory testing
Also called: exploratory test, exploratory tests, session-based exploratory testing
Definition
Testing where the tester designs and runs tests at the same time, using what each result reveals to decide what to try next.
Exploratory testing is simultaneous learning, test design and test execution. Instead of following pre-written steps, the tester investigates the product, forms a hypothesis about where it might fail, tries it, and lets the result shape the next test. It is structured thinking, not random clicking, and it finds the bugs that nobody thought to write a test case for.
Example: a time-boxed session
Teams usually run exploratory testing in sessions with a written charter:
Charter: Explore the file upload on the profile page with unusual files, to discover how it handles invalid input. 60 minutes.
During the session the tester might try a 0-byte file, a 50 MB image, a .png that is actually a PDF, a filename with emoji or 255 characters, two uploads in quick succession, and cancelling halfway. Each surprise leads to follow-up tests. Notes record what was covered, bugs found, questions raised and areas left for another session.
Exploratory vs scripted testing
| Exploratory | Scripted | |
|---|---|---|
| Design | During execution | Before execution |
| Strength | Finds unexpected bugs, adapts quickly | Repeatable, auditable, easy to automate |
| Weakness | Depends on tester skill, harder to repeat | Only finds what was anticipated |
They complement each other. Scripted and automated tests protect known behavior. Exploration finds the unknowns, and its best findings often become new automated regression tests.
Common mistakes
- No charter, no notes. Without a focus and a record, nobody can tell what was covered and the session cannot be reported.
- Confusing it with ad hoc testing. Ad hoc testing is informal and undocumented. Exploratory testing is deliberate, time-boxed and debriefed.
- Leaving it to the end. Exploring a feature early, while it is still being built, gives developers feedback when it is cheapest to act on.