Reason number 1: The number one reason of writing a test strategy document is to “have” a signed, sealed, and delivered, FDA (or FAA) approved document, where the document includes a written testing methodology, test plan, and test cases.
Reason number 2: Having a test strategy does satisfy one important step in the software testing process.
Reason number 3: The test strategy document tells us how the software product will be tested.
Reason number 4: The creation of a test strategy document presents an opportunity to review the test plan with the project team.
Reason number 5: The test strategy document describes the roles, responsibilities, and the resources required for the test and schedule constraints.
Reason number 6: When we create a test strategy document, we have to put into writing any testing issues requiring resolution (and usually this means additional negotiation at the project management level).
Reason number 7: The test strategy is decided first, before lower level decisions are made on the test plan, test design, and other testing issues.
Subscribe to:
Post Comments (Atom)
Thanks for starting the discussion on this topic. Here is my view on this. Many people often get confused by the terms test strategy and test plan and what are the differences between them. In this article let us try to clear that doubt.
ReplyDeleteWhen a project gets initiated, we create the test strategy first. Test-Strategy will tell how to go about testing a business requirement or feature. It details the approach that you will implement to ensure that the product is ready for shipping by release date. This will include the high level functional and non functional test-scripts that you run based on the requirements.
Also I recommend to check the following article for more information:
What is the difference between a Test Strategy and Test Plan