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

More documents

Recommendations

Info

Tips and Guidelines• There is no need to explicitly passed PTC verdicts to the MTCusing coordination messages– A global verdict is automatically maintained by the MTC– The global verdict is updated whenever a component terminates– Remember: Verdict never improve– Make the TTCN-3 script more readable39© Telelogic ABTesting Concept: Self-test of Test Cases• Use Concurrency to perform aself-test of a test case– All behavior is encapsulated in afunction. In the normal case, thisfunction is simply called in theMTC– For Self-Testing, a Simulation ofeach of the SUT Ports isimplemented in one or moreParallel Test Components (PTCs).They are connected to the MTCports– Since the Test System Interfacecan be left empty, SUT Adaptationis not needed for the self-test testsuiteNormalTest systemTest System InterfaceSUTSelftestTest systemPTC (Simu1)PTC (Simu2)Behavior_function()Test System InterfaceMTCBehavior_function()MTC40© Telelogic AB
Benefits with Concurrent TTCN• Less code to write• Can have several test architectures in the same test suite• Several service providers can be used• Other components can be created at any time during the testcase execution• Concurrency– We can have several components executing simultaneously– Several processes aiming at the same goal41© 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 16 and 17: Connecting and mapping• After cre
Page 18 and 19: Details from ETSI ES 201 873-1 v3.2

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

Create successful ePaper yourself

Delete template?

Save as template?