context-driven-testing

Context-driven testing adapts testing practices to specific project contexts by analyzing goals, constraints, and risks. It focuses on investigating whether software solves problems rather than applying generic best practices.

Apply risk-based testing in agile by questioning existing practices to ensure they address actual project risks. This approach adapts methodologies based on team skills and specific constraints rather than following rigid plans.

Start exploratory testing by analyzing project goals, constraints, and team skills to inform decisions. Document discoveries and adapt approaches based on findings, focusing on investigation over pre-written checking procedures.

Use context-driven testing when universal best practices fail to address specific project risks. It suits projects requiring adaptable methodologies where investigating software behavior outweighs following predefined test scripts.

Yes, context-driven testing requires understanding project goals, constraints, risks, and team skills. This foundational knowledge ensures testing approaches are properly adapted to address relevant factors instead of generic scenarios.

Focus on investigation over checking to determine whether software actually solves the problem or creates new ones. This context-driven approach prioritizes discovering critical information over verifying pre-written test plan compliance.