Learn To Write Test Strategy Document Efficiently
A strategy plan for defining the testing approach, what you want to accomplish and how you are going to achieve it.
Recommended IPTV Service Providers
- IPTVGREAT – Rating 4.8/5 ( 600+ Reviews )
- IPTVRESALE – Rating 5/5 ( 200+ Reviews )
- IPTVGANG – Rating 4.7/5 ( 1200+ Reviews )
- IPTVUNLOCK – Rating 5/5 ( 65 Reviews )
- IPTVFOLLOW -Rating 5/5 ( 48 Reviews )
- IPTVTOPS – Rating 5/5 ( 43 Reviews )
This document removes all uncertainty or vague requirement statements with a clear plan of approach for achieving the test objectives. Test Strategy is one of the most important documents for the QA team.
=> Click Here For Complete Test Plan Tutorial Series
What You Will Learn:
- Writing a Test Strategy Document
- Test Strategy
- What is a Test Strategy?
- Test Strategy Vs. Test Plan
- Process to Develop a Good Test Strategy Document
- Common Sections of Test Strategy Document
- Simple Tips to Write a Test Strategy Document
Writing a Test Strategy Document
Writing a Test Strategy effectively is a skill that every tester should achieve in their career. It initiates your thought process that helps to discover many missing requirements. Thinking and test planning activities help the team to define the Testing scope and Test coverage.
It helps Test managers to get the clear state of the project at any point. The chances of missing any test activity are very low when there is a proper test strategy in place.
Test execution without any plan rarely works. I know teams who write strategy document but never refer back while test execution. The Testing Strategy plan must be discussed with the whole team so that the team will be consistent with its approach and responsibilities.
In tight deadlines, you can’t just waive any testing activity due to time pressure. It must atleast go through a formal process before doing so.
What is a Test Strategy?
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 get the application for testing.
I see many companies that follow the Test Strategy template very strictly. Even without a standard template, you can keep this Test Strategy document simple but still effective.
Test Strategy Vs. Test Plan
Over the years, I have seen a lot of confusion between these two documents. So let’s start with the basic definitions. Generally, it doesn’t matter which comes first. The test planning document is a combination of strategy plugged with an overall project plan. According to IEEE Standard 829-2008, the Strategy plan is a sub-item of a test plan.
Every organization has its own standards and processes to maintain these documents. Some organizations include strategy details in the test plan itself (here is a good example of this). Some organizations list strategy as a subsection in a testing plan but details are separated out in different test strategy documents.
Project scope and test focus are defined in the test plan. Basically, it deals with test coverage, features to be tested, features not to be tested, estimation, scheduling and resource management.
Whereas the 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, approaches, test environments, automation strategies and tools, and risk analysis with a contingency plan.
To summarize, the Test Plan is a vision of what you want to achieve and the Test Strategy is an action plan designed to achieve this vision!
I hope this will clear all your doubts. James Bach has more discussion on this topic here.
Process to Develop a Good Test Strategy Document
Don’t just follow the templates without understanding what works best for your project. Every client has its own requirements and you must stick to the things that work perfectly for you. Do not blindly copy any organization or any standard. Always make sure that it is helping you and your processes.
Below is a sample strategy template that will outline what should be covered in this plan along with some examples to illustrate what makes sense to cover under each component.
Test Strategy in STLC:
Common Sections of Test Strategy Document
Step #1: Scope And Overview
Project overview along with information on who should use this document. Also, include details like who will review and approve this document. Define testing activities and phases to be carried out with timelines with respect to overall project timelines defined in the test plan.
Step #2: Test Approach
Define the testing process, level of testing, roles, and responsibilities of every team member.
For every test type defined in the Test plan (For Example, Unit, Integration, System, Regression, Installation/Uninstallation, Usability, Load, Performance, and Security testing) describe why it should be conducted along with details like when to start, test owner, responsibilities, testing approach and details of automation strategy and tool if applicable.
In test execution, there are various activities like adding new defects, defect triage, defect assignments, re-testing, regression testing and finally test sign-off. You must define the exact steps to be followed for each activity. You can follow the same process that worked for you in your previous test cycles.
A Visio presentation of all these activities including a number of testers and who will work on what activities would be very helpful to quickly understand the roles and responsibilities of the team.
For example, defect management cycle – mention the process to log the new defect. Where to log in, how to log new defects, what should be the defect status, who should do defect triage, whom to assign defects after triage etc.
Also, define the change management process. This includes defining change request submissions, templates to be used, and processes to handle the request.
Step #3: Test Environment
The test environment setup should outline information about the number of environments and the required setup for each environment. For example, one test environment for the functional test team and another for the UAT team.
Define the number of users supported in each environment, access roles for each user, software and hardware requirements like operating system, memory, free disk space, number of systems, etc.
Defining test data requirements is equally important. Provide clear instructions on how to create test data (either generate data or use production data by masking fields for privacy).
Define test data backup and restore strategy. The test environment database may run into problems due to unhandled conditions in the code. I remember the problems we faced on one of the projects when there was no database backup strategy defined and we lost all the data due to code issues.
Backup and restore process should define who will take backups when to take a backup, what to include in backup when to restore the database, who will restore it and the data masking steps to be followed if the database is restored.
Step #4: Testing Tools
Define test management and automation tools required for test execution. For performance, load and security testing, describe the test approach and tools required. Mention whether it is an open source or commercial tool and how many users are supported on it and plan accordingly.
Step #5: Release Control
As mentioned in our UAT article, unplanned release cycles can result in different software versions in test and UAT environments. The release management plan with proper version history will ensure test execution of all modifications in that release.
For example, set build management process which will answer – where new build should be made available, where it should be deployed, when to get the new build, from where to get the production build, who will give the go, the no-go signal for production release, etc.
Step #6: Risk Analysis
List all the risks that you envision. Provide a clear plan to mitigate these risks along with a contingency plan in case you see these risks in reality.
Step #7: Review And Approvals
When all these activities are defined in the test strategy 1plan, they need to be reviewed for sign-off by all entities involved in project management, business team, development team, and system administration (or environment management) team.
A summary of the review changes should be tracked at the beginning of the document along with the approver’s name, date and comment. Also, it’s a living document meaning this should be continuously reviewed and updated with testing process enhancements.
Simple Tips to Write a Test Strategy Document
- Include product background in the test strategy document. Answer the first paragraph of your test strategy document – Why do stakeholders want to develop this project? This will help us understand and prioritize things quickly.
- List all the important features you are going to test. If you think some features are not a part of this release then mention those features under “Features not to be tested” label.
- Write down a test approach for your project. Clearly, mention what type of testing you are going to conduct?
i.e., Functional testing, UI testing, Integration testing, Load/Stress testing, Security testing, etc.
- Answer questions like how you are going to perform functional testing? Manual or automation testing? Are you going to execute all the test cases from your test management tool?
- Which bug tracking tool are you going to use? What will be the process when you find a new bug?
- What are your test entry and exit criteria?
- How will you track your testing progress? What metrics are you going to use for tracking test completion?
- Task distribution – Define the roles and responsibilities of each team member.
- What documents will you produce during and after the testing phase?
- What risks do you see in Test completion?
Test Strategy is not a piece of paper. It’s the reflection of all QA activities in the software testing life cycle. Refer to this document from time to time during the test execution process and follow the plan till the software release.
When the project nears its release date, it’s fairly easy to cut down on testing activities by ignoring what you have defined in the test strategy document. However, it is advisable to discuss with your team whether or not cutting down on any particular activity will help for release without any potential risk of major issues post-release.
Most agile teams cut down on writing strategy documents as team focus is on test execution rather than documentation.
But having a basic test strategy plan always helps to clearly plan and mitigate risks involved in the project. Agile teams can capture and document all high-level activities to complete test execution on time without any issues.
I’m sure that developing a good Test Strategy plan and committing to follow it will definitely improve the testing process and quality of the software. It would be my pleasure if this article inspires you to write a Test Strategy plan for your project!
If you like this post please consider sharing it with your friends!