What is the Context-Driven Testing
Let us formulate the following questions in our head: Do we know the importance of context driving testing? What are its values? When should we use it?. After thinking about these questions, we want to answer them by sharing with you the importance of context-driven testing in any process, its values, and the most important thing, what is context-driven testing.
What is the Context-Driven Testing?
Context-driven testing is a model based on the context; it mentions that the human part is the most important. It recommends testers to choose their testing techniques, test deliverables, test documentation, and test objectives by looking into the details of a specific situation. This testing method is very useful when programmers are not provided with documentation.
To successfully conduct this type of testing, software developers must identify the intended market and evaluate the environment in which people are likely to use the product.
Context Driven Testing is not a testing technique, it is a set of values within a testing methodology.
According to James Bach: “To be a context-driven tester is to approach each testing situation as if it were unique in important ways, and to develop the skills to react to situations with a broad and deep awareness of problems in projects and possible testing-related solutions to those problems”.
The idea of this method is that software testing must adapt to the nature of the project, its context, and must not to rely on the simple application of good practices.
There are Seven Basic Principles of the Context-Driven:
- The value of any practice depends on its context.
- There are good practices in context, but there are no best practices.
- People, working together, are the most important part of any project’s context.
- Projects unfold over time in ways that are often not predictable.
- The product is a solution. If the problem isn’t solved, the product doesn’t work.
- Good software testing is a challenging intellectual process.
- Only through judgment and skill, exercised cooperatively throughout the entire project, are we able to do the right things at the right times to effectively test our products.
Values of Context-Driven Testing
Why use Context Driven Testing
- They can control the main challenges of test planning
- Help clarify the mission
- The product is analyzed
- Analyze the risk of the product
- Design the test strategy
- Have a logistics plan
- The plans shared with others
When not to do context-driven testing
- When others are entirely responsible for the quality of the work.
- If the tester is working in a specific and unchanging context.
- When the aim is to change the context.
Effective Context Driven Testing
- Ask questions. It’s important, to get the project’s context and get the maximum test coverage.
- Plan ahead. With that, the person in charge will increase the work efficiently, build rapport within the company and generate more conversations.
- Adjust your plan. It is necessary to adapt to strategy accordingly with new features that arise.
- Let stakeholders decide on the project completion. It helped the tester focus on testing and relieved from responsibility for project completion.
- Avoid applying any practice blindly. Because what works for one project may not necessary will work for others.
After reading about the importance, values, and meaning of context-driven testing, we hope that you can begin utilizing this approach.
If you have any questions about this topic, feel free to reach out to us.
- Context-Driven school of software testing
- Context-Driven Testing.
- Context Driven Testing.
- Context Driven Testing: Complete Tutorial.
- Software Testing Testing: Stuff.
- Context-driven testing in an agile context.
OTHER POSTS YOU MIGHT LIKE
BrowserStack is one of several services that can be used to run a test remotely. Imagine the possibility of testing your system with absolutely any environment. Having that chance is the holy grail of testing since it takes a lot of the guessing game out…
Picture this, you’re in a team working on a new product and you need to design a test plan for it. It’s the first time this product goes through any sort of QA process. Automation isn’t a top priority at the moment. The Product Owners…