Test Strategy

Test Strategy document is the high level document which is defined the Software Testing Approach  and designed by the Project Manager. Test Strategy document derived from the Business Requirement and Specification Requirement. 

This document is static document and can't change too often. Once Project Manager develop the Test Strategy then this strategy generally company used for several project. If Software is small then Test Strategy is the part of Test Plan otherwise Test Strategy document should be separated for big projects.

Test Strategy document describe the Testing Approach following by the Testing team. Following are the parts of the Test Strategy.

• Scope and Objective: The objective as per the Business and the scope is how much testing is needed for the software.

• Business Issues: In Business issue part, we manager describe the how much time needed, what is the cost, what new resources need to perform testing. 

• Testing Approach: in Testing approach, Manager describe that the what type of testing needed like it needed functionality, UI, Regression, Load, Performance. It also describe that the testing we needed only Manual or we need Automation too for the project.

• Test Deliverable: In this document Manager describe the all the documents that needed in testing. 

• Roles and Responsibilities: In this part, manager describe the all team members roles and assign their responsibilities. 

• Communication and Status Report: It include the document of communication and status report sending between the two teams like if any build send from developer team to test team and bug report send from test team to team lead etc.

• Test Automation and Tools: It include the availability of the automation tools and the purpose for the Automation Testing. 

• Defect Reporting and Tracking: It include that which defect tool or tracking tool needed for communication between the development team and the teasing team.

• Change and Configuration Management: It include that how to handle the sudden changes if client want some changes in between of the software development.

• Training: It include the training part if some new or complex module introduce in the software development and testing team needed to learn some new tool that are important.

Apart from the part of Test Strategy, following are type of Test Strategy

• Analytical
• Risk Based Test Strategy
• Requirement Based Test Strategy
• Model Based Test Strategy
• Methodical Test Strategy
• Process Compliant Test Strategy
• Dynamic Test Strategy
• Consultative and Directed Test Strategy
• Regression Averse Test Strategy