A test Plan in software testing is a detail understanding of the system work flow like objective of system, scope, different requirement and testing strategies, schedule, roles and responsibility etc. Test Plan Template / test plan Format is as
Name of the Product-:
Prepared by -:
A brief summary of the product being tested
2.0 OBJECTIVES AND TASKS-:
Describe the objectives supported by the Master Test Plan, e g., defining tasks and
Responsibilities, document to be used as a service level agreement, etc.
List all tasks identified by this Test Plan, i.e., testing, post-testing, problem reporting, etc
This section describes what is being tested, such as all the functions of a specific product, its existing interfaces, integration of all functions.
4.0 TESTING STRATEGY-:
Describe the overall approach to testing
4.1 Unit Testing-:
Definition: Meaning and concept
Participants: Actual involved person
Methodology: How Unit testing is done
4.2 System and Integration Testing-:
4.3 Performance and Stress Testing-:
4.4 User Acceptance Testing-:
4.5 Regression Testing-:
4.6 Beta Testing-:
5.0 HARDWARE AND SOFTWARE REQUIREMENTS-:
Hardware used -:
E.g. -: Computers (Processor, Processor speed, Hard disk, RAM), Modems etc
Technologies used -:
E.g. JAVA, ASP.NET, PHP etc
6.0 TEST SCHEDULES-:
Estimate the time required to do each testing task. Specify the schedule for each testing task and test milestone. For each testing resource (that is, facilities, tools, and staff), specify its periods of use.
You can list the following documents:
– Test Plan
– Test Cases
– Test Incident Reports
– Test Summary Reports
|Contents||Est. Start Date||Est. End Date||Actual Start Date||Actual End Date||Total Delay Days|
7.0 RESOURCES/ROLES & RESPONSIBILITIES-:
Specify the staff members who are involved in the test project and what their roles are going to be (for example, Mary Brown (User) compiles Test Cases for Acceptance Testing). Identify groups responsible for managing, designing, preparing, executing, and resolving the test activities as well as related issues. Also identify groups responsible for providing the test environment. These groups may include developers, testers, operations staff, testing services, etc.
|S.N||Name of Employee||Roles /Responsibility|
8.0 CONTROL PROCEDURES-:
– Problem reporting
– Change request
9.0 FEATURES TO BE TESTED AND NOT-:
Identify all software features and combination’s of software features that will be tested and not to be tested.
Identify the high-risk assumptions of the test plan. Specify contingency plans for each
(For example, delay in delivery of test items might require increased night shift scheduling to meet the delivery date).
List the Automation or Manual tools you are going to use.
E.g. -: Selenium, Ranorex, JMeter, QTP etc.
Specify the names and titles of all persons who must approve this plan. Provide space for the signatures and dates.
Name Designation Signature Date