# Exploratory Testing

Exploratory testing combines learning, test design, and execution so each observation can guide the next investigation.

- Type: method
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-10-19
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/exploratory-testing/>)

## What it means

Exploratory testing is an investigative approach in which a tester learns about the product while choosing and adapting tests. It can use a charter, timebox, tools, and detailed notes; it is not synonymous with random clicking or undocumented work. Scripted checks verify anticipated outcomes, while exploration can reveal unexpected risks and questions.

## Why it matters

Written requirements and automation inevitably leave gaps. A skilled tester can connect surprising behavior across states, challenge assumptions, and identify questions that no existing test script asks.

## When to use it

Use it for unfamiliar features, complex state transitions, ambiguous requirements, and incident follow-up. Pair it with repeatable checks for known critical behavior. Where formal evidence is needed, preserve a session record and reproducible observations rather than relying on memory.

## How it works

1. Set a charter describing the area, risks, and learning objective.
2. Prepare useful data, tools, and a bounded session duration.
3. Probe behavior and adapt the next test from what you observe.
4. Record paths, evidence, questions, and reproduction details for failures.
5. Debrief findings and turn stable, important cases into repeatable checks where useful.

## A practical example

A tester explores a booking flow with the charter “recover from interrupted checkout.” Switching networks and returning through browser history reveals a duplicate reservation. The team preserves the reproduction and adds a focused automated check after fixing the issue.

## Where it breaks

Coverage depends on tester knowledge and available time. Exploration cannot show that every state was examined, and weak notes make findings difficult to reproduce. It is not a substitute for user research about whether people understand or value the product.

## Common mistakes

- Calling unstructured clicking an exploratory test strategy.
- Reporting a failure without preserving the state and steps.
- Judging session value only by the number of bugs filed.

## Sources

1. [What is Exploratory Testing?](<https://agilealliance.org/glossary/exploratory-testing/>) — Agile Alliance · Professional glossary
2. [Exploratory Testing](<https://www.satisfice.com/exploratory-testing>) — Satisfice · Original author

## Related topics

- [Acceptance Criteria](<https://wiki.soroush.uk/topic/acceptance-criteria/>)
- [Usability Testing](<https://wiki.soroush.uk/topic/usability-testing/>)
- [Product Risk Management](<https://wiki.soroush.uk/topic/product-risk-management/>)
