Acceptance Testing Procedure

Objectives

This standard defines the content of the Acceptance Test Plan and Test Cases.

Scope

This standard only applies if Department X is playing a role in the development of the Acceptance Test Plan. If the customer is assuming full responsibility for developing the Acceptance Test Plan, then this standard does not apply.

References

CM051 Documentation Format Guideline

SD060 Acceptance Testing Procedure

Outstanding Issues

None.

Approvals

Development Manager.

Responsibilities

The Project Manager (see Acceptance Testing Procedure) is responsible for ensuring that an Acceptance Test Plan and Test Cases are produced.

The Project Manager is responsible for ensuring that the Acceptance Test Plan and Test Cases are updated when requirements change.

Template

Test Plan

Lead-In Sections

i. The following sections are at the beginning of the Acceptance Test Plan. They are described in more detail in the Documentation Format Guideline.

a. Objectives

b. Scope

c. References

d. Outstanding Issues

e. Approvals.

Test Responsibilities

i. customer's responsibilities in preparing for and performing acceptance test.

ii. Department X' responsibilities in preparing for and performing acceptance test.

Testing Approach

i. the types of tests which will be performed (e.g. stress testing, timing tests, compliance testing, capacity testing).

ii. the level at which testing is performed (e.g. system level, component level, integration level).

iii. test methods, tools, harnesses and procedures which will be used.

iv. source of test data.

Test Schedule

i. a schedule indicating the start and end times for all the aspects of testing included in this test including preparation.

Fault Reporting and Data Recording

i. a description of, or reference to, the fault reporting process which will be used.

ii. a description of how test results will be recorded.

Resource Requirements

i. hardware requirements (e.g. hardware items, interfacing equipment, firmware items).

ii. software requirements (e.g. operating systems, compilers, test drivers, test data generators).

iii. documentation requirements (e.g. test documentation).

iv. people requirements (e.g. Department X employees, customer employees).

v. test data requirements

vi. any other requirements (e.g. special equipment).

Test Environment

i. describe the plans for setting up the test environment.

Identification of Tests

i. list of individual tests and objective of each test.

Note: A Test Case will be prepared for each test identified here.

Test Cases

Test Case Identifier

i. a unique reference number assigned to the Test Case.

Requirements Traceability

i. cross references to applicable requirements as identified in the Requirements Specification.

Description of Test

i. a brief overview of the test.

Test Initialization

i. hardware and software configuration.

ii. preset hardware conditions.

iii. preset software conditions.

Test Inputs

i. describe test inputs

Test Procedure

i. detailed steps used to perform the test.

Expected Results

i. the expected outcome of the test or a description of the type of result which the tester should check for.

Special Instructions

i. anything that the tester needs to be aware of when running the test e.g. another Test Case must be run first, the test produces a large quantity of printout.