| name | context-driven-testing |
| description | Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'. Use when making testing decisions, questioning dogma, or adapting approaches to specific project needs. |
| category | testing-methodologies |
| priority | high |
| tokenEstimate | 1100 |
| agents | ["qe-fleet-commander","qe-regression-risk-analyzer","qe-requirements-validator","qe-quality-analyzer"] |
| implementation_status | optimized |
| optimization_version | 1 |
| last_optimized | "2025-12-02T00:00:00.000Z" |
| dependencies | [] |
| quick_reference_card | true |
| tags | ["context-driven","rst","exploratory","heuristics","oracles","skilled-testing"] |
| trust_tier | 0 |
| validation | null |
Context-Driven Testing
<default_to_action>
When making testing decisions or adapting approaches:
- ANALYZE context: project goals, constraints, risks, team skills
- QUESTION practices: "Why this? What risk does it address? What's the cost?"
- INVESTIGATE not just check: Does software solve the problem, or create new ones?
- ADAPT approach based on context, not "best practices"
- DOCUMENT discoveries, not pre-written plans
Quick Context Analysis:
- Mission: "Find important problems fast enough to matter" (not "execute test cases")
- Risk: Safety-critical = high rigor; internal tool = lighter touch
- Constraints: Startup with tight timeline ≠ enterprise with compliance
- Skills: Novice needs structure; expert adapts intuitively
Critical Success Factors:
- No "best practices" work everywhere - only good practices in context
- Testing is investigation, not script execution
- Context changes; your approach should too
</default_to_action>
Quick Reference Card
When to Use
- Making testing decisions for new project
- Questioning "that's how it's done" dogma
- Adapting approach to specific constraints
- Exploratory testing sessions
RST Heuristics
| Heuristic | Application |
|---|
| SFDIPOT | Structure, Function, Data, Interfaces, Platform, Operations, Time |
| Oracles | Consistency with history, similar products, expectations, docs |
| Tours | Business District, Historical, Bad Neighborhood, Tourist, Museum |
Context-Driven Decisions
Example: Test Automation Level
Startup Context:
- Small team, rapid changes, unclear product-market fit
- Decision: Light automation on critical paths, heavy exploratory
- Rationale: Requirements change too fast for extensive automation
Enterprise Context:
- Stable features, regulatory requirements, large team
- Decision: Comprehensive automated regression suite
- Rationale: Stability allows automation investment to pay off
