Test Strategy

The purpose of a test strategy is to clarify the major tasks and challenges of the test project.

Creating a Test Strategy :
The test strategy is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment.

Defining Test Strategy :
A solid testing strategy provides the framework necessary to implement your testing methodology. A separate strategy should be developed for each system being developed taking into account the development methodology being used and the specific application architecture.
The heart of any testing strategy is the master testing strategy document. It aggregates all the information from the requirements, system design and acceptance criteria into a detailed plan for testing. A detailed master strategy should cover the following:

1. Project Scope
2. Test Objectives
3. Features and Functions to be Tested
4. Testing Approach
5. Testing Process and Procedures
6. Test Compliance
7. Testing Tools
8. Defect Resolution
9. Roles and Responsibilities
10. Process Improvement
11. Deliverables
12. Schedule
13. Environmental Needs
14. Resource Management
15. Risk and Contingencies
16. Approvals and Workflow

What to include in the Testing Strategy

1. Project Overview
2. Business Risks
3. Testing Milestones
4. Testing Approach
5. Testing Environment