This Testing Ask Me Anything is kindly sponsored by Applitools. Applitools is on a mission to help test automation, DevOps, and software engineering teams release apps that are visually perfect -- by providing the only commercial-grade solution that validates the user interface of any app in a fully automated manner. Find out more about Applitools.
A Test Strategy is a solution to a complex problem: how do we meet the information needs of our team & stakeholders in the most efficient way possible? A Test Strategy is “a set of ideas that guide your test design or choice of tests to be performed”. Rikard Edgren says: "Test strategy contains the ideas that guide your testing effort and deals with what to test, and how to do it. (Some people say test plan or test process, which is unfortunate…). It is in the combination of WHAT and HOW you find the real strategy. If you separate the WHAT and the HOW, it becomes general and quite useless."
A Test Strategy is the start for every tester and helps you to do the right things, gives testing structure and provides insight in risks and coverage. Developing a Test Strategy is hard and many testers struggle with it.
Once registered you could ask Huib any question on Test Strategy you might have, here are a few examples:
- What is the difference between a test plan and a Test Strategy?
- How do I create a Test Strategy? And how do you document your Test Strategy?
- Who should be involved in creating the Test Strategy?
- When is the right time in the development process to create a Test Strategy?
You can find out more about our other software testing conferences and online educational events on our Events page.