Context-driven testing is more a testing approach rather than a testing technique, as it recommends testers to choose their test techniques, test deliverable, test documentation and test objectives by looking into the details of the specific situation.
Context-driven testing method is useful when programmers are not provided with any documents.
The context-driven approach is based on the judgmental call of programmers and testers to develop a software product.
In this tutorial, you will learn-
- Definition of Context Driven Testing
- Seven basic principles of the Context Driven School
- Why to use Context Driven Test
- When NOT to do context driven testing
- How to ensure effective context driven testing
Following are the seven basic principles of the Context-Driven School
- Monitor major test planning challenges
- Clarify your mission
- Analyze the product
- Analyze product risk
- Design the test strategy
- Plan logistics
- Share the plan
- Ask questions: To get the project's context and get the maximum test coverage, you have to ask questions to development team, stakeholders, fellow testers etc.
- Plan ahead: Planning ahead the test plan and sharing it with whole team will make you increase the work efficiently, build rapport within the company and generate more meaningful conversations
- Adjust your plan: With changing schedules, new features and arising priorities it is necessary that you adapt to your strategy accordingly
- Let stakeholders decide on the project completion: Let stakeholder decide the completion of the project. It relieves the tester from responsibility of project completion, and helps him to focus on testing
- Avoid applying any practice blindly: Flexibility is very important for context driven tester because what works for one project may not necessary will work for other