| name | exploratory-testing-advanced |
| description | Advanced exploratory testing techniques with Session-Based Test Management (SBTM), RST heuristics, and test tours. Use when planning exploration sessions, investigating bugs, or discovering unknown quality risks. |
| category | testing-methodologies |
| priority | high |
| tokenEstimate | 1000 |
| agents | ["qe-flaky-test-hunter","qe-visual-tester","qe-quality-analyzer"] |
| implementation_status | optimized |
| optimization_version | 1 |
| last_optimized | "2025-12-02T00:00:00.000Z" |
| dependencies | [] |
| quick_reference_card | true |
| tags | ["exploratory","sbtm","rst","heuristics","test-tours","session-based"] |
| trust_tier | 0 |
| validation | null |
Advanced Exploratory Testing
<default_to_action>
When exploring software or investigating quality risks:
- CREATE charter with mission, scope, and time-box (45-90 min)
- APPLY heuristics: SFDIPOT (quality criteria), FEW HICCUPPS (consistency oracles)
- EXPLORE systematically using test tours (Business District, Bad Neighborhood, Historical)
- DOCUMENT findings in real-time with notes, screenshots, evidence
- DEBRIEF: What learned? What's next? Share via agent memory
Quick Heuristic Selection:
- What to test → SFDIPOT (Structure, Function, Data, Interfaces, Platform, Operations, Time)
- Recognize problems → FEW HICCUPPS (Familiar, Explainable, World, History, Image, Comparable, Claims, Users, Product, Purpose, Standards)
- Navigate app → Test Tours (12 types for different exploration strategies)
Critical Success Factors:
- Exploration is skilled, structured thinking - not random clicking
- Document discoveries, not pre-planned test cases
- Pair testing reveals more than solo exploration
</default_to_action>
Quick Reference Card
When to Use
- Investigating new or changed features
- Finding bugs automation misses
- Learning unfamiliar systems
- Risk discovery before test planning
Session Structure (SBTM)
| Phase | Duration | Activity |
|---|
| Charter | 5 min | Define mission, scope, focus |
| Explore | 45-75 min | Systematic investigation |
| Note | Continuous | Document findings real-time |
| Debrief | 10-15 min | Summarize, prioritize, share |
SFDIPOT Heuristic (What to Test)
| Letter | Focus | Example Questions |
|---|
| Structure | Is it properly composed? | Code structure, UI layout, data schema |
| Function | Does it do what it should? | Core features work correctly |
| Data | Handles data correctly? | CRUD, validation, persistence |
