Questions & Answers

TTCN-3 FAQ

January 24, 2012

1.    What is TTCN-3? -    Testing and Test Control Notation Version 3 (maintained by ETSI – European Telecom Standardization Institute) -    TTCN-3 Testing Language -    Standardized modern high level language for testing -    TTCN-3 Architecture -    TTCN-3 TCI and TRI interfaces -    Black-box, functional testing of reactive systems 2.    What are the most popular domains [...]

Read the full article →

Why and how to migrate test suites from TTCN-2 to TTCN-3?

November 17, 2011

The major new capabilities of TTCN-3 compared to TTCN-2 are: different presentation formats (e.g. tabular and MSC presentation formats), dynamic concurrent testing configurations, operations for synchronous and asynchronous communications, ability to specify encoding information and other attributes (including user extensibility), data and signature templates with powerful matching mechanisms, type and value parameterization, assignment and handling [...]

Read the full article →

What is the role of Platform Adapter?

September 1, 2010

In platform adapter you implement: 1) external functions (if any) used in your TTCN-3 code 2) external timers (if any) If your TTCN-3 script does not contain external functions and you do not need external timers then you do not need platform adapter ( this is in case with some test tools, as they have [...]

Read the full article →

See Public TTCN-3 Test Suites

August 17, 2010

One of the benefit for using TTCN-3 test language has always been the opportunity to download free publicly available TTCN-3 test suites. Some publicly available test suites are available at ETSI’s website. Main areas for public TTCN-3 test suites that ETSI provides: digital Public Mobile Radio (dDMR) Dynamic Host Configuration Protocol (DHCPv6) IPv6 Multimedia Subsystem (IMS) Voice [...]

Read the full article →

Do TTCN-3 tools support test process management capability? Is it possible to integrate them with other tools like IBM/HP change management?

August 12, 2010

TTCN-3 test tools themselves do not include heavy test process management. There is standardized interface (TCI-TM) to integrate Test Management software to the TTCN-3 executable.  TCI-TM is the standardized interface  that enables to control the TTCN-3 executable through third party test process management systems from outside.

Read the full article →

Do TTCN-3 tools support any non-functional testing?

August 12, 2010

Software performance testing and load testing – yes/no, depends on use case Stability testing - yes Usability testing - no, usability testing is SW testing by real users, not by test script Security testing - yes, depends on test script Internationalization and localization - no Destructive testing – yes/no, depends on use case and TTCN-3 script Non-functional testing depends heavily on [...]

Read the full article →

Which testing levels do generic TTCN-3 test tools support?

August 12, 2010

Unit testing – yes Integration testing – yes System testing – yes System integration testing – yes Regression testing – yes Acceptance testing – yes Alpha testing – yes Beta testing – no, beta testing is actual usage of SW, not testing it with some tool What you are actually testing depends on your TTCN-3 [...]

Read the full article →

What kind of System Under Test (SUT) can there be?

August 12, 2010

TTCN-3 testing language can be used to test a great variety of various SUT’s. The SUT type depends heavily on the system adapter implementation. Some examples of SUT are: Embedded SW (embedded to some device), but it must be possible to connect to the device from computer (since test tool runs on a computer) via LAN, USB [...]

Read the full article →

What are TCI and TRI?

August 12, 2010

TTCN-3 Control Interface (TCI) is a standardized interface helps to connect external logger, test management and codecs to the test tool. TTCN-3 Runtime Interface (TRI) is a standardized interface that helps to connect system adapter and platform adapter with the system under test (SUT).

Read the full article →

Is it possible to support embedded software black box testing and web/distributed app software black box testing?

August 12, 2010

These both aspects are about the implementation of SA (System Adapter). Therefore, it cannot be answered directly. The general deployment of TTCN-3 test system looks like this: TestTool <- TRI -> SA <- SUT proprietary protocol -> SUT There is an overview of the TTCN-3 Generic Framework below that illustrates how it is set-up.

Read the full article →