Test Plan Template .doc

8/10/2019 Test Plan Template .doc

1/6

[I[INSERTNSERTPPROJECTROJECTNNAMEAME]]

TEST PLANTEST PLAN

EXECUTIVESPONSOR [INSERTNAME]

BUSINESSOWNER- [INSERTNAME]

PROJECTMANAGER [INSERTNAME]

ORIGINALPLANDATE: [INSERTDATE, SPELLEDOUT]

REVISIONDATE: [INSERTDATE, SPELLEDOUT]

REVISION: [INSERTNUMBER]


2/6

OVERVIEWOVERVIEW

PROJECT OBJECTIVESPROJECT OBJECTIVESBriefly describe the business objectives and background of the system being

tested.

SYSTEM DESCRIPTIONSYSTEM DESCRIPTION

Briefly describe the system and the functions it is intended to perform.

PLAN OBJECTIVESPLAN OBJECTIVES

Briefly describe the objectives of the Project Test Plan, e.g., defining

responsibilities, identifying test methodologies and phases, identifying the testenvironment, etc. Explain how the plan might evolve throughout the project

lifecycle.

REFERENCESREFERENCES

dentify any sources of information used to develop this plan. nclude documents

which define and trace the system re!uirements to be tested, e.g., a "e!uirements#pecification or a "e!uirements Traceability $atrix.

OUTSTANDING ISSUES, ASSUMPTIONS, RISKS ANDOUTSTANDING ISSUES, ASSUMPTIONS, RISKS AND

CONTINGENCIESCONTINGENCIES

#tate any project planning issues or problems relevant to testing which are known

as of this plan revision. %escribe the effects of such issues on test planning and

identify any contingencies to mitigate risk.

Page &


3/6

TEST SCOPETEST SCOPE

FEATURES TO BE TESTEDFEATURES TO BE TESTED

#pecify all features and combinations of features which will be tested. This could

include items such as user manuals or system documents. 'lso included shouldbe some description of the expected successful performance of tested features.

FEATURES NOT TO BE TESTEDFEATURES NOT TO BE TESTED

#pecify all features and significant combinations of features which will not be

tested. Explain the reasons for excluding these features from testing.

TEST METHODOLOGIESTEST METHODOLOGIES

TESTING APPROACHTESTING APPROACH

(or each major group of features or feature combinations, specify the types of

tests re!uired, e.g., regression, stress tests, pilot tests, etc. #pecify the majoractivities, techni!ues, and tools which are used to test the designated features.

This section should also include a high level description of how the testing shall

be conducted, i.e., independent contractors, in)house staff, where testing to occur,

etc.

TEST DATATEST DATA

Provide a general description of the sources of test data. %escribe how the range

of test data will help to ensure the ade!uacy of testing, e.g., selection of boundary

or null values.

TEST DOCUMENTSTEST DOCUMENTSdentify tests documents which are created throughout the project lifecycle.

nclude more specific documents such as test cases, acceptance test plans,integration test reports, etc.

Page *


4/6

REUIREMENTS VALIDATIONREUIREMENTS VALIDATION

Explain how tests and test results will be mapped to documented systemre!uirements. %escribe the procedure for ensuring that re!uirements are

validated.

CONTROL PROCEDURESCONTROL PROCEDURES

%escribe the procedure for identifying, recording, and tracking test results to

closure. %ocument the change control procedure. nclude classification code and

prioriti+ation scheme for error tracking and resolution. #pecify the trackingmechanism for tests results test case validation log-test error log.

TEST PHASESTEST PHASES

dentify test phases, such as unit, integration, system, acceptance, and prototype testing.(or each phase, address the topics described below.

DEFINITIONDEFINITION

Provide a brief description of the process scenario involved in performing theactivities in the phase.

PARTICIPANTSPARTICIPANTS

dentify the person or group responsible for conducting this test phase. %escribe

the expected level of involvement of the project team, test group, and any other

functional areas.

SOURCES OF DATASOURCES OF DATA

Provide a more detailed description of the source and type of data for this test

phase.

ENTRANCE AND EXIT CRITERIAENTRANCE AND EXIT CRITERIA

#pecify the entrance and exit criteria for this phase. %escribe how test results areevaluated. Explain the criteria for test sufficiency. nclude criteria for test

suspension and resumption.

Page /


5/6

REUIREMENTSREUIREMENTS

dentify re!uirements which are validated in this phase.

WORK PRODUCTSWORK PRODUCTS

%escribe the work products which are initiated and-or completed in this phase,including test documents and reports.

TEST COMPLETION ACCEPTANCETEST COMPLETION ACCEPTANCE

%escribe the criteria for acceptance of the completion of the test results should be

tied into the 0' plan of the project product. 1hen is the test complete2

TEST ENVIRONMENTTEST ENVIRONMENT

HARDWAREHARDWARE

%escribe the hardware re!uirements for the test environment.

SOFTWARESOFTWARE

%escribe the software re!uirements for the test environment. dentify automatedtesting tools, operating systems, compilers, etc.

LOCATIONLOCATION

3utline the office and space re!uirements for the test environment. dentify all

sites where testing occurs.

STAFFING AND TRAININGSTAFFING AND TRAINING

dentify any staffing or training needs.

Page 4


6/6

SCHEDULESCHEDULE

Provide a detailed schedule of testing activities and responsibilities. ndicatedependencies and time frames for testing activities.

Page 5

Documents

Test Plan Template .doc