Exploratory Testing
Learn exploratory testing — the art of simultaneously learning, designing, and executing tests. Find bugs scripts miss.
What you'll learn
- Understand what exploratory testing is and when to use it
- Write a test charter to focus a session
- Take useful session notes using the SBTM approach
- Identify bugs that scripted tests would miss
Manual QAlessonsJump to another lesson
Exploratory Testing
Scripted vs Exploratory
Both styles find bugs. They just find different ones.
Scripted Testing
- Steps written in advance
- Repeatable by anyone
- Good for regression runs
- Finds known-risk bugs
- Limited by your imagination when writing
Exploratory Testing
- Steps decided on the fly
- Relies on tester skill and curiosity
- Good for new features or unknown areas
- Finds surprise bugs and usability issues
- Limited only by your curiosity in the moment
VerdictGreat teams use BOTH. Scripted tests catch regressions. Exploratory tests catch everything else.
Session-Based Test Management (SBTM)
Exploratory testing is not chaos. SBTM gives it structure using time-boxed sessions — usually 60 to 120 minutes of focused testing.
- 1
Setup (5 min)
Read the charter, open the app, prepare notes.
- 2
Explore (60-90 min)
Test freely against the mission. Take notes as you go.
- 3
Wrap up (10 min)
Summarize findings, log bugs, note new questions.
- 4
Debrief (15 min)
Share results with the team. Plan the next session.
The Test Charter
A charter is a short mission statement for your session. It keeps you from wandering.
Test Charter
4 fieldsPopular Heuristics
Heuristics are memory aids — lists that remind you what to look for when you’re stuck.
Tour-Based Testing
A “tour” is a lens for exploring the app. Each tour shows you something different.
Feature Tour
Walk every feature once, like a new user.
Money Tour
Follow revenue paths — signup, purchase, upgrade.
Landmark Tour
Jump between key screens in random order.
Supermodel Tour
Test only the visible UI — look, don't interact deeply.
Taking Useful Notes
Your notes are the output of the session. Keep them simple and searchable.
Quick check
Which of these is the BEST fit for exploratory testing?
When NOT to Use Exploratory Testing
Exploratory is powerful, but it is not for every job.
Great for Exploratory
- Brand-new features with no prior tests
- Features with confusing requirements
- Usability and UX investigation
- Following up on a vague bug report
- Evaluating a competitor's product
Bad for Exploratory
- Regression runs that must be identical every time
- Compliance tests that need an audit trail
- Performance tests that need repeatable metrics
- Automated CI pipelines
- Proving coverage for a contract
VerdictExploratory finds new bugs. Scripted proves old bugs stay fixed. Use the right tool for the job.
Practice: Match Tours to Their Purpose
Match each tour type to the best situation for using it.