Information Technology Reference
In-Depth Information
sequence, and the target line to which control flow is transferred at the end of
the linear sequence.
LCSAJ coverage:
The percentage of LCSAJs of a component that have been exer-
cised by a test suite. 100% LCSAJ coverage implies 100% decision coverage.
LCSAJ testing:
A white box test design technique in which test cases are designed
to execute LCSAJs.
Learnability:
The capability of the software product to enable the user to learn its
application. [ISO 9126] See also
usability
.
Level test plan:
A test plan that typically addresses one test level. See also
test plan.
Link testing:
See
component integration testing
.
Load testing:
A test type concerned with measuring the behavior of a component
or system with increasing load (e.g., number of parallel users and/or numbers of
transactions) to determine what load can be handled by the component or system.
See also
stress testing
.
Logic-coverage testing:
See
white box testing
.
Logic-driven testing:
See
white box testing
.
Logical test case:
See
high-level test case
.
Low-level test case:
A test case with concrete (implementation level) values for
input data and expected results. Logical operators from high-level test cases are
replaced by actual values that correspond to the objectives of the logical operators.
See also
high-level test case
.
M
Maintainability:
The ease with which a software product can be modified to cor-
rect defects, modified to meet new requirements, modified to make future mainte-
nance easier, or adapted to a changed environment. [ISO 9126]
Maintainability testing:
The process of testing to determine the maintainability
of a software product.
Maintenance:
Modification of a software product after delivery to correct defects,
to improve performance or other attributes, or to adapt the product to a modified
environment. [IEEE 1219]
Maintenance testing:
Testing the changes to an operational system or the impact
of a changed environment to an operational system.
Management review:
A systematic evaluation of software acquisition, supply,
development, operation, or maintenance process, performed by or on behalf of
management that monitors progress, determines the status of plans and schedules,
confirms requirements and their system allocation, or evaluates the effectiveness of
management approaches to achieve fitness for purpose. [IEEE 610, IEEE 1028]
Master test plan:
A test plan that typically addresses multiple test levels. See also
test plan
.
