Context-driven testing is truly
Explorative testing in practice
Development is people work, software is complex and projects are often unpredictable.
Context-driven testing is truly
Context-driven testing
Testing only adds real value if you fit it in seamlessly. Context-Driven Testing is maximally flexible and therefore always has the highest return!
For whom?
In the beginning you hardly have enough information and there is often time pressure: you have to get started right away. Learn to deal with this complexity and confusion in your work. Prepare for new insights and changes that are sure to come. Context-driven testers choose their test objectives, approach and test documentation by looking closely at the details of the specific situation. The essence of context-driven testing is the application of knowledge and skills that fit in your specific situation. Not using a standard recipe.
Products we test are solutions that meet a need. They provide added value for our stakeholders. Testing is the collection of information through learning, research, exploration and analysis with many different experiments, observations and conclusions about the value of the product. Proper software testing is a challenging, intellectual process.
Context-driven testing is based on the skills of a tester. This makes testing more challenging and fun, but also more effective and efficient and is therefore interesting for anyone who has anything to do with testing. From tester to test manager and from programmer to project manager.
Context-driven testing sees software testing as an intellectually challenging process. It learns testers to deal with true reality in IT projects: complexity, ambiguity, constant change, new information and unclear answers.
How is agile impacting our testing strategies? How do you combine checking and testing in such a fast paced environment? How do you handle continuous change and the ever increasing use of tools?
What's the benefit?
We are increasingly working in an agile way. The market demands faster and cheaper testing with better results. Working software is more important than exhaustive documentation. People and interaction are more important than methods and tools. How does a tester implement this? A tailor-made test approach instead of a test method cast in concrete is the solution. Depending on the specific characteristics of the organization, the project and the system, the tester chooses appropriate methods and techniques.
It is often pointless to write a master test plan that states the test strategy that you will be applying in the coming months. During the project you will learn more and more about the product and you will get a better picture of the risks. As a result, priorities change and the parts to be tested are supplemented or changed completely. During the project you learn and it becomes increasingly clear what the best solution is. So the test strategy and tests also change regularly. A context-driven approach helps in choosing the most appropriate approach because every situation and every project and / or product is unique.
Rapid Software Testing Explored
This three-day, practical training was developed by James Bach and Michael Bolton and introduces you to Rapid Software Testing (RST). It is a complete testing methodology designed for a world of limited resources, information and time. The training is based on the principles from the book “Lessons Learned in Software Testing: a Context-Driven Approach”. You will learn a testing approach that starts with skills development and focuses entirely on the ultimate mission of testing: “providing insight into the status of the project by evaluating the product”.
We have provided in-house Rapid Software Test training courses for various customers. From 2015 we also provide this training as public training; alternating with Michael Bolton and James Bach. Since 2015 you can also follow the training in Dutch.
It is often pointless to write a master test plan that states the test strategy that you will be applying in the coming months. During the project you will learn more and more about the product and you will get a better picture of the risks. As a result, priorities change and the parts to be tested are supplemented or changed completely. During the project you learn and it becomes increasingly clear what the best solution is. So the test strategy and tests also change regularly. A context-driven approach helps in choosing the most appropriate approach because every situation and every project and / or product is unique.
Why Improve Quality Services?
Improve Quality Services has successfully implemented a Context-Driven and Rapid Software testing based approach at several customers. A Context-Driven approach has proven its value in the financial, administrative and (regulated) medical and technical market.
Improve has developed a number of training courses and workshops for you that help implement and optimize a Context-Driven approach.
How can Improve Quality Services help you?
Make an appointment with one of our experts via 040 202 18 03 or via our Contact page.
