Exploratory Testing
Simultaneously design, execute, and learn. Exploratory testing isn't just "random clicking" — it's a structured investigation that finds the bugs scripted tests always miss.
1 The Hook — The "Off-Script" Bug
A Senior Tester at a NZ retail giant was running a regression script for the checkout. Every step passed. The computer said "Green."
But the tester noticed that when the "Success" message appeared, it flickered for a split second. Instead of ignoring it, they went Off-Script. They tried clicking the "Confirm" button five times rapidly. The system crashed, double-charged the card, and wiped the user's cart. Automated scripts follow instructions; Exploratory testers follow their instincts.
2 The Rule — Explore / Using / To Discover
Use a Charter to define your mission, and a Timebox to keep you focused.
A good charter follows this formula:
"Explore [Target] using [Resources] to discover [Information]"
3 The Analogy — The Detective
Sherlock Holmes vs. a Patrol Officer.
A patrol officer has a route. They walk the same blocks every day at 10 PM. (That's Scripted Testing). A detective is given a mission: "Find the burglar." They don't have a route; they follow clues. If they find a muddy footprint, they follow it. That's Exploratory Testing. You have a goal, but your path is decided by what you find.
4 Watch Me Do It — NZ Post Address Hunt
Mission: Test the NZ Post "Address Lookup" feature on a new delivery app.
- Create Charter: "Explore the address lookup field using unusual NZ addresses (Rural, Apartments, Gated) to discover if the system fails to resolve valid locations."
- Set Timebox: 30 Minutes.
-
The Hunt:
- Test "101 Customhouse Quay" (Standard) → Works.
- Test "Flat 4, 12B High St" (Complex) → Works.
- Test "RD 1, Kaikohe" (Rural) → Bug! The system doesn't show the RD options.
- The Pivot: Since Rural failed, I'll spend the next 10 mins testing only North Island rural towns.
5 Decision Tool — When to Explore?
✅ Use Exploratory when...
- The feature is brand new and buggy.
- Requirements are vague or missing.
- You have a limited time (e.g., "We ship in 1 hour").
❌ Use Scripted when...
- Testing critical safety/financial math.
- New testers need to follow a process.
- Running a massive regression suite (Automate it!).
6 Common Mistakes
🚫 Thinking it's "Ad-Hoc" (Random)
I used to think: I'll just click around and see what happens.
Actually: Without a Charter, you'll waste time on things that don't matter. Exploratory testing is focused investigation, not aimless wandering.
🚫 Forgetting the Timebox
I used to think: I'll just test until I'm bored.
Actually: Without a time limit (e.g., 30 mins), you'll go down "rabbit holes" and miss the big picture. Respect the timer.
7 Now You Try — Write a Charter
Scenario: You need to test a new "Auckland Council Rates" payment portal. It's live in 20 minutes.
Complete the charter mission below:
Explore... The Credit Card payment flow
Using... Invalid NZ credit card numbers and timeouts
To Discover...
8 Self-Check
Q1. What is the main difference between Exploratory and Ad-hoc testing?
Structure. Exploratory testing uses Charters, Timeboxes, and Session Reports. Ad-hoc is informal and undocumented.
Q2. Can Exploratory testing be used alongside Automation?
Yes! Automation handles the "Boring" stuff (regression). Exploratory testing handles the "New" and "Complex" stuff where human intuition is needed.
9 Interview Prep
"How do you ensure exploratory testing is productive and not just a waste of time?"
Answer: "I use Session-Based Test Management (SBTM). I start with a clear charter, set a strict 30-60 minute timebox, and keep a log of everything I find. At the end of the session, I produce a summary report so the team knows exactly what was covered and where the risks are."
10 Next Step
Now that you've learned to hunt for bugs, let's learn how to Guess where they're hiding based on experience. Next: Error Guessing.