20+ Sections That Should Be In Your Testing Strategy
The Test Strategy defines the general approach that will be employed to test the software and to evaluate the results of testing. It outlines the testing approach, identifies the required resources and communication plan and lists the deliverable elements of the project.
This Test Strategy also supports the following specific objectives:
- Identifies the items that should be targeted by the tests.
- Identifies the motivation for and ideas behind the test areas to be covered.
- Outlines the testing approach that will be used.
- Identifies the required resources.
- Identifies the communication plan.
- Lists the deliverable elements of the test project.
The Testing Strategy document is created during the planning phase. You should check your organizations templates to see if there is pre-made template you should follow for your project.
Below are some key sections that should be part of your testing strategy:
- Scope of Testing
- Abbreviations, Acronyms & Definitions – State the specific terms that will be used in the document.
- Testing Phases
- Testing Types – At the time of planning all testing types should be considered. In the specific test plans you can state which testing type will be performed in the phase/iteration.
- Objectives of the testing types
- State who is responsible for the conducting the testing type
- State which environment the testing type is planed to be performed in.
- Test Approach
- Estimation of testing effort
- Testing Risks
- Testing Dependencies
- Testing Assumptions
- Testing Issues & Risks
- Environments – list the different environments that are part of the project
- Environment Entrance Criteria
- Environment Exit Criteria
- Tools – Specify which tools are used by the testing tools
- Resources – Specify if there are any staffing or training needs as well
- Deliverables – Specify when the distribution cycle as well as the intended recipients.
- Types of testing and what phase they are planned to be conducted
Are there any other sections that you think should be part of the testing strategy?