Foreword
(This Foreword is not a part of ANSI/IEEE Std 1008-1987, IEEE Standard for Software Unit Testing.)
Objectives
This standard's primary objective is to specify a standard approach to software unit testing that can be used
as a basis for sound software engineering practice.
A second objective is to describe the software engineering concepts and testing assumptions on which this
standard approach is based. This information is contained in Appendix B. Note that Appendix B is not a part
of this standard.
A third objective is to provide guidance and resource information to assist with the implementation and
usage of the standard unit testing approach. This information is contained in Appendixes A, C, and D. Note
that these Appendixes are not a part of this standard.
Motivation
A consensus definition of sound unit testing provides a baseline for the evaluation of specific approaches. It
also aids communication by providing a standard decomposition of the unit testing process.
Audience
The primary audience for this standard is unit testers and unit test supervisors. This standard was developed
to assist those who provide input to, perform, supervise, monitor, and evaluate unit testing.
Relationship with Other Software Engineering Standards
ANSI/IEEE Std 829-1983, IEEE Standard for Software Test Documentation, describes the basic information
needs and results of software testing. This unit testing standard requires the use of the test design specification
and test summary report specified in ANSI/IEEE Std 829-1983.
This standard is one of a series aimed at establishing the norms of professional practice in software engineering.
Any of the other software engineering standards in the series may be used in conjunction with it.
Terminology
Terminology in this standard is consistent with ANSI/IEEE Std 729-1983, IEEE Standard Glossary of Software
Engineering Terminology. To avoid inconsistency when the glossary is revised, its definitions are not
repeated in this standard.
The referred to in this standard is a specific case of the referred to in ANSI/IEEE 829-1983. The term is
used because of this standard's narrower scope.
The use of the term specification, description, or document refers to data recorded on either an electronic or
paper medium.
The word must and imperative verb forms identify mandatory material within the standard. The words
should and may identify optional material.