Managing Concurrency and Parallel Testing with TTCN-3 Telelogic ...

More documents

Recommendations

Info

Connecting and mapping• After creation of the components we need to connect portsbetween MTC/PTC components and map ports between anMTC/PTC component and the Test System Interface – TSI– The mtc-keyword identifies the MTC, system identifies the TSIinstance and the self-keyword identifies the currently executingMTC/PTC• Without connecting/mapping a component cannotcommunicate with the outside world• When connecting port A and port B, the in list of port A mustmatch the out list of port B and vice versa• When mapping port A and port B, the in list of port A mustmatch the in list of port B, and the out list of port A must matchthe out list of port B31© Telelogic ABUnconnect and Unmap• Connections and Mappings can be undone, to changeconfiguration during the runtime of the test• Syntax is the same as for connect and map32© Telelogic AB
Starting and Stopping test components• Once components are created and connected/mapped, theycan be started• The behavior to be executed by the component is given in thestart command– The behavior is defined as a function• Components can be stopped using the stop command– Only the execution of test behavior is stopped.– Components can stop themselves, or other components• Components can be destroyed using the kill command– The execution of test behavior is stopped - if any– All associated resources (including all port connections) are freed– Components can kill themselves, or other components33© Telelogic ABQuerying test components• The running operation returns a boolean value based onwhether the component is running or not• The alive operation returns a boolean value based on weatherthe component is already executing or ready to executebehavior, or not• The done operation can only be executed when thecomponent has completed its behavior• The killed operation can only be executed when thecomponent has been destroyed34© Telelogic AB
Page 1 and 2: TTCN-3 Users conference Asia 2007Be
Page 3 and 4: Why do we need a concurrent testarc
Page 5 and 6: Why do we need a concurrent testarc
Page 7 and 8: What kind of architecture can be us
Page 9 and 10: What kind of architecture can be us
Page 12 and 13: A TTCN-3 Example// Behavior descrip
Page 14 and 15: A TTCN-3 Example// Behavior descrip
Page 18 and 19: Details from ETSI ES 201 873-1 v3.2
Page 20 and 21: Tips and Guidelines• There is no

Managing Concurrency and Parallel Testing with TTCN-3 Telelogic ...

Create successful ePaper yourself

Delete template?

Save as template?