Skip to content

Master test plan skeleton variant (template)

February 10, 2011

Here is described the sample of master test plan skeleton for any project.
It is based on IEEE and FURPS+.

Master test plan template

1. Introduction

1.1. Overview

Project to test overview in general

1.2. Purpose

This Test Plan document for the <Project Name> supports the following objectives:

Identify existing project information and the software components that should be tested.

List of recommended Requirements for test (high level)

Recommend and describe the testing strategies to be employed

List the deliverable elements of the test project

1.3. Scope

Describe the stages of testing (e.g. Unit, Integration) and the types of testing that will be addressed by this plan, such as Function or Performance

Provide a brief list of the target-of-test’s features and functions that will be or will not be tested.

List any assumptions made during the development of this document that may impact the design, development or implementation of testing.

List any risks or contingencies that may affect the design, development or implementation of testing.

List any constraints that may affect the design, development or implementation of testing.

2. Project requirements

The listing below identifies those items – use cases, functional requirements, and non-functional requirements – that have been indentified as targets for testing. This list represents what will be tested.

Enter a high level list of the major test requirements

3. Test strategy

The test strategy presents the recommended approach to the testing of the target-of-test. The previous section, Requirements for test, described what will be tested – this describes how the targe-of-test will be tested.

For each type of test, provide a description of the test and why it is being implemented and executed.

If a type of test is not appropriate for the target-to-test do not include it into test plan.

The main considerations for the test strategy are the techniques to be used and the criterion for knowing when the testing is completed.

3.1. Module A

Link to module or group of features test plan to simplify documentation and test maintains

3.4. Integration/system tests

Describe the way to implement project integration/system tests.

If using CI systems define which one.

3.5 Security tests

Describe whole project security tests process

3.6. Test process life cycle

Describe test process life cycle. Must be compatible with project development life cycle.

Here need to define which test levels (regression, new feature and reporting) and when should be started (e.g. when to launch new test iteration every new project build that means to launch regression tests and if it passed to fire new feature testing and so on)

3.7. Tools

The following tools will be employed for this project:


4. Deliverables

In this section, list the various documents, tools, and reports that will be created, by whom, delivered to who and when delivered.

4.1. Test results

Describe the method and tools used to record and report on the test results and testing status

4.2. Defect reporting

In this section, identify the method and tools used to record, track and report on test incidents and their status

One Comment
  1. It’s an amazing article for all the web viewers; they will get benefit from it I am sure.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: