test procedure. (NIST) A formal document developed from a test plan that presents detailed instructions for the
setup, operation, and evaluation of the results for each defined test. See: test case.
test report. (IEEE) A document describing the conduct and results of the testing carried out for a system or
system component.
test result analyzer. A software tool used to test output data reduction, formatting, and printing.
testing. (IEEE) (1) The process of operating a system or component under specified conditions, observing or
recording the results, and making an evaluation of some aspect of the system or component. (2) The process of
analyzing a software item to detect the differences between existing and required conditions, i.e. bugs, and to
evaluate the features of the software items. See: dynamic analysis, static analysis
testing, acceptance. (IEEE) Testing conducted to determine whether or not a system satisfies its acceptance
criteria and to enable the customer to determine whether or not to accept the system. Contrast with testing,
development; testing, operational.
testing, alpha []. (Pressman) Acceptance testing performed by the customer in a controlled environment at the
developer’s site. The software is used by the customer in a setting approximating the target environment with the
developer observing and recording errors and usage problems.
testing, assertion. (NBS) A dynamic analysis technique which inserts assertions about the relationship between
program variables into the program code. The truth of the assertions is determined as the program executes.
testing, beta []. (1) (Pressman) Acceptance testing performed by the customer in a live application of the
software, at one or more end user sites, in an environment not controlled by the developer. (2) For medical
device software such use may require an Investigational Device Exemption [IDE] or Institutional Review Board
[IRB] approval.
testing, boundary value. A testing technique using input values at, just below, and just above, the defined
limits of an input domain; and with input values causing outputs to be at, just below, and just above, the defined
limits of an output domain. See: boundary value analysis; testing, stress.
testing, branch. (NBS) Testing technique to satisfy coverage criteria which require that for each decision point,
each possible branch [outcome] be executed at least once. Contrast with testing, path; testing, statement. See:
branch coverage.
testing, compatibility. The process of determining the ability of two or more systems to exchange information.
In a situation where the developed software replaces an already working program, an investigation should be
conducted to assess possible comparability problems between the new software and other programs or systems.
testing, exhaustive. (NBS) Executing the program with all possible combinations of values for program
variables. Feasible only for small, simple programs.
testing, functional. (IEEE) (1) Testing that ignores the internal mechanism or structure of a system or
component and focuses on the outputs generated in response to selected inputs and execution conditions. (2)
Testing conducted to evaluate the compliance of a system or component with specified functional requirements
and corresponding predicted results. Syn: black-box testing, input/output driven testing. Contrast with testing,
structural.
