TEST PLAN

1. INTRODUCTION

A brief summary of the product being tested. Outline all the functions at a high level.

2. OBJECTIVES AND TASKS

●       Objectives

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

●      Tasks

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

3. SCOPE

● General

This section describes what is being tested, such as all the functions of a specific product, its
existing interfaces, the integration of all functions.

● Tactics

List here how you will accomplish items that you have listed in the “Scope” section. For
example, if you have mentioned that you will test the existing interfaces, what would be the
procedures 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. 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 in sufficient detail to permit identification of the major testing
tasks and estimation of the time required to do each one.
4.1 Unit Testing

Specify the minimum degree of comprehensiveness desired. Identify the techniques whic
judge the comprehensiveness of the testing effort (for example, determining which statem
Definition
executed at least once). Specify any additional completion criteria (for example, error fre
techniques to be used to trace requirements should be specified

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

Describe how the unit testing will be conducted. Who will write the test scripts for the un
Methodology
would be the sequence of events of the unit testing and how will the testing activity take

4.2 System and Integration Testing

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

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

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

4.3 Performance and Stress Testing

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

Who will be conducting Stress Testing on your project? List the individuals that will b
Participants
for this activity.
 Describe how Performance & Stress testing will be conducted. Who will write the tes
Methodology testing, what would be sequence of events of Performance & Stress Testing, and how
activity take place?

4.4 User Acceptance Testing

The purpose of the acceptance test is to confirm that the system is ready for operational u
Definition
acceptance testing, end-users (customers) of the system compare the system to its initial r

Participants Who will be responsible for the User Acceptance Testing? List the individuals’ names an

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

4.5 Automated Regression Testing

Regression testing is the selective retesting of a system or component to verify that m

Definition not caused unintended effects and that the system or component still works as specifie
requirements.

Who will be conducting Regression Testing on your project? List the individuals that
Participants
responsible for this activity.

Describe how Automated Regression Testing will be conducted. Who will write the te
Methodology testing, what would be sequence of events of Automated Regression Testing, and how
activity take place?

5. HARDWARE REQUIREMENTS

Computers:

● Architecture
All computer operating systems are designed for a particular computer architecture. Most
software applications are limited to particular operating systems running on particular
architectures. Although architecture-independent operating systems and applications exist, most
need to be recompiled to run on a new architecture. See also a list of common operating systems
and their supporting architectures.
 ● Processing power
The power of the central processing unit (CPU) is a fundamental system requirement for any
software. Most software running on x86 architecture define processing power as the model and
the clock speed of the CPU. Many other features of a CPU that influence its speed and power,
like bus speed, cache, and MIPS are often ignored. This definition of power is often erroneous, as
AMD Athlon and Intel Pentium CPUs at similar clock speed often have different throughput
speeds. Intel Pentium CPUs have enjoyed a considerable degree of popularity, and are often
mentioned in this category.
● Memory
All software, when run, resides in the random access memory (RAM) of a computer. Memory
requirements are defined after considering demands of the application, operating system,
supporting software and files, and other running processes. Optimal performance of other
unrelated software running on a multi-tasking computer system is also considered when defining
this requirement.
● Secondary storage
Hard-disk requirements vary, depending on the size of software installation, temporary files
created and maintained while installing or running the software, and possible use of swap space
(if RAM is insufficient).
● Display adapter
Software requiring a better than average computer graphics display, like graphics editors and
high-end games, often define high-end display adapters in the system requirements.
● Peripherals

6. 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 the system software, the mode of usage (for example, a standalone), and
any other software or supplies needed to support the test. Also specify the level of security which
must be provided for the test facility, system software, and proprietary components such as
software, data, and hardware.
Identify special test tools needed. Identify any other things for testing are needed (for example,
publications or office space). Identify the source of all needs which are not currently available to
your group.

7. TEST SCHEDULE
Include test milestones identified in the Software Project Schedule as well as all item transmittal
events.
Define any additional test milestones needed. Estimate the time required to do each testing task.
Specify the schedule for each testing task and the test milestone. For each testing resource (that
is, facilities, tools, and staff), specify its periods of use.

8. CONTROL PROCEDURES
 ● Problem Reporting

Document the procedures to follow 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 you are using an automated incident logging system, write those procedures in this section.

● 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 existing programs, these modules need to be identified.
 

9. FEATURES TO BE TESTED
Identify all software features and combinations of software features that will be tested.

10. FEATURES NOT TO BE TESTED

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

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

12. SCHEDULES

Major Deliverables

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

● Test Plan
● Test Cases
● Test Incident Reports
● Test Summary Reports

13. SIGNIFICANTLY IMPACTED DEPARTMENTS (SIDs)

 
Department/Business Area                     Bus. Manager                Tester(s)
 

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

15. 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. TOOLS
List tools you are going to use. List also the Bug tracking tool here.

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