[Jump to start of article]

Home > Test Plans

Testing Documentation

As testing is a formal process it has to be documented. This section outlines the various types of document required to record the testing process with a special emphasis on the Test Plan.

IEEE829 Documentation

A number of types of document are needed for testing to take place of any type. In many cases these are created as the project proceeds. However a there is an International standard, IEEE829, which details the types of document, what should be in each, and how each relates to the other.



Test Plans

A particularly important document is the Test Plan. This series of articles outlines various issues to do with creating a good test plan. read about this and download a plan template based on the IEEE 829 standard.

Test Plan Identifier

Section 1 is the Test Plan Identifier and is a unique code to distinguish this plan from any other.

Introduction

The 2. Introduction section is part of QUALITY and has four subsections.

Scope Headings

Sections 3, 4 and 5 are to do with the SCOPE of the testing.



UAT Approach

Section 6 is to do with the QUALITY of the testing and defines how you go about testing.

Ending Testing

Section 7 is to do with the QUALITY of the testing and defines how you evaluate the testing you have done.

Suspension Criteria

Section 8 deals with when you suspend and restart testing and is a RISK section .

Testing Deliverables

Testing produces a lot of data and Section 9 outlines what the are. These are a QUALITY item.

Time Issues

Section 10 - Testing Tasks, and Section 14 Schedule deal with the TIME issues to do with testing.

Resource Issues

Section 11 - Environmental Needs, Section 12 - Responsibilities, and Section 13 - Staffing and Training Needs, deal with the RESOURCE issues of a test plan.and Section 14 Schedule deal with the TIME issues to do with testing.



Risks and Contingencies

Section 15 - Risks and contingencies deals with how to handle the risks in a project.

Approvals

Section 16 - Approvals deals with getting sign-off for a testing plan.

Test Documentation Detail