 |
Business | Industries | Finance | Tax |
| Index: > A B C D E F G H I J K L M N O P Q R S T U V W X Y Z |
|
|||||
Up to version 2 the language is a unconventionally written in tables and called 'Tree And Tabular Notation'. Reading and editing this language requires special TTCN editors. From version 3 on TTCN was renamed to 'Testing and Test Control Notation', is closer to current programming languages and can be edited with traditional editors. TTCN-3 is more even flexible than TTCN-2 can be used besides for protocol testing also for testing traditional software.
All versions need for execution dedicated compilers or interpreters.
TTCN has been widely used by e.g. ETSI, ITU for testing of telecommunication protocols. Conformance test case s of ETSI standards like ISDN, DECT, GSM, EDGE, 3G have been written in TTCN. Since a few years it has been used also used for testing of other protocol standards e.g. Bluetooth, IP.
Execution of those test case s against products (e.g. phones, mobile phones or network elements) isused to verify that the protocol implementation in those products are meeting the requirements defined by the telecommunication standards.
TTCN is often combined with ASN.1.
While conformance testing mean test execution against a well defined test case e.g. written in TTCN, plug-test s (often also called interoperability testing) are test cases executed against other products of opposite role of the tested product. E.g. Mail-Client against Mail-server, phone against network, Bluetooth headset against Bluetooth phone). Plug-test s are e.g. often executed at so called unplug-fests .
Internet standards such as IETF use today mainly so called plug-test s for test execution.
Conformance-tests and plug-test s complement each other. If well done, interoperability errors found with plug-test s should lead to definition of new conformance test cases that cover the failure situation.| Politics | Business | Finance |
 |
 |
 |
|