Test Plan

Test Plan is the document describing the scope of the software, approaches that will be used to develop the software, resources which are available and schedule to perform these testing activities. 

Test Plan is the document which helpful for all the team member ( it may be Test Team, Developer Team, Business Team or even Customers) to understand the software. Test plan is the document which determine the efforts that team used to work over the software.

A Test Plan document is a strategy that will be used to verify that the software meets their design specification and other requirement. A Test Plan is prepared by the Test Engineers.

As per IEEE 829 documents following are the part of Test Plan(Source Wikipedia).

• Test Plan Identifier: It is an Unique number that provide to the document. This is a number for future reference to identify the Test Plan. This number is connected with the Configuration Management System).

• Test Introduction: The Test Introduction contains the detailed understanding of the software, workflow, objective, Scope of Testing, Schedule, Test Deliverable, Release Criteria and risk of the Software.

• Test Items: A Test item is the software and it's version which is under Test.

• Featured to be tested: In this part, We include all the features of the software which will be test. These features can be identifies from the design specification and the requirement. 

• Featured not to be tested: In software some features are also there those not needed to tested. In this part we documented all those featured which are not needed to tested and provide a reason also along with the feature to ensure that why these features not to be tested.

• Test Approach: In this part, Test team document the overall Testing approach that they will used for testing the software. This include that how testing will be carried out. 

• Item Pass/Fail Criteria: This part include in the document that weather the software item pass or fail in Test. 

• Suspension Criteria and Resumption Criteria: In Suspension criteria , Test team should include the criteria where we need to suspend all the Test activities while Resumption Criteria specify when testing can resume after the suspension. 

• Test Deliverable: In Deliverable, we deliver which are in the testing part like Test Data, Test Strategy, Test Case Document, Test Result, Test Execution Report and Test Summery Report.

• Testing Tasks: This part contains the all tasks for Planning and execution of Test Cases.

• Environmental Needs: In this part, we documented all environment that needed for testing like Hardware requirement, Software Requirement, Network. OS and Tool Required. 

• Responsibilities: In this part, we describe the responsibilities for each and every team member (Project Team Lead, Testing Manager, Test Designer, Tester, Reviewer). 

• Staffing and Training Needs: In this part, we describe the staffing as per the his/her quality and provide any training if any training need for that Software.

• Schedule: In this part, we describe the dates of delivery and dates of each modules of finish as per deadlines.

• Risks: In this part, we describe all high level risks and provide any mitigation plan for those risks.

• Approval: In the part, we describe all the person who approve the plan with signature and date.