In Software Testing, test strategy is a document describing how the software will be tested. Generally, it is developed for all levels of testing. Test Lead / Test Manager write the Test Strategy and review the strategy with the project team.

Also, please note that Test Plan may include test environment, risk assessment, test cases, conditions, pass / fail criteria and a list of related tasks.

The inputs of Test Strategy can be:

• Test Environment
• Test Tool data
• Project Schedule
• Defined Software Testing Standards
• Functional and technical requirements

An ideal Test Strategy must contain:

• Required hardware and software components details including test tools
• Roles and Responsibilities
• Software Testing methodology
• Limitations of the application

At the completion of this stage, testing team will be having following three documents:

• Test Strategy
• Test Plan
• Test Cases

All the above tasks collectively, called as Software Testing Methodology. This methodology can be used and molded as per the organizational needs.

Also See:

• Test Strategy - All Aspects
• Test Specification
• Testing Estimation
• Test Planning

SPONSORED LINKS

Search this site - within more than 167 pages of Software Testing