Context-driven testing is an approach where the situation shapes how testing is done, rather than following a fixed best practice. Testers choose methods based on the project, team, product and risks in front of them.
Why it matters: Approaches that worked in one setting may not fit another. A tester moving from a staged waterfall project to an XP team practising TDD, for example, often finds their old methods no longer apply. Context-driven testing encourages testers to inspect and adapt.
In practice: Testers start by understanding the context: the people, the product, the constraints and what the team needs to learn. They then choose and combine techniques to fit, and keep adjusting as the context changes.
Examples:
- A tester moving from a waterfall organisation to an XP team and rethinking their whole approach.
- Choosing lightweight exploratory notes over detailed scripts for a fast-moving product.
Common pitfalls:
- Using “it depends” to avoid making decisions.
- Ignoring useful practices because they came from a different context.
Is context-driven testing the same as exploratory testing? No. Exploratory testing is a technique. Context-driven testing is a broader approach to choosing techniques, which often includes exploratory testing.
