Test Strategy is a part of your Test Plan. Test Plan contain the complete details of your Testing.. Test Stratgey is the summary of your Testing Solution. For e.g. If you have to do the testing of a website application then what will be your test strategy...When talking about Test Strategy, remember to include:
1. Testing Process
2. Solution - Types of Testing
3. Resource Alignment
4. Acceptance Criteria
and other attributes as per requirement and org standard.
It is a company level document developed by quality assurance manager or quality analyst category people.
It defines testing approach to reach the standards. Below are the items need to be mentioned in Test Strategy
1. Scope and Objective
2. Budget control
3. Testing approach
4. Test deliverables
5. Roles and responsibilities
6. Communication and status reporting
7. Automation tools (if needed)
8. Testing measurements
9. Risks and mitigations
10. Change configuration management
11. Training plan
It is document which describes the objectives, scope, and approach to follow for validating the software/application or build.
It Contains below items:
1.Test Plan ID
2.Test Description (small description on Module/Feature)
3.Features to be tested
4.Features not to be tested
9.Risk and Mitigations
12.Featues pass or fail critera
Smaller Projects: Test Strategy is contained in Test Plan Document itself
Bigger Projects: Test Strategy gets separated from the Test Plan
Actually Test Strategy is the heart of Test Plan
Good joke.... ;)
A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements. Know more about test plan in the below link-
A test strategy includes the testing objective, methods of testing new functions, total time and resources required for the project, and the testing environment. Know more about test strategy in the below link-
Test Strategy takes a wider view of the whole test process while test design is more focused on the test design process itself. A test strategy document involves input not only from the technical team but also from all the stakeholders in the project e.g business users, top managers etc while a test plan is solely produced by testers.
This is based on my own experience I must say.