Test Plan v/s Test Strategy

Test Plan v/s Test Strategy

Test Plan:

1.Test plan document is a document which contains the plan for all the testing activities to be done to deliver a quality product

2.It is designed by test lead or test manager

3.It is a dynamic document. It can be changed

4.It is defined at project level

Steps for Preparing test plan document:

As soon as Product Description, SRS or Use Case document are ready test lead will concentrate on test planning and will prepare the test plan document

Test plan document involves below process steps:

a. Team formation: Test plan process starts with testing team formation. In this stage test lead depends on below stated fac tors

>Size of the project

>Available test duration

>Available testers on bench

>Availability of the test resources(testing tools)

b.Identifying tactile risks:

After completion of test team formation, test lead concentrates on risks identification and analysis

Risks: 1.Lack of domain knowledge to testers

2.Lack of time

3.Lack of resources

4.Lack of communication

c. Prepare Test Plan:

Once done with team formation and risks analysis,Test lead will design test plan document and contains below furnished features:

1. Test Plan Identifier
2. Introduction
3. Features(or) Test items
4. Features to be tested
5. Features not to be tested
6. Test approach
7. Test environment
8. Entry criteria
9. Suspension criteria
10. Exit criteria
11. Test deliverables
12. Staff and Training needs
13. Roles and Responsibilities
14. Schedule
15. Risks and assumptions
16. Approvals

d.Review test plan:

Once test plan document designing completes,the corresponding test lead will take approval from PM and then test lead communicate with team in current project regarding test plan

Test Strategy:

1.Test Strategy is a high level document which captures the approach on how we go about testing the product and achieve the goals.

2.It is designed by the project manager

3.It is a static document. Once defined, it cannot be changed

4.It is defined at organization level and can be used for similar kind of projects

Test strategy document furnished with the below features:

1. Scope and Objective
2. Business Issues
3. Test responsibility matrix
4. Requirement traceability matrix
5. Roles and Responsibilities
6. Communication and status reporting
7. Need for test automation
8. Defect Reporting and Tracking
9. Configuration management
10. Test metrics
11. Environment requirements
12. Industry standards to follow
13. Risks and assumptions
14. Training plan