Information Technology Reference
In-Depth Information
Structural test design technique: See white box test design technique .
Structural testing: See white box testing .
Structured walkthrough: See walkthrough .
Stub: A skeletal or special-purpose implementation of a software component, used
to develop or test a component that calls or is otherwise dependent on it. It replaces
a called component. [IEEE 610]
Sub path: A sequence of executable statements within a component.
Suitability: The capability of the software product to provide an appropriate set of
functions for specified tasks and user objectives. [ISO 9126] See also functionality .
Suspension criteria: The criteria used to (temporarily) stop all or a portion of the
testing activities on the test items. [IEEE 829]
Syntax testing: A black box test design technique in which test cases are designed
based on the definition of the input domain and/or output domain.
System: A collection of components organized to accomplish a specific function or
set of functions. [IEEE 610]
System integration testing: Te s t i n g t h e i nt e g r a t i on of f s y s t e m s a n d p a c k a g e s ; t e s t i n g
interfaces to external organizations (e.g., Electronic Data Interchange, Internet).
System testing: The process of testing an integrated system to verify that it meets
specified requirements.
T
Technical review: A peer group discussion activity that focuses on achieving con-
sensus on the technical approach to be taken. [IEEE 1028] See also peer review .
Te s t : A set of one or more test cases [IEEE 829]
Test approach: The implementation of the test strategy for a specific project. It
typically includes the decisions made that follow based on the (test) project's goal
and the risk assessment carried out, starting points regarding the test process, the
test design techniques to be applied, exit criteria, and test types to be performed.
Test automation: The use of software to perform or support test activities (e.g., test
management, test design, test execution, results checking).
Test basis: All documents from which the requirements of a component or system
can be inferred. The documentation on which the test cases are based. If a docu-
ment can be amended only by way of formal amendment procedure, then the test
basis is called a frozen test basis.
Test bed: See test environment .
Test case: A set of input values, execution preconditions, expected results, and
execution post conditions, developed for a particular objective or test condition,
such as to exercise a particular program path or to verify compliance with a specific
requirement. [IEEE 610]
Test case design technique: See test design technique .
Search WWH ::




Custom Search