Exploratory Testing in Agile

What it is

Exploratory testing is not random clicking. It is a disciplined, investigative approach where the tester simultaneously learns about the system, designs tests, and executes them in real time. The goal is to find what scripted tests cannot: unexpected behaviour, usability gaps, and emergent risks.

In agile teams, exploratory testing is often structured using Session-Based Test Management (SBTM):

• Charter — a mission statement defining what to test, where to look, and what risks to probe.
• Time-box — a focused session of 45–90 minutes with no interruptions.
• Debrief — a short conversation after the session to share findings, assess coverage, and decide next steps.

Because it adapts to what the tester discovers mid-session, exploratory testing excels at finding the unexpected—the behaviours nobody thought to script.

When to use it

Occasion	Why exploratory testing helps
Throughout the sprint	Keeps testing aligned with incremental delivery rather than a big-bang phase at the end.
New features	When functionality is unfamiliar, exploratory testing reveals gaps in requirements and assumptions.
High-risk areas	Complex calculations, security boundaries, or integrations benefit from targeted deep dives.
After major refactoring	Smoke tests may pass, but only a human eye can spot subtle regressions in UX or logic.
Before release	A final sanity check to catch issues that automation and scripted tests have not covered.

Key concepts

Concept	Description
Test Charters	A concise mission statement (e.g., "Explore checkout flow with invalid payment methods to find error-handling gaps"). Guides the session without prescribing steps.
Time-boxing	Fixed-length sessions (typically 45–90 minutes) that create focus and make planning predictable.
SBTM	Session-Based Test Management: a structured approach to planning, tracking, and reporting exploratory testing work.
Debriefs	A 10-minute post-session review with the team or test lead to share findings, discuss coverage, and decide on follow-up actions.
Heuristics	Cognitive shortcuts (e.g., CRUD, boundaries, error handling) that guide testers toward likely defect clusters.

Common pitfalls

Pitfall	How to avoid it
Confusing with ad-hoc clicking	Always use charters and time-boxes. Without structure it is just guessing.
Failing to document findings	Use session sheets, screenshots, or video. Undocumented bugs tend to be forgotten or dismissed.
Sessions without charters	A charter provides mission and scope. Without one, coverage is impossible to measure.
Using as an excuse to skip automation	Exploratory and automated testing are complementary. Automation handles the known; exploration finds the unknown.
Not time-boxing	Open-ended sessions lose focus and are hard to schedule. Stick to 45–90 minutes.

NZ context

In New Zealand's agile teams, exploratory testing should be treated as a scheduled sprint task, not an afterthought. Many NZ organisations—particularly in SaaS and fintech—run tight sprint cycles and expect testers to report progress in stand-ups. Time-boxed sessions fit naturally into this rhythm: a tester can commit to "two 60-minute exploratory sessions on the payment module" and report results the next day.

Remote-work culture is also strong in NZ. Debriefs can be async (shared session notes in Confluence or Slack) or sync (a quick Zoom call). The key is that findings are shared, not siloed.

Career level guidance

Level	Focus	What to practise
Junior	Structure & discipline	Run chartered sessions within a time-box, take thorough notes, report findings clearly, and learn common heuristics (boundaries, CRUD, error handling).
Senior	Risk targeting & coaching	Design charters based on risk analysis, facilitate debriefs, pair with juniors during sessions, and identify automation candidates from exploratory findings.
Test Lead	Strategy & metrics	Balance exploratory and automated testing across the release, track session coverage vs risk, coach the team on SBTM, and report exploratory findings to stakeholders in business terms.