Software test strategy is a very important thing when it comes to software quality assurance.Software test plan and strategy plan are two different documents.Normally strategy plan is included in the test plan.It is nice to have a test plan in any project. But having a strategy plan is a very effective thing to do.
In an agile environment, you can create a test strategy plan for every sprint. Creating a test plan is optional.
Having a test strategy plan will help you to mitigate risks and minimize faults during the testing process. Hence it will help test team to complete a successful testing cycle.
You can create test strategy document anyway you want depend on your organizational requirements and your QA approach.
Below are the items that we used in creating test strategy document in one of my previous companies.
1. Scope and overview
Here you can mention an overview of the application you are going to test.And then as for the scope, mention what to test and why to test. For example, If it is a customer registration module that you are testing, what to test is customer registration process. And why to test is to make sure you can successfully register a customer.
2. Test approach
In this section we define Test levels, Test types, Roles and responsibilities and environment requirements.
As for the test levels, You can mention unit testing (this means testing individual components separately), integrated testing, system testing, Acceptance testing(If only if this is done by QA team).
As for the test types, you can mention functional testing, regression testing, smoke testing, performance testing, security testing.
You can also mention whether you are going to do automation or not as well.
Roles and responsibilities, mention the roles and responsibilities of individual testers.
As environment requirements, mention the requirement of hardware and software needed to create the testing environment.
3. Test deliverable
In this section you can mention that you are going to produce before, during and end of the testing process. Test deliverables such as test plan, test strategy plan, test cases, test data, incident report(this helps to mitigate the future risks that will come while testing.), test status, requirement traceability matrix test summary and test release.
4. Test tools
Mention all the testing tools you are going to use such as where to create test cases and track bugs and what tool to be used for performance testing or security testings.
5. Risk and mitigation
This section is one of the important things worth to mention according to my opinion. Because we face various difficulties during a testing process and it is always good to make a note of predictable risks that can happen and action that need to take to overcome them. For example what are you going to do if a team member goes missing(get sick or resign), what are you going to do if you not enough time to complete the testing process and what are you going to do if another urgent functionality needed to be tested during this testing process. Hence there are many more predictable risks as such.