2. The Test Strategy is normally derived from the Business Requirement Specification document.
3. This document defines “Testing Approach” to achieve testing objectives. The Test Strategy document is a static document meaning that it is not updated too often. It sets the standards for testing processes and activities and other documents such as the Test Plan draws its contents from those standards set in the Test Strategy Document.
4. Main Components are:
- Scope and Objectives
- Business issues - Roles and responsibilities
- Communication and status reporting
- Test deliverability
- Industry standards to follow
- Test automation and tools
- Testing measurements and metrics
- Risks and mitigation
- Defect reporting and tracking
- Change and configuration management
- Training plan
2 comments:
It's very beneficial... Thanks a lot for publishing this stuff.
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.
When 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
Post a Comment