Test strategy means “How you are going to test the application”. It deals with test objectives, approach, test environment, automation strategy and tools, and risk analysis with a contingency plan.

参考资料：

1. How To Write Test Strategy Document (With Sample Test Strategy Template)
2. What is Test Strategy? Types of strategies with examples
3. 7 Steps to Develop Good Test Strategy Document
4. Test Plan Tutorial: A Guide To Write A Software Test Plan Document From Scratch

What

Test strategy means “How you are going to test the application?” You need to mention the exact process/strategy that you are going to follow when you will get the application for testing.

test strategy defines guidelines for test approach to be followed in order to achieve the test objectives and execution of test types defined in the testing plan. It deals with test objectives, approach, test environment, automation strategy and tools, and risk analysis with a contingency plan.

How

Sections of test strategy document

1. Scope and overview
   This stage is fundamental as it shapes testing company’s vision. It includes:
   • dividing roles and responsibilities, deciding who should approve, review and use this document;
   • defining phases of each project according to the timelines that are specified in the test plan.
2. Test Approach
   This step should be well-thought to avoid further mess in case something goes wrong. The main points to be considered at this stage are:
   • testing process and life cycle;
   • distribution of responsibilities among the team of QA engineers;
   • defining all testing types that company can provide the client with;
   • establishing testing approaches.
3. Test environment
   This stage of Test Strategy document has to cover the next aspects regarding test data:
   • requirements – the clear instruction on how to create test data;
   • environments and all required setups for each of them;
   • backup and restore strategy to make sure you won’t lose any data due to some unexpected code issues.
4. Testing tools
   At this point you need to choose all the tools that will be used for test execution. All commercial, open source, automation and management tools have to be listed here.
5. Realese
   To ensure successful test execution, make sure your release management plan is created thoughtfully. Thus, set a build management process to know where new build should be available, when it’s going to be deployed, who should deploy it, how to stop release in case of issues, etc.
6. Industry standards to follow
7. Test deliverables
8. Testing metrics
9. Requirement Traceability Matrix
10. Risk and mitigation
    Try to foresee all possible risks related to your project. Write a clear plan to avoid such risks and a contingency plan in case these risks become a reality.
11. Reporting tool
12. Test summary
    The ready plan must be reviewed and approved by managers, technical team leaders, business development, and software development teams. Also Test Strategy document can be updated in case some important changes occur in the course of the testing process.

Simple Tips To Write Test Strategy Document

1. Include product background in the test strategy document. In the first paragraph of your test strategy document answer – Why stakeholders want to develop this project? This will help to understand and prioritize things quickly.
2. List all important features you are going to test. If you think some features are not part of this release then mention those features under “Features not to be tested” label.
3. Write down the test approach for your project. Clearly, mention what types of testing you are going to conduct?
   i.e. Functional testing, UI testing, Integration testing, Load/Stress testing, Security testing, etc.
4. Answer questions like how you are going to perform functional testing? Manual or automation testing? Are you going to execute all test cases from your test management tool?
5. Which bug tracking tool you are going to use? What will be the process when you will find a new bug?
6. What are your test entry and exit criteria?
7. How will you track your testing progress? What metrics are you going to use for tracking test completion?
8. Task distribution – Define the roles and responsibilities of each team member.
9. What documents will you produce during and after the testing phase?
10. What risks do you see in Test completion?