Software test documentation

Definitions of IEEE
SQAP - Software Quality Assurance Plan IEEE 730 SCMP - Software Configuration Management Plan IEEE 828 STD - Software Test Documentation IEEE 829 SRS - Software Requirements Specification IEEE 830 SVVP - Software Validation & Verification Plan IEEE 1012 SDD - Software Design Description IEEE 1016 SPMP - Software Project Management Plan IEEE 1058

The definition of IEEE 829 Standard for Software Test Documentation is one of the IEEE ( Institute of Electrical and Electronics Engineers published) standard , a set of eight basic documents for the documentation of software testing describes. The current version is the IEEE 829-2008. The standard describes the form and content of the respective documents. However, it does not stipulate which of the respective documents must be used.

In September 2013, the first parts of the international standard ISO / IEC / IEEE 29119 were published, which replaces the IEEE 829 Standard for Software Test Documentation internationally.

General

Relationship between the documents in the course of the procedure

The standard describes eight documents, which can be divided into three categories as follows.

• Overview

1. Test concept (test plan): The test determines concept definition, procedure, agent, and the flowchart of test activities. It determines the items and product functions to be tested, the test tasks to be performed, the responsible personnel for each task and the risk associated with the concept.

• Test specification

1. Test design specification: The test design specification refines the description of the procedure for testing the software. It identifies the product functions that must be covered by the tests. It also describes the test cases and test procedures that are required to pass tests and specifies the criteria for passing or failing the individual product functions.
2. Test case specification: The test case specification documents the input values ​​to be used and the expected output values. Test cases are separate from the test design. This allows the test cases to be used in multiple designs and reused in other situations.
3. Test procedure specification (test procedure specification): description of all steps for performing the specified test cases and implementation of the associated test designs.

• Test (test reporting)

1. Test object handover report are the test object handover report describes the transfer of the test cases in the event that separate development and test teams involved or in the event that an official time for the start of a test execution is desired: (test item transmittal report).
2. Test log: The test log is used to record the events during a test execution.
3. Test incident report (test incident report): It describes all events that occur during a test execution and require further investigation.
4. Test final report (test summary report): Summarizes the test activities together, associated with one or more test design specifications.

Web links

• IEEE Software Engineering Collection
• Robert Bullinger: Test documentation according to IEEE 829 .
• German Testing Board - Glossary (PDF; 463 kB)

Individual evidence

1. ↑ IEEE (Ed.): 829-2008 - IEEE Standard for Software and System Test Documentation . July 18, 2008, p. 150 , doi : 10.1109 / IEEESTD.2008.4578383 .