Abstract
When deploying TTCN-3 at Nokia, we converted two TTCN-2 test systems to TTCN-3. We explain to which extend we have been able to do the conversion automatically. The conversion tool used provided a syntactically and semantically correct conversion of the TTCN-2 code. We define some improvements made on the tool to increase readability and maintainability of the resulting code. We cover aspects of converting also the non-TTCN-2 parts and describe the experiences we made as a set of lessons learnt.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
MTS; The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language, ETSI ES 201 873-1
ISO/IEC 9646-3: Tree and Tabular Combined Notation
ITU-T Recommendation X.680: Information technology—Abstract Syntax Notation One (ASN.1): Specification of basic notation (2002)
OMG Formal Document FORMAL/2001-12-01: The Common Object Request Broker–Architecture and Specification, Version 2.6 (2001)
MTS; The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI), ETSI ES 201 873-5
MTS; The Testing and Test Control Notation version 3; Part 6: TTCN-3 Control Interface (TCI), ETSI ES 201 873-6
Zeiß, B. et al.: Refactoring TTCN-3 Test Suites. In: Proceedings of SAM’06, 5th Workshop on System Analysis and Modeling, Revised Selected Papers. LNCS, vol. 4320. pp. 148–165, Springer, Heidelberg (2006)
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
About this article
Cite this article
Deiß, T. Refactoring and converting a TTCN-2 test suite. Int J Softw Tools Technol Transf 10, 347–352 (2008). https://doi.org/10.1007/s10009-008-0079-9
Published:
Issue Date:
DOI: https://doi.org/10.1007/s10009-008-0079-9