context-driven-testing

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"]

Context-Driven Testing

<default_to_action> When making testing decisions or adapting approaches:

1. ANALYZE context: project goals, constraints, risks, team skills
2. QUESTION practices: "Why this? What risk does it address? What's the cost?"
3. INVESTIGATE not just check: Does software solve the problem, or create new ones?
4. ADAPT approach based on context, not "best practices"
5. 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

Seven Context-Driven Principles

1. Value of any practice depends on its context
2. Good practices in context, no universal best practices
3. People working together are most important
4. Projects unfold in unpredictable ways
5. Product is a solution - if problem not solved, product fails
6. Good testing is challenging intellectual work
7. Judgment and skill determine right things at right times

Context Factors

Factor	Questions
Project	Business goal? User needs? Failure impact?
Constraints	Timeline? Budget? Team skills? Legacy?
Risk	Safety-critical? Regulated? High volume?
Technical	Stack quirks? Integrations? Observability?

RST Heuristics

Heuristic	Application