T. Deiß, "Refactoring and Converting a TTCN-2 Test Suite," ETSI TTCN-3 User Conference 2005: Sophia Antipolis (France), June 6-8, 2005.
Added by: Deleted user (25 Jul 2008 14:50:37 Europe/Berlin) Last edited by: Axel Rennoch (09 Jan 2013 16:53:55 Europe/Berlin)
|Resource type: Conference Paper
BibTeX citation key: Deissa
View all bibliographic details
Publisher: ETSI (Sophia Antipolis (France))
Collection: ETSI TTCN-3 User Conference 2005
Views index: %
Popularity index: 8.75%
TTCN-3 as a language has been designed such that existing TTCN-2 test suites can be converted automatically to TTCN-3. Conversion of TTCN-2 to TTCN-3 test suites is an important way of resolving the dilemma when extending systems with new features and when there is already a TTCN-2 test system. Shall the TTCN-2 test system be extended or shall a new test system be developed using TTCN-3? If an existing TTCN-2 test suite can be converted, then the investments in the original TTCN-3 test suite can be saved and the advantages of TTCN-3 can be used when extending the test suite to cover also the new features. Although we have been able to convert several TTCN-2 test suites almost automatically to TTCN-3, this is not the case for all test suites. In addition, conversion from TTCN-2 to TTCN-3 has also to take care of migrating the whole test systems.
In this presentation I will highlight experience we made at Nokia in preparing the conversion of large TTCN-2 test system for a network element to TTCN-3.
In a first part of the presentation the existing TTCN-2 test system is introduced. Aspects of both the test suite structure as well as the test system architecture will be shown.
The second part of the presentation will focus on the test system related issues. The test system architecture has been a distributed architecture, separating protocol layer implementations needed to connect to the SUT and the executable TTCN-2 test suite from each other. The interface between these two parts has been rather narrow, therefore the implementation of this interface could be easily replaced with a TRI compliant version for the TTCN-3 test system. Almost all message types in the test suite have been defined using ASN.1 with standardized encodings. As the used TTCN-3 tool supported ASN.1 and codec generation well, few effort was needed to provide encoding and decoding functions for the TTCN-3 test suite.
The third part of the presentation will focus on the actual conversion of the TTCN-2 test suite. It will be presented, why fully automated conversion has not been possible. Instead, it has been decided to take a mixed approach, using only parts of the converted code. These TTCN-3 parts will then be manually combined to test cases, mainly to achieve better maintainability than with the TTCN-2 test suite. The used conversion tool had to be adapted to cope with problems in the TTCN-2 code and to fit into the process used. These adaptations will be highlighted.
The presentation will close with some general remarks on converting a test suite still under development and on gaining user acceptance for the new tools.
Added by: Deleted user Last edited by: Axel Rennoch