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. 

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.

TEST PLAN DOCUMENT

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

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

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, E.g., 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 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 acceptance test is to confirm that the system is ready for operational use. During 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 the 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. Hi Deepesh
    At my company we have worked with various customers, some of whom use traceability matrices, and I don’t think there is any standard format. Some populate tables by hand in MS Word specifications containing requirement tags for example.
    We prefer to auto-generate a requirements traceability matrix using an in-house tool (www.pixref.com), and there are other tools on the market. Our tool trawls through the specification and implementation files searching for requirement tags, and automatically lists which match and which do not.
    Cheers

  2. Guys,

    Does anybody have a Project Classification documents… i.e. project falls on which category, it’s small or medium project…. etc.

    Please send the documents to – karthik@when.com

    Thanks in advance!
    Karthik

  3. Hi

    I wish to know about Master Test Plan (Strategic Test Plan) and how is it different from the normal test-plan that is made for each level 1) unit testing 2) Integration Testing 3) System Testing and 4) Acceptance Testing?
    Is Strategic/ Master Test Plan ever made in Practical Testing Environment? Why is Master Test Plan necessary? How is it different from Actual Test Plan? What are the different Criteria that go into the making of Master Test Plan? Who is involved in Making a Master Test Plan? How many Years of work-expereince in required before a Test-Engineer starts designing a Master Test Plan? Kindly email me the reply to

    email id : subu_scorpio@yahoo.com

  4. Hi Anuradha,

    Wht you see is what the testplan contains. Still if you feel that you are not satisfied with that , then i would def provide you the real time testplan.

    Thanks,
    Santosh Palvai
    anybody can reach me @ santoshpalavi@yahoo.com

  5. I don’t know if copying chunks of text out of a well known standard is plaigarism, but at least citing it as a reference may make you look a little more legit.

    Best of luck.

  6. Hi friends,
    I am doing manual testing and performing load test by using jmeter test tool. can u tell me how to prepare the performance- load test report..

    with regards
    sundar

  7. ———————–
    3 Principal Test Documents
    ———————–
    1. Test Policy (Organisation Level)

    – Very High Level Document
    – What “Testing” means for organisation
    – How organisation measures test success
    – Relatively static document (Changes when organisation’s focus changes)
    – Developed by IT department

    2. Test Strategy (Programme Level)

    – Applicable for a Programme/System which covers multiple projects
    – Objective/Scope of Testing
    – Inscope/Out of scope Items for testing
    – Test Levels (Unit/Module/System/Integration)
    – Test Types ( Functional/Non-Functional)
    – Entry/Exit/Stop/Resumption Criteria for testing (for different Levels/Phases)
    – Risks to be addressed
    – Test Environment
    – Test case design methodology (Specification driven/BVA/EQ Parttition)
    – Test methodology ( Top-down/bottom-up/risk based)
    – Test Automation Approach
    – Test Tools to be used
    – Defect Management approach
    – Defect classification
    – Retesting & regression approach

    3. Test Plan (Project Level)

    – All above points specific for this project
    – Test Estimation & Test schedule
    – Test Organisation/roles/responsibilities
    – Test deliverables
    – Test reporting

  8. I want to know the following things regarding Test Plan.

    1. When preparation of test plan start?
    2. How the resource, deadline gets estimated? Is there any sceintific approach or any technique used for estimation of all this things?

    Plaes reply on this as I want to understand the testplan in detail.

    Thanks in advance.

    Vishal

  9. hi vishal

    Here are the answers for your questions

    1)Test plan should be started immediately after the requirements are available. It should be flexible enough so that if the requirements gets changed, then the plan should also be changed accordingly
    2)a)Scheduling is based on the project deadlines.
    b)Resource estimation is based on the project size. In general QA resources are half the development team size. Also you need to prepare Staffing matrix which can give you idea of how many resources are required for a particular module. For example, if there are 3 modules in a project then you can hire 3 persons, one for each module. Similarly you can also categorize by type of testing.

  10. Guys

    Can you please send me the template to do estimation using Test Point ANalysis. Harpeet or George, I see you both discussing on this as well.

    Thanks
    Selvan

  11. any one tell me.

    1) What is diff b/n unit testing and white box testing(WBT) and it have any related link and WB tester can test the unit testing and voice versa?.

    2)how can test acceptance testing without alpha and beta testing(that is end user)

  12. Hi Anadhan,

    1. Unit testing is usually done by developers where they will be testing every function point/unit which they are developing before it is being integrated to other application. White box testing can be conducted by a developer or a tester, white box testing is conducted with the motive of identifying/pointing a defect/bug exactly where inside the code.

    2. Alpha testing is usually called first phase of testing, where it will be tested within the project team like unit testing, FVT (functional verification testing), system testing. Beta testing is the one executed along with the end user, usually called User Acceptance Testing or Certification testing. It cannot be executed without the end user.

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

  14. Hi,

    I wants to know about the Certification in software testing for beginners??

    Its duration,fees,how to apply,which website provide online training for the same.

  15. Hi friends,

    I advised to freshers like me… this is pretty site for learning Testing…
    I thank to who establish this site.

    Regards,
    Somanthan R.

  16. @ Rupali,

    There is no difference between Functional and functionality testing. They are having same meaning To Test the functionality of the system.

  17. hi how to plan write the test cases in iam workig on mannual testing how can i start the test process iam new in testing please

  18. hi,
    i am planning to do software testing course from long back.but i am still confusion to see lots of test…what will be the best for me.just i want get a job any how , can i do both manual and automation? what is the difference? or shall i concentrate testing course.plz szst me what will ve to do to find the testing job.
    thanks

  19. Hi Satya, Go through requirements and understand the changes in the application. Download a simple test plan template and put your scope and test strategy in that test plan. For preparing test cases, understand the flow of the application and bring in to your imagination for different kind scenarios how application works, and start your test cases putting those scenarios in to as test cases. Let us know any one of here if you need any clarification. Writing test case is an art, build that skill within you and I am sure you will enjoy writing test cases.
    Thanks,
    Viswanathan D
    dviswa@gmail.com

  20. Hi Divya,

    When you come across a defect and if it does not have a test case, then you need to update your test case accordingly through following change test case process. A defect need to have test cases, please tell this answer in your next interview.

    Thanks,
    Viswanathan D
    dviswa@gmail.com

Leave a Comment