context-driven-testing

Context-driven testing selects strategies by analyzing your project's specific goals, constraints, and risks rather than applying universal best practices. Map your project's context—team skills, timeline, budget, risk areas—then propose a testing approach tailored to that situation, documenting the rationale for each decision.

Risk-based testing prioritizes testing efforts on areas with the highest potential impact and likelihood of failure. Identify functional and technical risks in your project, assess their severity, and allocate your testing resources—including exploratory testing sessions—to cover high-risk scenarios first using frameworks like SFDIPOT and Oracles.

Exploratory testing involves simultaneous learning, test design, and execution guided by risk scenarios. Use Tours and Oracles to structure discovery, document findings as you test, and adapt your approach based on what you learn about the system, ensuring comprehensive coverage of context-specific risks.

Question standard practices when project constraints—timeline, budget, team expertise, or specific risks—diverge from their assumptions. Context-driven testing encourages adaptive planning: reassess your testing strategy as context changes, document why you're deviating from convention, and validate that your chosen approach meets your actual project goals.

Prescriptive methodologies apply fixed processes regardless of situation; context-driven testing tailors strategies to your project's unique constraints and risks. Rather than following dogma, you analyze context, make deliberate trade-offs, and choose methods—including exploratory testing—that fit your specific goals and resources.

Capture discovery documentation throughout your testing process: record which testing strategies you chose, why they fit your context, what risks they address, and what you learned. This documentation serves as rationale for your approach and helps teams understand the trade-offs made in adaptive test planning.