Lecture Notes in Computer Science 3472

500 Zhen Ru Dai
state machines, states or regions, and in Activity Diagrams to actions and activities.
Since each default in an Interaction applies only to one test component,
defaults are attached on interaction fragments to the intersection between the
fragment and the test component. In U2TP, defaults behaviors can be specified
on different behavior levels, e.g. on a state, interaction, instance etc.. If the innermost
default fail to recognize the observed behavior the default of the next
level is tried.
Test verdicts specify possible test results, e.g. pass, fail, inconclusive or error.
The definition of the verdicts originate from the OSI Conformance Testing
Methodology and Framework [ISO94]: Pass indicates that the SUT behaves correctly
for the specific test case. Fail describes that the test case has violated.
Inconclusive is used where the test neither passes nor fails. An error verdict
indicates exceptions within the test system itself.
A validation action can be performed by a test component to denote that
the arbiter is informed of a test result which was determined by that test component.
The coordination between arbiter and test components is controlled by
the scheduler.
Both a test context and a test case may trace their executions. These traces
are behaviors in general and are generated during the execution of a test case.
They can be recorded as test logs and become part of the test specification. A
test log has to be attached to a test context or a test case such that it is specified
from which test context or test case that test log has been taken.
Data Concepts This concept group contains concepts needed to describe test
data. There are means provided to specify test data for the data transmission
between the SUT and the test system.
Wildcards which can denote an omitted value, any value or any value or omit
(* or ?) are needed to specify test data, especially for data reception.
Test cases are often executed repeatedly with different data values to stimulate
the SUT in various ways. Also when observing data, abstract equivalence
classes are used to define sets of allowed values. Typically, these values are taken
from a partition of test data, or lists of explicit values. For this purpose, a data
pool provides a means for associating data sets with test contexts and test cases.
A data pool contains either data partitions which build equivalence classes, or
explicit values.
Data partition is used to define an equivalence class for a given type. By
denoting the partitioning of data explicitly U2TP provides a more visible differentiation
of data.
Data selectors are typically operations that operate over the contained values
or value sets. By means of data selectors, test data can be retrieved out of a data
pool or a data partition.
Coding rules are shown as strings referencing coding rules defined outside the
U2TP such as by ASN.1, CORBA or XML. Coding rules are basically applied to
data value specification to denote the concrete encoding and decoding for these
values during test execution.