From OpenTTCN DocZone

OpenTTCN DocZone   Home | Developer's corner | Knowledge base | Working documents | Documentation | Tutorials | Training | How do I | Frequently asked questions | Technical support

How do I create a test system using OpenTTCN?

---

The following article explains how to create and package a redistributable OpenTTCN-based test system.

Test system components

OpenTTCN-based test system normally consists of the following components that constitute an "indivisible final product" referred to in the licensing agreement that describes the use of royalty free OpenTTCN Runtime and test system that can be redistributed.

Test system start-up application

Test system start-up application can be programmed as a separate application or the functionality can be combined with the TM-UI implementation. This application shall set-up and start-up the rest of the test system. The binary file / executable is produced by the test system vendor or integrator by linking the compiled test system start-up application with OpenTTCN-provided ISL library. For more information, see OpenTTCN SDK User Manual and <sdk install location>/include/isl/TTCN3.h.

Test management (TM) user interface (UI)

TM-UI implementation is programmed using ETSI TTCN-3 TCI-TM interface. The binary file / executable is produced by the test system vendor or integrator by linking the compiled TM-UI implementation with OpenTTCN-provided TCI-TM and TCI-CD libraries. It is not advised to combine TM-UI implementation with any other component of the test system. In this way the TM-UI implementation will not be affected if other components fail to operate correctly. For more information, see OpenTTCN SDK User Manual and <sdk install location>/include/tci/tci.h and tci_ext.h.

OpenTTCN Runtime

OpenTTCN Runtime consists of:

• all files included in the tester part of OpenTTCN Tester for TTCN-3 (for example, all files included in OpenTTCN-tester-2.56.0.exe installation package for Windows or all files included in OpenTTCN-tester-2.56.0.bin installation package for Linux);
• the runtime license key allowing execution of compiled test cases but not allowing neither compilation nor debugging of TTCN-3 source code. The binary files / executables of OpenTTCN Runtime are provided by OpenTTCN Ltd. For more information, see User Guide for OpenTTCN Tester Command-Line Utilities, chapter 4.9 Compiling Test Cases for OpenTTCN Runtime.

Pre-compiled abstract test suites

Pre-compiled abstract test suites consist of FS files (including the naming.fs file and suiteXXXX.fs files, where XXXX is the number of the individual file) located in the <tester install directory>/var directory. The FS files comprising pre-compiled test suites contain testing session information and test suites in intermediate XML format used by the OpenTTCN virtual machine implementing the TTCN-3 executable and test components. The FS files are non-encrypted and contain the abstract test suite data in pre-processed format. For more information, see User Guide for OpenTTCN Tester Command-Line Utilities, chapter 4.9 Compiling Test Cases for OpenTTCN Runtime.

TTCN-3 SUT adapter (SA)

SA implementation is programmed using ETSI TTCN-3 TRI interface. The test system may contain one or multiple SA implementations. One or multiple SA implementations can be implemented using one binary / executable. One or multiple SA implementation binaries / executables can exist in a single test system. The binary files / executables are produced by the test system vendor or integrator by linking the compiled SA implementation with OpenTTCN-provided SA library. For more information, see OpenTTCN SDK User Manual and <sdk install location>/include/tri/tri.h and tri_ext.h.

TTCN-3 platform adapter (PA)

PA implementation is programmed using ETSI TTCN-3 TRI interface. The test system may contain one or multiple PA implementations. One or multiple PA implementations can be implemented in one binary / executable. One or multiple PA implementation binaries / executables can exist in a single test system. The binary files / executables are produced by the test system vendor or integrator by linking the PA implementation with OpenTTCN provided PA library. For more information, see OpenTTCN SDK User Manual and <sdk install location>/include/tri/tri.h and tri_ext.h.

TTCN-3 coding and decoding (CD)

CD implementation is programmed using ETSI TTCN-3 TCI-CD interface. The test system may contain one or multiple CD implementations. One or multiple CD implementations can be implemented in one binary / executable. One or multiple CD implementation binaries / executables can exist in a single test system. The binary files / executables are provided by the test system vendor or integrator by linking the CD implementation with OpenTTCN provided TCI-CD library. For more information, see OpenTTCN SDK User Manual and <sdk install location>/include/tci/tci.h and tci_ext.h.