Software Testing Strategy – The Test Strategy

We discussed Test Plans and their contents in the earlier blog and today we will discuss the Test Strategy. Some people will look at the title above and think we are just repeating our blog from three weeks ago. Luckily, that’s not the case. We differentiate between Test Plans and Test Strategies.

NVP considers a Test Strategy to be a document that outlines a long term direction for testing. It’s possible that the Test Plans for each project will borrow heavily from the Test Strategy and may even be based on it. We’re not necessarily considering that level of connection in this scenario.

The following is a set of contents for a Test Strategy

1. Introduction – outlines the purpose of the document
2. Corporate Business Strategy – Copy and paste from the relevant business document
3. A high level outline of the Test Strategy – See below
4. Alignment with corporate strategy and identification of the gaps
5. Baseline of current testing (where we are today)
6. Gaps between the baseline and Test Strategy
7. Goals or methodologies to close the gaps
8. Strategy assessment process
9. Continuous improvement

The Test Strategy section would include answers to the following:

1. Where is the best place to complete testing in the life cycle?
2. Who are the best resources for each level and type of testing?
3. What is the long term development process for the identified resources?
4. From where are the resources going to be sourced?
5. What is the long term automation process or direction?
6. Where is the greatest ROI for testing?

Some questions to assess your Test Strategy readiness:

1. Do you have a Test Strategy?
2. If you have a Test Strategy; has it been reviewed recently?
3. Is there a person or a group responsible for the Test Strategy?

If you answered No to any of the above questions, send us an email to see if a Test Strategy would be a fit for your organization.

Next Week: Assessments – Deal with Results