Lecture Notes in Computer Science 3472

472 George Din
Abstract Test System Interface can also be defined as a component, since its
definition is the same as a component definition: a collection of ports used to
connect and communicate with other components.
For Dino web service test we define the MTCType, PTCType and SUTType
components. The SUTType component defines a component type which contains
an array of ports. This component represents, at an abstract level, the SUT. According
to SUTType definition the SUT provides many connection ports which
implies that many PTCs can interact with the SUT at the same time.
type component MTCType {}
type component PTCType {
port httpTestPortType httpPort;
timer localTimer := 3.0;
}
type component SUTType {
port httpTestPortType httpTestSystemPort[NUMBER_OF_PTCS];
}
The communication between test components as well as the one between test
components and test system interface are realized over ports. There are two types
of communication: message based (the communication is based on asynchronous
interchange of messages) and procedure based (the communication is realized
in form of synchronous remote procedure invocations). Therefore, TTCN-3 supports
two types of ports: message-based and procedure-based ports. Data transmission
directions can be defined for each port: in (the received data), out (the
sent data), inout (the data can be both sent or received). Ports can also be
mixed; they can be used both for message-based and for procedure-based communication.
In our example, we use the httpTestPortType port to connect a test component
to the web service (SUT). Since the communication with the SUT is an
asynchronous one, we define this port of type message. This port allows to send
request messages like search, update, add or remove. The incoming messages can
be of type dinosaur, updateAck, addAck or removeAck.
type port httpTestPortType message {
out search;
out update;
out add;
out remove;
in dinosaur;
in updateAck;
in addAck;
in removeAck;
}