Test Plan Document



Introduction to Test Plan :

1. Test Plan ID : TPID -1

2. Introduction : The project involves  retail project. Where customers will register and use the credentials to login. With this login the user will be able to book the product, pay the amount through gateway or cash on delivery option can be opted.

3.Test Items : Home, User Registration, Order Tracking, Products Catalog.

4.Features to be tested : User Registration in shopping site.

5.Features not to be tested : Home, Order Tracking, Products Catalog in shopping site.

6.Test Approach : Test approach usually  refers to Test Strategy document, normally we design first the Test Strategy document. Hence Test Strategy document becomes integral part of Test Plan. Test Approach mostly covers the following concepts :

A.What will be the scope and objective of the testing Process followed in current project?

B.What kind of tests needs to be done for the application?

C.How the status reporting and communication is done?

D.What Test Delieverables needs to be handed over?

E.Any scope of the Automation in the current project, if so do the company havve resources?

F.What defect tracking tools do we need to use for tracking Defects?

G.What measurements and metrics that needs to be collected?

H.How much risk analysis is required?

I.How to track the change and configuration management tools if any required?

7.Test Environment : The environment the test plan is valid and the requirements of hardware and software to use in current project testing.

8.Entry Criteria :

A. Thorough understanding of Requirements in current project.

B.Establish test environment.

C.Software build has to be available.

9.Suspention Criteria :

A.Most critical defects detected In current project.

B.Test Environment becomes absolute.

C.More Minary defects are yet to be solved.

10.Exit Criteria :

A. The release cycle has been completed.

B. All kinds of expected tests applied.

C. Major defects has to be solved.

11.Test Deliverables : Test Cases, Automation scripts and Defect Reports.

12.Staff and Training needs : For the available team members, a training has to be conducted as per project requirements

13.Responsibilities : Responsibilities section mainly deals with individual responsibilities in their day to day activities and tasks they carry out for completion.

A. Prioritising the Features to be tested and which features not to test.

B. Making resources available at the schedule time.

C. Organize appropriate meetings to have proper communication between developement team and testing team.

D. Arranging Training needs for the team members.

14.Schedule : Schedule will contain the Planned and actual schedule.

15.Risks and Mitigation : Test Lead will analyse  the risks and overcome the Risks with Mitigation plan.

Few are some of the General risks for any project.

A. Lack of Budget.

B. Lack of Time.

C. Delays in Planned delievery.

D. Lack of communication and documentation.

E. Lack of Resources in the project.

16.Approvals : Approvals for project needs will be given by Test Lead and project manager.

17.Review Test Plan : After completing the test plan, the Test lead will conduct a review meeting in order to make sure the all the risks, testing wise coverage and requirement wise coverage.


Please enter your comment!
Please enter your name here