Lecture Notes in Computer Science 3472

468 George Din
• Tabular Presentation Format. TTCN-3 offers optional presentation formats.
The tabular format is similar in appearance and functionality to earlier versions
of TTCN. It was designed for users that prefer the TTCN-2 style of
writing test suites. A TTCN-3 module is presented in the tabular format as
a collection of tables [Ins03].
• Graphical Presentation Format. It is the second presentation format of
TTCN-3 and is based on the MSC format [ITU99] (Message Sequence
Charts). The graphical format is used to represent graphically the TTCN-3
behavior definitions as a sequence of diagrams [Ins03].
• Operational semantics. This document describes the meaning of TTCN-3
behavior constructs and provides a state oriented view of the execution of a
TTCN-3 module [Ins03].
• The TTCN-3 Runtime Interface (TRI). A complete test system implementation
requires also a platform specific adaptation layer. The TRI document
contains the specification of a common API interface to adapt TTCN-3 test
systems to SUT [Ins03].
• The TTCN-3 Control Interfaces (TCI). This part provides an implementation
guide-line for the execution environments of TTCN-3. It specifies the
API the TTCN-3 execution environments should implement in order to ensure
the communication, management, component handling, external data
control and logging [Ins03].
16.1.4 Chapter Overview
The rest of the chapter is structured as it follows: Section1.2 introduces a webservice
test example which will be used among all sections to exemplify the
TTCN-3 concepts, Section1.3 introduces the semantic of the TTCN-3 language
artifacts, next, Section1.4 presents some issues on TTCN-3 compiling. Section1.5
introduces TCI and TRI specifications and presents how the TTCN-3 test systems
can be realized on top of these interfaces. Section1.6 concentrates on test
configuration and deployment revealing some of the related problems. Summary
and an outlook are presented in Section1.7
16.2 Web Service Testing Example
In this section we try to show how easy or how complex it is to use TTCN-3 by
using an web service test as example. The main idea is to define a test system for
interaction with the system under test (the web service) and validate its basic
functionality (i.e. simple queries). TTCN-3 test components are used to emulate
system clients. These test components perform the basic functional tests in order
to evaluate the reaction of the system to selected service requests or complex
service request scenarios. The combination of test components performing different
basic functional tests and their parallel execution leads to different test
scenarios for the system under test.
In our example we use a dinosaurian database web service (Dino web service)
which contains dinosaurian information stored in form of database entries. A