Advanced Exploratory Testing
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
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 |
| Interfaces |
Interacts well? |
APIs, UI, integrations |
| Platform |
Works in environment? |
Browsers, OS, devices |
| Operations |
Can be used/managed? |
Install, config, monitor |
| Time |
Handles timing? |
Concurrency, timeouts, scheduling |
FEW HICCUPPS Oracle (Recognize Problems)
| Consistency With |
Check |
| Familiar problems |
Does this look like a known bug pattern? |
| Explainable |
Can behavior be explained rationally? |
| World |
Matches real-world expectations? |
| History |
Consistent with prior versions? |
| Image |
Matches brand/product image? |
| Comparable |
Similar to competing products? |
| Claims |
Matches specs/docs/marketing? |
| Users |
Meets user expectations? |
| Purpose |
Fulfills intended purpose? |
| Statements |
Matches what devs said? |
Test Tours (12 Types)
| Tour |
Strategy |
| Business District |
Critical business flows |
| Historical |
Where bugs clustered before |
| Bad Neighborhood |
Known problem areas |
| Money |
Revenue-impacting features |
| Landmark |
Navigate by key features |
| Intellectual |
Complex, thinking-intensive features |
| FedEx |
Follow data through system |
| Garbage Collector |
Cleanup and edge cases |
| Museum |
Help docs and examples |
| Rained-Out |
What happens when things fail? |
| Couch Potato |
Minimal effort paths |
| Obsessive-Compulsive |
Repetitive actions |
Session Note Template
**Charter:** Explore [area] to discover [what] focusing on [heuristic]
**Time-box:** 60 min | **Tester:** [name] | **Date:** [date]
## Session Notes
- [timestamp] Observation/finding
- [timestamp] Bug: [description] - [severity]
- [timestamp] Question: [unclear behavior]
## Findings Summary
- Bugs: X (Critical: Y, Major: Z)
- Questions: X
- Ideas: X
## Coverage
- Areas explored: [list]
- Heuristics used: [SFDIPOT areas]
- % Time on: Bug investigation 30%, Exploration 50%, Setup 20%
## Next Steps
- [ ] Deep dive on [area]
- [ ] Follow up on question about [topic]
Agent-Assisted Exploration
// Collaborative exploration session
await Task("Exploratory Session", {
charter: 'Explore checkout flow for payment edge cases',
duration: '60min',
heuristics: ['SFDIPOT', 'FEW_HICCUPPS'],
tour: 'money',
collaboration: 'human-navigator-agent-driver'
}, "qe-flaky-test-hunter");
// Agent generates test variations while human observes
await Task("Edge Case Generation", {
area: 'payment-form',
variations: ['boundary-values', 'invalid-inputs', 'concurrent-submits']
}, "qe-test-generator");
// Visual exploration
await Task("Visual Exploration", {
tour: 'landmark',
focus: 'responsive-breakpoints',
compare: 'baseline-screenshots'
}, "qe-visual-tester");
Agent Coordination Hints
Memory Namespace
aqe/exploratory/
├── sessions/* - Session notes and findings
├── charters/* - Reusable charter templates
├── bug-clusters/* - Historical bug patterns
└── heuristic-results/* - What heuristics revealed
Fleet Coordination
const exploratoryFleet = await FleetManager.coordinate({
strategy: 'exploratory-testing',
agents: [
'qe-flaky-test-hunter', // Pattern recognition
'qe-visual-tester', // Visual anomalies
'qe-quality-analyzer' // Risk assessment
],
topology: 'mesh'
});
Pairing Patterns
| Pattern |
Human Role |
Agent Role |
| Driver-Navigator |
Navigate strategy |
Execute variations |
| Strong-Style |
Dictate actions |
Record findings |
| Ping-Pong |
Observe one area |
Explore another |
Related Skills
Remember
Exploratory testing = simultaneous learning, test design, and test execution.
Not random clicking. Structured, skilled investigation guided by heuristics and oracles. Document discoveries in real-time. Pair testing amplifies findings.
With Agents: Agents generate variations, recognize patterns, and maintain session notes while humans apply judgment and intuition. Combine agent thoroughness with human insight.
1---2name: exploratory-testing-advanced3description: 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.4---56# Advanced Exploratory Testing78<default_to_action>9When exploring software or investigating quality risks:101. CREATE charter with mission, scope, and time-box (45-90 min)112. APPLY heuristics: SFDIPOT (quality criteria), FEW HICCUPPS (consistency oracles)123. EXPLORE systematically using test tours (Business District, Bad Neighborhood, Historical)134. DOCUMENT findings in real-time with notes, screenshots, evidence145. DEBRIEF: What learned? What's next? Share via agent memory1516**Quick Heuristic Selection:**17- What to test → SFDIPOT (Structure, Function, Data, Interfaces, Platform, Operations, Time)18- Recognize problems → FEW HICCUPPS (Familiar, Explainable, World, History, Image, Comparable, Claims, Users, Product, Purpose, Standards)19- Navigate app → Test Tours (12 types for different exploration strategies)2021**Critical Success Factors:**22- Exploration is skilled, structured thinking - not random clicking23- Document discoveries, not pre-planned test cases24- Pair testing reveals more than solo exploration25</default_to_action>2627## Quick Reference Card2829### When to Use30- Investigating new or changed features31- Finding bugs automation misses32- Learning unfamiliar systems33- Risk discovery before test planning3435### Session Structure (SBTM)36| Phase | Duration | Activity |37|-------|----------|----------|38| Charter | 5 min | Define mission, scope, focus |39| Explore | 45-75 min | Systematic investigation |40| Note | Continuous | Document findings real-time |41| Debrief | 10-15 min | Summarize, prioritize, share |4243### SFDIPOT Heuristic (What to Test)44| Letter | Focus | Example Questions |45|--------|-------|------------------|46| **S**tructure | Is it properly composed? | Code structure, UI layout, data schema |47| **F**unction | Does it do what it should? | Core features work correctly |48| **D**ata | Handles data correctly? | CRUD, validation, persistence |49| **I**nterfaces | Interacts well? | APIs, UI, integrations |50| **P**latform | Works in environment? | Browsers, OS, devices |51| **O**perations | Can be used/managed? | Install, config, monitor |52| **T**ime | Handles timing? | Concurrency, timeouts, scheduling |5354### FEW HICCUPPS Oracle (Recognize Problems)55| Consistency With | Check |56|-----------------|-------|57| **F**amiliar problems | Does this look like a known bug pattern? |58| **E**xplainable | Can behavior be explained rationally? |59| **W**orld | Matches real-world expectations? |60| **H**istory | Consistent with prior versions? |61| **I**mage | Matches brand/product image? |62| **C**omparable | Similar to competing products? |63| **C**laims | Matches specs/docs/marketing? |64| **U**sers | Meets user expectations? |65| **P**urpose | Fulfills intended purpose? |66| **S**tatements | Matches what devs said? |6768### Test Tours (12 Types)69| Tour | Strategy |70|------|----------|71| Business District | Critical business flows |72| Historical | Where bugs clustered before |73| Bad Neighborhood | Known problem areas |74| Money | Revenue-impacting features |75| Landmark | Navigate by key features |76| Intellectual | Complex, thinking-intensive features |77| FedEx | Follow data through system |78| Garbage Collector | Cleanup and edge cases |79| Museum | Help docs and examples |80| Rained-Out | What happens when things fail? |81| Couch Potato | Minimal effort paths |82| Obsessive-Compulsive | Repetitive actions |8384---8586## Session Note Template8788```markdown89**Charter:** Explore [area] to discover [what] focusing on [heuristic]90**Time-box:** 60 min | **Tester:** [name] | **Date:** [date]9192## Session Notes93- [timestamp] Observation/finding94- [timestamp] Bug: [description] - [severity]95- [timestamp] Question: [unclear behavior]9697## Findings Summary98- Bugs: X (Critical: Y, Major: Z)99- Questions: X100- Ideas: X101102## Coverage103- Areas explored: [list]104- Heuristics used: [SFDIPOT areas]105- % Time on: Bug investigation 30%, Exploration 50%, Setup 20%106107## Next Steps108- [ ] Deep dive on [area]109- [ ] Follow up on question about [topic]110```111112---113114## Agent-Assisted Exploration115116```typescript117// Collaborative exploration session118await Task("Exploratory Session", {119 charter: 'Explore checkout flow for payment edge cases',120 duration: '60min',121 heuristics: ['SFDIPOT', 'FEW_HICCUPPS'],122 tour: 'money',123 collaboration: 'human-navigator-agent-driver'124}, "qe-flaky-test-hunter");125126// Agent generates test variations while human observes127await Task("Edge Case Generation", {128 area: 'payment-form',129 variations: ['boundary-values', 'invalid-inputs', 'concurrent-submits']130}, "qe-test-generator");131132// Visual exploration133await Task("Visual Exploration", {134 tour: 'landmark',135 focus: 'responsive-breakpoints',136 compare: 'baseline-screenshots'137}, "qe-visual-tester");138```139140---141142## Agent Coordination Hints143144### Memory Namespace145```146aqe/exploratory/147├── sessions/* - Session notes and findings148├── charters/* - Reusable charter templates149├── bug-clusters/* - Historical bug patterns150└── heuristic-results/* - What heuristics revealed151```152153### Fleet Coordination154```typescript155const exploratoryFleet = await FleetManager.coordinate({156 strategy: 'exploratory-testing',157 agents: [158 'qe-flaky-test-hunter', // Pattern recognition159 'qe-visual-tester', // Visual anomalies160 'qe-quality-analyzer' // Risk assessment161 ],162 topology: 'mesh'163});164```165166---167168## Pairing Patterns169170| Pattern | Human Role | Agent Role |171|---------|------------|------------|172| Driver-Navigator | Navigate strategy | Execute variations |173| Strong-Style | Dictate actions | Record findings |174| Ping-Pong | Observe one area | Explore another |175176---177178## Related Skills179- [context-driven-testing](../context-driven-testing/) - RST foundations180- [risk-based-testing](../risk-based-testing/) - Focus exploration on risk181- [agentic-quality-engineering](../agentic-quality-engineering/) - Agent coordination182183---184185## Remember186187**Exploratory testing = simultaneous learning, test design, and test execution.**188189Not random clicking. Structured, skilled investigation guided by heuristics and oracles. Document discoveries in real-time. Pair testing amplifies findings.190191**With Agents:** Agents generate variations, recognize patterns, and maintain session notes while humans apply judgment and intuition. Combine agent thoroughness with human insight.
fndlalit