Sample Test Plan Document (Test Plan Example With Details Of Each Field)

Do you wish to learn and download a Sample Test Plan? This tutorial is in response to those who have requested for a Test Plan example.

In my previous tutorial, I have outlined the Test Plan Index. In this tutorial, I will elaborate on that index with more details.

A Test Plan reflects your entire test schedule and approach.

=> Click Here For Complete Test Plan Tutorial Series


This includes the purpose of a Test Plan i.e scope, approach, resources, and schedule of the testing activities. In order to identify the items being tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, the risks associated with this plan, etc.

I have included the link to download a PDF format of this Test Plan example at the end of this post.

Sample Test Plan

(Name of the Product)

Prepared By: 
(Names of those who Prepared)



2.1 Objectives
2.2 Tasks


4.0 Testing Strategy
4.1 Alpha Testing (Unit Testing)
4.2 System and Integration Testing
4.3 Performance and Stress Testing
4.4 User Acceptance Testing
4.5 Batch Testing
4.6 Automated Regression Testing
4.7 Beta Testing

5.0 Hardware Requirements

6.0 Environment Requirements
6.1 Main Frame
6.2 Workstation

7.0 Test Schedule

8.0 Control Procedures

9.0 Features to Be Tested

10.0 Features Not to Be Tested

11.0 Resources/Roles & Responsibilities

12.0 Schedules

13.0 Significantly Impacted Departments (SIDs)

14.0 Dependencies

15.0 Risks/Assumptions

16.0 Tools

17.0 Approvals

Note: This Test Plan is provided as a PDF. For maximum flexibility, consider using a web-based test management tool like TestRail to develop your test plans.

Let's explore each field in detail!!


It is a brief summary of the product that is being tested. Outline all the functions at a high level.


2.1 Objectives
Describe the objectives supported by the Master Test Plan, For Example, defining tasks and responsibilities, a vehicle for communication, a document to be used as a service level agreement, etc.

2.2 Tasks
List all the tasks identified by this Test Plan, i.e., testing, post-testing, problem reporting, etc.


General: This section describes what is being tested, which is new to all the functions of a specific product, its existing interfaces, integration of all functions, etc.

Tactics: List here about how you will accomplish the items that you have listed in the “Scope” section.

For Example, if you have mentioned that you will be testing the existing interfaces, what would be the procedures that you would follow to notify the key people to represent their respective areas, as well as allotting time in their schedule for assisting you in accomplishing your activity?


Describe the overall approach to testing. For each major group of features or feature combinations, specify the approach which will ensure that these feature groups are adequately tested.

Specify the major activities, techniques, and tools which are used to test the designated groups of features.

The approach should be described with sufficient details to permit the identification of the major testing tasks and estimation of the time required to do each one.

4.1 Unit Testing

Definition: Specify the minimum degree of comprehensiveness desired. Identify the techniques which will be used to judge the comprehensiveness of the testing effort (For Example, determining which statements have been executed at least once).

Specify any additional completion criteria (For Example, error frequency). The techniques to be used to trace requirements should be specified.

Participants: List the names of the individuals/departments who would be responsible for Unit Testing.

Methodology: Describe how unit testing will be conducted. Who will write the test scripts for Unit Testing, what would be the sequence of events of Unit Testing and how will the testing activity take place?

4.2 System and Integration Testing

Definition: List what is your understanding of System Testing and Integration Testing for your project.

Participants: Who will be conducting System and Integration Testing on your project? List the individuals who will be responsible for this activity.

Methodology: Describe how System & Integration testing will be conducted. Who will write the test scripts for Unit Testing, what would be the sequence of events of System & Integration Testing, and how will the testing activity take place?

4.3 Performance and Stress Testing

Definition: List what is your understanding of Stress Testing for your project.

Participants: Who will be conducting Stress Testing on your project? List the individuals who will be responsible for this activity.

Methodology: Describe how Performance & Stress Testing will be conducted. Who will write the test scripts for testing, what would be the sequence of events for Performance & Stress Testing, and how will the testing activity take place?

4.4 User Acceptance Testing

Definition: The purpose of the acceptance test is to confirm that the system is ready for operational use. During the Acceptance Test, end-users (customers) of the system compare the system to its initial requirements.

Participants: Who will be responsible for User Acceptance Testing? List the name of the individuals and their responsibility.

Methodology: Describe how User Acceptance testing will be conducted. Who will write the test scripts for testing, what would be the sequence of events of User Acceptance Testing, and how will the testing activity take place?

4.5 Batch Testing

4.6 Automated Regression Testing

Definition: Regression testing is the selective retesting of a system or a component to verify that the modifications have not caused unintended effects and that system or component still works as specified in the requirements.

4.7 Beta Testing



6.1 Main Frame
Specify both the necessary and desired properties of the test environment.

The specification should contain the physical characteristics of the facilities, including the hardware, the communications, and system software, the mode of usage (For Example, stand-alone), and any other software or supplies that are required to support the test.

Also, specify the level of security that must be provided for the test facility, system software, and proprietary components such as software, data, and hardware.

Identify the special test tools that are required. Identify any other testing needs (For Example, publications or office space). Identify the source of all needs which are not currently available to your group.

6.2 Workstation


Include all test milestones identified in the Software Project Schedule as well as all item transmittal events.

Define any additional test milestones required. 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.


Problem Reporting
Document the procedures to be followed when an incident is encountered during the testing process. If a standard form is going to be used, attach a blank copy as an “Appendix” to the Test Plan.

In the event that you are using an automated incident logging system, write those procedures.

Change Requests
Document the process of modifications to the software. Identify who will sign off on the changes and what would be the criteria for including the changes to the current product.

If the changes will affect the existing programs, then these modules need to be identified.


Identify all the software features and combinations of the software features that will be tested.


Identify all the features and significant combinations of features that will not be tested along with the reasons.


Specify the staff members who are involved in the Test Project and what are their roles going to be (For Example, Mary Brown (User) compile Test Cases for Acceptance Testing).

Identify the groups responsible for managing, designing, preparing, executing, and resolving the test activities as well as related issues.

Also, identify the groups responsible for providing the test environment. These groups may include developers, testers, operations staff, testing services, etc.


Major Deliverables: Identify the deliverable documents. You can list the following documents:

  • Test Plan
  • Test Cases
  • Test Incident Reports
  • Test Summary Reports


Department/Business Area Bus. Manager Tester(s)


Identify significant constraints on testing, such as test-item availability, testing-resource availability, and deadlines.


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).

16.0 TOOLS
List the Automation tools that you are going to use. Also, list the Bug tracking tool here.


Specify the names and titles of all the persons who must approve this plan. Provide space for the signatures and dates.

Name (In Capital Letters) Signature Date:


Download: You can also Download this Sample Test Plan Template here.

We have also prepared a real Live Project Test Plan from this sample.

You can check and download it on the following tutorials:

  1. Simple Test Plan Template
  2. Test Plan Document (Download)

=> Visit Here For Complete Test Plan Tutorial Series

Recommended Reading

165 thoughts on “Sample Test Plan Document (Test Plan Example With Details Of Each Field)”

  1. “why we should prepare system & integration test plan?”

    First, System test plan is prepared to make our self ready to prepare the entire system which is being developed from the scratch. System test plan is prepared only if the application or product is completely new. And the application or product need to undergo all type of testing like Functional, Performance, Load, Certification, UAT etc.
    Second, Integration test plan is prepared if a product or application being developed by several team or several developers and if one complete module output is going to be as a input for another module, then this Integration Test Plan will be useful to plan accordingly. So when two systems being integrated the possibilities of issues are like software compatibility, input variable map etc. So these needs to be tested completed when its integrated. Hope its clear now.

    D. Viswanathan

  2. Thanks for guiding me. My another query is under which circumstances do we prepare unit ,integration & system test plan

  3. “Unit Testing”

    Unit Testing is usually done by developers, they don’t prepare exact test plan for Unit Testing. They will write high level test cases where the scope of the testing will be limited to within their module or functionality undergone changes. Unit Testing/White Box Testing is also done by experienced Test Engineers who has knowledge on coding in the respective platform. Unit Testing executed by testers are mostly to show the defect where exactly in the code it is affected.

  4. Hi,

    I want to know how to get a job in s/w testing. I have 5+ years of s/w deveopment experience and after that I took a 6 year break from IT to handle family responsibilities. Now I want to comeback in IT field but not in the development. I feel testing/quality area would be little less consuming than mainstream development. Correct me if I am wrong.
    Can anybody send me details about testing job, some reading material and courses which can help getting a job in today’s demanding job mkt.

  5. Hi,
    Thanks a lot for the detailed test plan template.
    I would like to know the test strategy how to apply.
    And test estimation techniques.

  6. hi,would you please suggest me some basic techniques for preparing an idea of test plan for car manufacturing?
    thanks alot


  7. preethi just put 6 month live project Experience in Testing recognized Training center or take One year fake Experience
    No problem ……….

  8. Hiii,

    First of all thanks…:), i found this site is very useful… Please send me some real time example of test cases & test data on my email..

  9. @ Pallavi

    Both severity and priority are related with bug.
    Severity shows “How sever Bug is” (i.e. if there is any bug found in any functionality then how it is impacting on system)
    Priority shows “Urgency of fixing the bug” (i.e. Seeting the priority for solving the bug, if any bug is more sever then it should be fix first.)
    There are levels of severity and Priority.
    Severity: Catastrophic, Sever, Medium, Low
    Priority: Blocker, High, Medium, Low

  10. What do you think are the advantages/disadvantages of having separate unit,
    integration, and system test plans as opposed to an inclusive test plan that contains
    all three in the same document?

  11. Thank you for such a nice post very helpful.

    But what I want to know who work on Test Plan means Who make it. I am sure this is a work of QA Lead so my question is that WHETHER THE TEST PLAN CONTAINS THE NAME OF QC EXECUTIVE MEANS WHICH SOFTWARE TESTER WILL DO WHAT?

  12. Sir i am new in this field, so i just want to know from where should i start learning software testing.
    Please help me.

    Best Regards,
    Aman Agrawal

  13. Hey there! I simply would like to give you a huge thumbs up for your excellent info you’ve got right here on this post. I am coming back to your web site for more soon.

  14. Hi am i interesting in s/w testing field doing now manual testing and future which testing useful and weather information sharing for me..

  15. Hi,
    Please can any one of u tel how to apply for ISTQB certification? Is there any course given for that?Where is it?
    Please give me details about ISTQB because i dont ve any idea. Please.


  16. Hey guys, anyone can help me? i’m struggling with my system documentation :( please send me an realtime testing documentation of a sales and inventory system :(
    i will look after to that please help me :(

  17. Hi Guys,

    Anyone can help me? i need E Commerce based test plan document. If any one having please send me. this is my email id “”


Leave a Comment