exploratory-testing-advanced

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.

$ 설치

git clone https://github.com/proffesor-for-testing/agentic-qe /tmp/agentic-qe && cp -r /tmp/agentic-qe/.claude/skills/exploratory-testing-advanced ~/.claude/skills/agentic-qe

// tip: Run this command in your terminal to install the skill


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.0 last_optimized: 2025-12-02 dependencies: [] quick_reference_card: true tags: [exploratory, sbtm, rst, heuristics, test-tours, session-based]

Advanced Exploratory Testing

<default_to_action> When exploring software or investigating quality risks:

  1. CREATE charter with mission, scope, and time-box (45-90 min)
  2. APPLY heuristics: SFDIPOT (quality criteria), FEW HICCUPPS (consistency oracles)
  3. EXPLORE systematically using test tours (Business District, Bad Neighborhood, Historical)
  4. DOCUMENT findings in real-time with notes, screenshots, evidence
  5. 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)

PhaseDurationActivity
Charter5 minDefine mission, scope, focus
Explore45-75 minSystematic investigation
NoteContinuousDocument findings real-time
Debrief10-15 minSummarize, prioritize, share

SFDIPOT Heuristic (What to Test)

LetterFocusExample Questions
StructureIs it properly composed?Code structure, UI layout, data schema
FunctionDoes it do what it should?Core features work correctly
DataHandles data correctly?CRUD, validation, persistence
InterfacesInteracts well?APIs, UI, integrations
PlatformWorks in environment?Browsers, OS, devices
OperationsCan be used/managed?Install, config, monitor
TimeHandles timing?Concurrency, timeouts, scheduling

FEW HICCUPPS Oracle (Recognize Problems)

Consistency WithCheck
Familiar problemsDoes this look like a known bug pattern?
ExplainableCan behavior be explained rationally?
WorldMatches real-world expectations?
HistoryConsistent with prior versions?
ImageMatches brand/product image?
ComparableSimilar to competing products?
ClaimsMatches specs/docs/marketing?
UsersMeets user expectations?
PurposeFulfills intended purpose?
StatementsMatches what devs said?

Test Tours (12 Types)

TourStrategy
Business DistrictCritical business flows
HistoricalWhere bugs clustered before
Bad NeighborhoodKnown problem areas
MoneyRevenue-impacting features
LandmarkNavigate by key features
IntellectualComplex, thinking-intensive features
FedExFollow data through system
Garbage CollectorCleanup and edge cases
MuseumHelp docs and examples
Rained-OutWhat happens when things fail?
Couch PotatoMinimal effort paths
Obsessive-CompulsiveRepetitive 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

PatternHuman RoleAgent Role
Driver-NavigatorNavigate strategyExecute variations
Strong-StyleDictate actionsRecord findings
Ping-PongObserve one areaExplore 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.