Lecture Notes in Computer Science 3472

484 George Din
Value
Type getType()
String getValueEncoding()
boolean notPresent()
FloatValue BooleanValue CharValue VerdictValue
IntegerValue ObjidValue UniversalCharValue
HexstringValue OctetstringValue CharstringValue BitstringValue
UniversalCharstringValue
UnionValue EnumeratedValue RecordOfValue RecordValue
Fig. 16.5. The TTCN-3 Value Types which can appear in a TE.
Management of the Test Execution The overall management of a test
system is realized by the Test Management entity (TM). The TM operations
can be split into two parts: operations which are used by the user to control the
test execution and operations provided to TE in order to notify the user about
changes in the execution status.
The user may start or stop the test cases and the control part. This functionality
is implemented in TE. In response, the TE may notify the TM when a test
case or the control started or terminated. As presented in Section 1.3, the test
cases can be parameterized. This is also reflected in the TM - tciStartTestCase
method which has a TciParamterListType as argument. The TE, where the
MTC is executed, is called special TE and is used to start the test cases or the
control part.
The values of the parameters of a module are transferred to TE also via
TM interface. TE may ask TM about the value of a parameter by using the
tciGetModuleParameter.
A user may obtain information about the content of a module. With the
tciGetTestCases and the tciGetModuleParameters methods, the user may
acquire the list of test cases and module parameters.
Test Configuration The abstract operations used in the TTCN-3 test specifications
in order to define test configurations (create, connect, disconnect, start,
stop etc) are mapped to concrete operations in the CH interface. All the configuration
operations are reflected by the CH API. The configuration operations are
called from behaviors (test cases, functions, control) which are contained by TE.
Since the TE does not know where to create or start components, the request
is sent to CH. Conceptually, CH has knowledge about every component. The
requests from TE are analized on the basis of the CH knowledge; CH decides if
the requests are to be handled locally or remotely (a component can be created
either locally or remotely). If the request is executed locally, it is sent back to
the local TE. If the request is to be executed on a remote node, the CH sends