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 that index with more details.

A Test Plan reflects your entire test schedule and approach.

TEST PLAN DOCUMENT

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)
(Date)

TABLE OF CONTENTS (TOC)

1.0 INTRODUCTION

2.0 OBJECTIVES AND TASKS
2.1 Objectives
2.2 Tasks

3.0 SCOPE

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.


Recommended Tool

TestRail

testrail logo

In addition to recording details like test steps and expected results, TestRail helps organize testing efforts and get real-time insights into testing activity.

You can track the status of individual tests and measure progress with informative dashboards and activity reports. Compare results across multiple test runs, configurations, and milestones.

Monitor team workload to adjust assignments and resources, and work more productively with personalized to-do lists, filters, and email notifications.

=> Learn more about TestRail and get a free 30-day trial on their website


Let's explore each field in detail!!

1.0 INTRODUCTION

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

2.0 OBJECTIVES AND TASKS

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.

3.0 SCOPE

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?

4.0 TESTING STRATEGY

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

5.0 HARDWARE REQUIREMENTS
Computers
Modems

6.0 ENVIRONMENT REQUIREMENTS

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

7.0 TEST SCHEDULE

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.

8.0 CONTROL PROCEDURES

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.

9.0 FEATURES TO BE TESTED

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

10.0 FEATURES NOT TO BE TESTED

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

11.0 RESOURCES/ROLES & RESPONSIBILITIES

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.

12.0 SCHEDULES

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

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

13.0 SIGNIFICANTLY IMPACTED DEPARTMENTS (SIDs)

Department/Business Area Bus. Manager Tester(s)

14.0 DEPENDENCIES

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

15.0 RISKS/ASSUMPTIONS

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.

17.0 APPROVALS

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:

1.
2.
3.
4.

**************************

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)

Recommended Reading

163 thoughts on “Sample Test Plan Document (Test Plan Example with Details of Each Field)”

  1. thanks
    I gain idea about the basic test plan requirements. can you please provide me any basic application or system test plan example which is implemented in software companies, so that we get clear idea about the test plan ?

  2. thanks
    i found the test plan which is very easy and understandable…
    can you please provide me bug tracking report format , so that i get how to submit bug to developer

  3. hi,
    i am planning to do software testing course from long back.but i am still in confusion which institute will be the best in bangalore. and which institute is giving placement assistance? can i do both manual and automation? what is the difference? pls let me know which will not involve programming. i dont want to get into programming.pls let me know which will suit me. or shall i concentrate only in one course.either manual or automation. thanks.

  4. @ manjunath – Thanks for making me to write article on Bug life cycle (https://www.softwaretestinghelp.com/bug-life-cycle/) This is actually base for my next article “Writing a good bug report”. I will write it soon.

    @ anjana – If you don’t want to go for Programming language then its useless to think about Automation testing. So you have only one option of Manual testing which may restrict your career.

    @ sricharan – Diff. In short- Test strategy describes the overall testing approach i.e how to test? Test strategy comes under test plan.
    Test plan defines Scope, approach and what to test?

    @ reddy – traceability matrix is used to map the user requirements with the deliverables. We can use traceability matrix for mapping user level requirements to functional requirements and also for verifying system specifications. You can use a simple excel sheet having two columns of requirement and traceability to maintain traceability matrix.

  5. Hi
    Still this is more usefull than the other ones but it’s great if you all can provide us template in dco or excel format.

    Thank you

  6. *If my earlier message was posted please disregards this*
    Above template of the test plan was very useful.
    I am required to create an automation test plan.It would be very helpful if i can get a template of this automated test plan.
    Thanks in advance.
    JAS

  7. Hi

    I am pavani and have recently joined as tester. Presently I am testing a web based application where in I am assigned to do Funcional testing., I have some questions like

    1)is there any format we need to follow to prepare TRM
    2) how do we create Test beds for automating test cases?

  8. Hi Kavitha,

    Static Testing: Testing the application without running the application. Nothing but testing the Documents like Business Requirement Specification, Functional Specifications and other testing documents whether the mentioned requirements and functionalities are complete or not. Ex: Testing the documents Test Case document for checking whether it covers the full functional flow of the applications or not.

    Dynamic Testing: Testing the application by running it currently. Ex: Testing the applications whether it meets all the functionalities mentioned in the Functional Specifications by running the Test Cases which are generated against the Requirements of the client.

  9. Hi Venky,
    thank you for your reply. . .
    may i know the differnce between test strategy and test plan. . does test strategy comes within test plan?

  10. I am not from s/w dev background; i am basically from quality assurance; can i get involved in software testing? what are the pre requisites .

  11. Hi
    I AM HANSAL. LOOKING FOR A JOB IN TELECOM SOFTWARE TESTING FIELD. SO CAN ANYBODY GIVE ME SOME WEBSITES WHERE I CAN GET SOME GOOD PROJECTS .PLEASE HELP ME . I NEED SOME PROJECT DETAIL OF GSM,UMTS .

  12. Hi,Can anybody pls let me know “what is the actual need for test strategy when there is test Plan?”Why is test plan needed?

  13. hi i am sethuraman, presently i am doing a software testing courses in STC. I like to do some projects related in automation tools of Winrunner and QTP. thereby i am in need of some sample SRS. if u have any relevant SRS, send to me, thereby its useful to do some projects.

    Same time, can u give a weblink to take a model online exams in software testing.

  14. Hi Vijay,
    I like the web-site very much. It is very useful.
    What I understand is that different interpretations are given by different professional :
    E.g :
    Test Strategy & Test Plan

    Test Strategy may be a higher level document where in it may contain various Test Plans (Strategy may include plans for integration testing, system testing, user acceptance testing, etc)

    E.g : Static Testing

    When I go through articles under static testing the entire life cycle activities such as various reviews, audits, etc are covered.

    I get confused. Is there any standard where in specific definitions are given so as remove ambiguity.

    Can you please define a role of QA in a Software Testing Service Orgn?

    Thank you for your immence service. Like to interact more.

    Regards
    Nagesh

  15. Can anyone help me regarding switching the software comapny.I want to know if anyone has experince in Junit and manual testing after 2 yrs of experience in software industry,is his knowledge enough to switch or need to gain more and then switch.

  16. Can anyone help me out with the templates for load testing, capacity planning and volume testing…??

    I need to knw the difference between them also..

  17. Hi,

    Test Plan : It contains all (like Introduction, scope, s/w req. h/w req, ,…etc…).
    But it is not necessary that all should be followed in TEST STRATEGY for any of the new project, where we can modify according to the Client or Project requirements.

    TESTPLAN: It is the set of rules made for the company
    TEST STRATEGY:By Modifying the testplan according to the Client, TEST STRATEGY comes into picture, here we may not follow all the rules. If you have still any doubts oe related to Manual testing., you can contact me @santoshpalvai@yahoo.com..

    Hope so, it cleared ur doubt..

  18. Hi, My email Id is kalraharpreet@gmail.com

    Please send me different type of template to do TPA if you have different. Or If you can also send me the templates to have the High Level Estimations of Tsting…

    I really Appreciate.

    Thanks,
    Harpreet

  19. Hi Sujatha,

    Test Plan : It contains all (like Introduction, scope, s/w req. h/w req, ,…etc…).
    But it is not necessary that all should be followed in TEST STRATEGY for any of the new project, where we can modify according to the Client or Project requirements.

    TESTPLAN: It is the set of rules made for the company
    TEST STRATEGY:By Modifying the testplan according to the Client, TEST STRATEGY comes into picture, here we may not follow all the rules. If you have still any doubts oe related to Manual testing., you can contact me @santoshpalvai@yahoo.com..

    Hope so, it cleared ur doubt..

  20. I don’t know how to write scope for integration testing Besides, I somehow mix the objectives with acceptance criteria. Could anyone clear me about those please?

    Thanks in Advance

  21. I have done my B.Sc.(Chemistry). & also done my software testing diploma in SQTL. I am fresher & wants jobs in testing.
    But please request to my all friends dont join SQTL.
    Because they dont have any placement. Don’t join SQTL.
    Don’t join SQTL.

  22. Test Plan and Test strategy documents are extremely important in any project. Both documents are usually frozen at the beginning of the test engagement, but do under constant changes and revisions. We can call both documents to be live documents.

    The basic difference between the two is as below:

    Test plan is a document that contains list of activities that would be a part of testing the application (AUT). A test plan contains the following details:

    1.Details on the Environment
    2.Details on the application and Scope of Testing
    3.Different phases of testing involved in the test project:
    i. Unit Testing – Responsibility & Exit criteria
    ii. System Testing – Responsibility & Exit criteria
    iii. Integration testing – Responsibility & Exit criteria
    iv. UAT / Business User Testing – Responsibility & Exit criteria
    4. Environment Cycle plan & Batch calendar plan
    5. Resource Requirement across each phases of testing
    6. Test Deliverables
    7. Test team skills, requirements, roles & responsibilities.
    8. Details on resource ramp up and ramp down
    9. Details of the availability of hardware and support software requirement.
    10. Details on training needs
    11. Risks and mitigation
    12. Contingency plan

    Test Strategy – Test Strategy is a document that talks about how the testing is to be carried out across each phase. Take for example, in Unit testing phase test strategy would define entry and exit criteria along with ways and means of how the module would be unit tested. Test Strategy would vary from phases to phase since same strategy cannot be followed for two phases keeping in mind no two phases of testing are similar.

    So, eventually Test Plan is a parent document the contain test strategy as a child document.

    The perception of test plan and test strategy would vary from organization to organization and even project to project.

    Regards,
    Arun
    http://www.focustesting.com

Leave a Comment