Information Technology Reference
In-Depth Information
Instrumentation:
The insertion of additional code into the program in order to
collect information about program behavior during execution (e.g., for measuring
code coverage).
Instrumenter:
A software tool used to carry out instrumentation.
Intake test:
A special instance of a smoke test to decide if the component or system
is ready for detailed and further testing. An intake test is typically carried out at
the start of the test.
Integration:
The process of combining components or systems into larger assemblies.
Integration testing:
Testing performed to expose defects in the interfaces and in
the interactions between integrated components or systems. See also
component
integration testing, system integration testing
.
Integration testing in the large:
See
system integration testing
.
Integration testing in the small:
See
component integration testing
.
Interface testing:
An integration test type that is concerned with testing the inter-
faces between components or systems.
Interoperability:
The capability of the software product to interact with one or
more specified components or systems. [ISO 9126] See also
functionality
.
Interoperability testing:
The process of testing to determine the interoperability
of a software product. See also
functionality testing
.
Invalid testing:
Testing using input values that should be rejected by the compo-
nent or system. See also
error tolerance
.
Isolation testing:
Testing of individual components in isolation from surrounding com-
ponents, with surrounding components being simulated by stubs and drivers, if needed.
Item transmittal report:
See
release note
.
Iterative development model:
A development life cycle where a project is broken
into a usually large number of iterations. An iteration is a complete development
loop resulting in a release (internal or external) of an executable product, a subset
of the final product under development, which grows from iteration to iteration to
become the final product.
K
Key performance indicator:
See
performance indicator
.
Keyword-driven testing:
A scripting technique that uses data files to contain not
only test data and expected results but also keywords related to the application
being tested. The keywords are interpreted by special supporting scripts that are
called by the control script for the test. See also
data-driven testing
.
L
LCSAJ:
A Linear Code Sequence And Jump, consisting of the following three
items (conventionally identified by line numbers in a source code listing): the
start of the linear sequence of executable statements, the end of the linear
