Sabiguero, A., Baire, A., Desmoulin, A., Floch, A., Roudaut, F., & Viho, C. 2006, May 31–June 2, Towards an IP-oriented testing framework: The IPv6 testing toolkit. Unpublished paper presented at ETSI TTCN-3 User Conference 2006, Berlin (Germany).
Added by: Deleted user (7/7/08, 1:54 PM) Last edited by: Deleted user (8/13/08, 2:23 PM)
|Resource type: Conference Paper
BibTeX citation key: Sabiguerob
View all bibliographic details
Creators: Baire, Desmoulin, Floch, Roudaut, Sabiguero, Viho
Publisher: Fraunhofer FOKUS, ETSI (Berlin (Germany))
Collection: ETSI TTCN-3 User Conference 2006
The European Community, through the European Telecommunications Standards Institute (ETSI), promotes the use of the TTCN-3 (Testing and Test Control Notation version 3) as the standard test specification and implementation language.
TTCN-3 is designed to provide a framework for the precise definition of test procedures for black-box testing of communicating systems, being the third part of the ISO/IEC 9646 recommendation. TTCN-3 has been designed to provide a well suited environment for any kind of testing activity, from abstract test suites specification to executable test suites. It is supposed to allow an easy, efficient and yet powerful description of abstract test suites in a platform independent manner. Even though it cannot be considered as a new language, there is not enough maturity regarding its application.
TTCN-3 is a strong-typed language which presents some difficulties when trying to work with complex, low level oriented data. Network protocols hold themselves several hard to predict behaviors related to flow flags, options, and other aspects that require the ability to handle unknown sizes, number of options, etc. TTCN-3 language provides basic matching capability based on the wildcards ? and *.
Coding of TTCN-3 values into transmittable messages and decoding of bitstrings into their TTCN-3 representation has been removed from the core language itself and is done in an external component. These operations of coding and decoding, are performed in a component called CoDec, that is interfaced with the TE through the TCI-CD interface. As CoDec are not standard in TTCN-3, required ones may be present or not in tools. Toolprovided generic CoDec were inadequate for working with IP traffic. TTCN-3 allows the possibility of extending the CoDec with new, specific to the problem ones. They have to be coded in a "lower level" programming language like Java or C.
TCI-CD helps building abstract specification of test suites, as coding and decoding details are removed from the test specification. On the other hand, it imposes additional complexity to the test development process: handling of communicable types has to be done both in TTCN-3 and the platform language (Java or C). Every time the low-level types are reviewed, pieces of highly coupled and independent code, written in different languages have to be altered and kept synchronized manually.
The objective of the present work is to present and discuss the experience gathered producing test suites for different IPv6 protocols in TTCN-3 language, the different matching alternatives and how we organized our code to allow reusability.
During this process, a framework for the testing of IPv6 based protocols was defined and implemented. This framework provides enough flexibility for software reuse without code modifications. It also gives hints which helps to determine if provided matching mechanisms are suitable for a particular problem or if a custom one has to be developed. Some concrete examples based on IPv6 message oriented protocols are used to explain part of the proposed solution and for validation purpose.
Added by: Deleted user Last edited by: Deleted user