Testing Ask Me Anything - Test Strategies - Huib Schoots image
A free account is required to view this content

Testing Ask Me Anything - Test Strategies - Huib Schoots

  • Locked
Define a success measure for a good test strategy?
How does automation figure into a test strategy? Do you create a separate strategy for automation?
What should a brief test strategy contain?
Can you provide an example of a test strategy that worked well for your team and how was this strategy was developed?
How would you approach the test strategy as the sole tester in an organisation where the developer teams are cross functional and everyone should play a role in the quality of the product?
How do you decide when you've spoken to enough people about your test strategy?
Who should be involved in deciding the test strategy - should developers be involved?
What not to do when creating a test strategy?
What are your thoughts on test strategy for an agile environment where modern/progressive approaches are encouraged compared to a traditional environment?
What is a test strategy?
Description

This Testing Ask Me Anything was 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.

Our host Vernon Richards was joined by Huib Schoots to answer all your questions.

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.

Get involved in the community discussion over at The Club where Huib continued to answer questions and share useful resources!

You can find out more about our other software testing conferences and online educational events on our Events page.

More Content