There is a dedicated website where you will be able tofind many more information.

Some of the benefits of using TTCN-3 include:

• The language is specifically designed for testing


• The syntax and operational semantics of TTCN-3 tests are commonly understood and not related to a particular programming language


• TTCN-3 tests concentrate on the purpose of the test and are abstracted from particular test system details


• Off the shelf tools and TTCN-based test systems are readily available


• The language is constantly maintained and developed Education and training costs can be rationalized and reduced


• Maintenance of test suites (and products) is easier


• Allows the application of a common methodology and style, both on a corporate level and within standardization

The Testing and Test Control Notation (TTCN), is a language used to write detailed test specifications. TTCN has been used to specify tests for many kinds of applications, including mobile communications (GSM, 3G, TETRA), wireless LANs (Hiperlan/2), cordless phones (DECT), Broadband technologies (B-ISDN, ATM), CORBA-based platforms and Internet protocols such as IPv6, SIGTRAN, SIP and OSP.

The latest version of the language, TTCN version 3 (TTCN-3), is standardized by ETSI (ES 201 873 series) and the ITU-T (Z.140 series).

NOTE: In earlier versions of the language TTCN stands for Tree and Tabular Combined Notation. The new meaning Testing and Test Control Notation is more apt for TTCN-3.

Applicable to telecom and datacom testing

Typical areas of application for TTCN-3 are protocols, services, APIs, software modules etc. TTCN-3 is not restricted to conformance testing. It can be used in many areas, for example:

• Interoperability testing


• Robustness testing


• Performance testing


• Regression testing


• System testing


• Integration testing, etc.

A modern programming Language
With its new syntax TTCN-3 has the look and feel of a modern programming language. This general purpose, flexible and user friendly test language is easier to learn, easier to use, and easier to implement.
TTCN-3 capabilities are attracting users from a wide range of technologies. The language is becoming an integral component in ETSI members’ own development processes. This reduces the necessity for special training and allows standardized test suites to be readily adapted and extended to specific needs.

Well-proven testing capabilities retained
TTCN-3 has retained (and even improved) much of the well-proven testing-specific capabilities of earlier versions:

• Dynamic concurrent testing configurations


• Synchronous and asynchronous communication mechanisms


• Encoding information and other attributes (including user extensibility)


• Data and signature templates with a powerful matching mechanisms


• Test verdict mechanisms


• Test suite parameterisation and test case selection mechanisms


• Harmonized with ASN.1 (and potentially with other languages such as IDL)


• Well-defined syntax, interchange format and static semantics


• Optional presentation forma (tabular and graphical)


• Precise execution algorithm (operational semantics)


• Test suite and test system control


Different presentation formats
The TTCN-3 standard includes several (optional) presentation formats. The text-based Core Language (ES 201 873-1) will be the natural choice for those used to a conventional programming environment.
However, the developers of TTCN-3 were well aware of the considerable investment already made in TTCN and ES 201 873-2 defines a tabular format (TFT) that is familiar to users of older versions of TTCN. ES 201 873-3 defines a graphical format (GFT) which expresses the tests in an intuitive and easily readable form. There are also hooks in the language that facilitate the development of proprietary, non-standardized presentation formats, if required.

No. Plugtests have been around for many years, though less in the telecommunications world. They are also known as "PlugFests", "Interoperability event", "Group tests".

Most of the participants are equipment manufacturers (vendors). But often operators are experimenting with the standard as well, writing their own implementations to get a better understanding of the standard and of potential problems, and so do participate.