What is the difference between Test Strategy and Test Plan?
Posted By Lax on March 06th, 2009 in Manual Interview Questions
Test Strategy and Test Plan are completely different from one another. Here is the difference between them.
Test Strategy: Test Strategy defines an approach to be followed by testing team n current project.
OR
Test Strategy is a organization level document which is common for all the projects in the organization with small customizations. It will explain the process you will follow in the current project to the out side world or clients.
Test Plan: Test Plan is a project level document which is used for testing a specific project.It will contain the following details…
- Test plan ID
- Introduction about the project
- Test Item (List of modules or features in project)
- Features to be tested
- Features not to be tested
- Test approach (Nothing but Test Strategy)
- Test Environment (Systems and network)
- Entry Criteria
- Suspension Criteria
- Exit Criteria
- Test Deliverable at the time of project closure
- Staff and training needs
- Responsibilities of team members
- Schedule
- Risks and Assumptions
- Approvals from managers
Similar Posts:
This post has one comment
May 15th, 2011
ok i agree to this difference but from other source i find that there is the Test Strategy is normally derived from the Business Requirement Specification document.while The Test Plan document on the other hand, is derived from the Product Description, Software Requirement Specification SRS, or Use Case Documents.
The Test Plan document is usually prepared by the Test Lead or Test Manager and the focus of the document is to describe what to test, how to test, when to test and who will do what test.
can any clear this.
thanks & regards
Ajay Mishra