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:
“Tried by a New England eye, or the more practical wisdom of modern times, they are the oracles of a race already in its dotage; but held up to the sky, which is the only impartial and incorruptible ordeal, they are of a piece with its depth and serenity, and I am assured that they will have a place and significance as long as there is a sky to test them by.”
—Henry David Thoreau (1817–1862)
“Do you think that mere words are strategy and power for war?”
—Bible: Hebrew, 2 Kings 18:20.