A test strategy is an outline that describes the testing approach of the software development cycle. It is created to inform project managers, testers, and developers about some key issues of the testing process. This includes the testing objective, methods of testing new functions, total time and resources required for the project, and the testing environment.
Test strategies describe how the product risks of the stakeholders are mitigated at the test-level, which types of test are to be performed, and which entry and exit criteria apply. They are created based on development design documents. System design documents are primarily used and occasionally, conceptual design documents may be referred to. Design documents describe the functionality of the software to be enabled in the upcoming release. For every stage of development design, a corresponding test strategy should be created to test the new feature sets.
Read more about Test Strategy: Test Levels, Roles and Responsibilities, Environment Requirements, Testing Tools, Risks and Mitigation, Test Schedule, Regression Test Approach, Test Groups, Test Priorities, Test Status Collections and Reporting, Test Records Maintenance, Requirements Traceability Matrix, Test Summary, See Also
Famous quotes containing the words test and/or strategy:
“Experimental work provides the strongest evidence for scientific realism. This is not because we test hypotheses about entities. It is because entities that in principle cannot be ‘observed’ are manipulated to produce a new phenomena
[sic] and to investigate other aspects of nature.”
—Ian Hacking (b. 1936)
“Our strategy in going after this army is very simple. First we are going to cut it off, and then we are going to kill it.”
—Colin Powell (b. 1937)