SIST ES 202 781 V1.1.1:2013

Methods for Testing and Specification (MTS) - The Testing and Test Control Notation version 3 - TTCN-3 Language Extensions: Configuration and Deployment Support

The present document defines the Configuration and Deployment Supportpackage of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services),
module testing, testing of CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3.
This package defines the TTCN-3 support for static test configurations. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

Metode za preskušanje in specificiranje (MTS) - 3. različica preskušanja in zapisa krmilnih preskusov - Razširitev nabora jezikov TTCN-3: Podpora konfiguriranju in uvajanju

Ta dokument določa paket za podporo konfiguriranju in uvajanju TTCN-3. TTCN-3 je mogoče uporabiti za specifikacijo vseh vrst reaktivnih sistemskih preskusov v okviru različnih komunikacijskih vrat. Običajna področja uporabe so preskušanje protokolov (vključno z mobilnimi in internetnimi protokoli), preskušanje storitev (vključno z dodatnimi storitvami), preskušanje modulov, preskušanje platform na osnovi CORBA, programski vmesniki (API) itd. TTCN-3 ni omejen na preskušanje skladnosti in se lahko uporabi za številne druge vrste preskušanja, vključno s preskušanjem interoperabilnosti, robustnosti, regresije, sistema in integracije. Specifikacija preskuševalnih nizov za protokole fizične plasti ne spada na področje uporabe tega dokumenta. Paketi TTCN-3 so namenjeni določitvi dodatnih pojmov TTCN-3, ki niso obvezni kot pojmi v temeljnem jeziku TTCN-3, ampak so izbirni kot del paketa, ki je primeren za namenske aplikacije in/ali uporabe TTCN-3.
Paket določa podporo TTCN-3 za statične preskusne konfiguracije. Zasnova paketa TTCN-3 upošteva skladnost kombinirane uporabe temeljnega jezika z več paketi, vendar pa dejanske uporabe tega paketa in smernice zanj v kombinaciji z drugimi paketi ne spadajo na področje uporabe tega dokumenta.

General Information

• Status: Published
• Publication Date: 12-Feb-2013
• ICS: 35.060 - Languages used in information technology
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 19-Aug-2010
• Due Date: 24-Oct-2010
• Completion Date: 13-Feb-2013
• Ref Project: ETSI ES 202 781 V1.1.1 (2010-08) - Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Configuration and Deployment Support

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ES 202 781 V1.1.1:2013
01-marec-2013
0HWRGH]DSUHVNXãDQMHLQVSHFLILFLUDQMH076UD]OLþLFDSUHVNXãDQMDLQ]DSLVD
NUPLOQLKSUHVNXVRY5D]ãLULWHYQDERUDMH]LNRY77&13RGSRUDNRQILJXULUDQMXLQ
XYDMDQMX
Methods for Testing and Specification (MTS) - The Testing and Test Control Notation
version 3 - TTCN-3 Language Extensions: Configuration and Deployment Support
Ta slovenski standard je istoveten z: ES 202 781 Version 1.1.1
ICS:
35.060 Jeziki, ki se uporabljajo v Languages used in
informacijski tehniki in information technology
tehnologiji
SIST ES 202 781 V1.1.1:2013 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ES 202 781 V1.1.1:2013

---------------------- Page: 2 ----------------------

SIST ES 202 781 V1.1.1:2013

ETSI ES 202 781 V1.1.1 (2010-08)
ETSI Standard


Methods for Testing and Specification (MTS);
The Testing and Test Control Notation version 3;
TTCN-3 Language Extensions:
Configuration and Deployment Support

---------------------- Page: 3 ----------------------

SIST ES 202 781 V1.1.1:2013
 2 ETSI ES 202 781 V1.1.1 (2010-08)



Reference
DES/MTS-00112 T3EXT_CONFDEP
Keywords
conformance, testing, TTCN
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2010.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 4 ----------------------

SIST ES 202 781 V1.1.1:2013
 3 ETSI ES 202 781 V1.1.1 (2010-08)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Package conformance and compatibility . 7
5 Package Concepts for the Core Language . 8
5.1 The special configuration type: configuration . 9
5.2 The configuration function . 9
5.3 Starting a static test configuration . 10
5.4 Destruction of static test configurations . 11
5.5 Creation of static test components . 11
5.6 Establishment of static connections and static mappings . 12
5.7 Test case definitions for static test configuration . 13
5.8 Executing test cases on static test configurations . 14
5.9 Further restrictions . 15
6 Package Semantics . 15
6.1 Replacement of short forms. 17
6.2 Order of replacement steps . 18
6.3 Flow graph representation of TTCN-3 behaviour . 18
6.4 Flow graph construction procedure . 19
6.5 Flow graph representation of configuration functions . 19
6.6 Retrieval of start nodes of flow graphs . 20
6.7 Module state . 20
6.8 Accessing the module state . 20
6.9 Configuration state . 21
6.10 Accessing the configuration state . 21
6.11 Entity states . 22
6.12 Accessing entity states . 24
6.13 Handling of connections among ports . 25
6.14 Handling of port states . 25
6.15 The evaluation procedure for a TTCN-3 module . 26
6.16 Evaluation phases . 26
6.17 Phase I: Initialization . 27
6.18 Phase II: Update . 28
6.19 Phase III: Selection . 28
6.20 Phase IV: Execution . 28
6.21 Global functions . 29
6.22 Clear port operation . 29
6.23 Configuration function call. 30
6.24 Connect operation. 31
6.25 Create operation . 32
6.26 Flow graph segment . 34
6.27 Flow graph segment . 35
6.28 Flow graph segment . 36
6.29 Flow graph segment . 36
6.30 Execute statement . 37
6.31 Flow graph segment . 38
6.32 Flow graph segment . 38
ETSI

---------------------- Page: 5 ----------------------

SIST ES 202 781 V1.1.1:2013
 4 ETSI ES 202 781 V1.1.1 (2010-08)
6.33 Flow graph segment . 38
6.34 Flow graph segment . 40
6.35 Flow graph segment . 42
6.36 Halt port operation. 43
6.37 Kill component operation . 44
6.38 Flow graph segment . 46
6.39 Flow graph segment . 46
6.40 Kill execution statement . 48
6.41 Kill configuration operation . 49
6.42 Map operation . 49
6.43 Start port operation . 50
6.44 Stop component operation . 51
6.45 Flow graph segment . 53
6.46 Flow graph segment . 53
6.47 Flow graph segment . 54
6.48 Stop port operation . 55
6.49 Flow graph segment . 57
6.50 Flow graph segment . 58
6.51 Flow graph segment . 59
7 TRI Extensions for the Package . 59
7.1 Changes and extensions to clause 5.5.2 of ES 201 873-5 [3] Connection handling operations . 59
7.2 Extensions to clause 6 of ES 201 873-5 [3] Java language mapping . 61
7.3 Extensions to clause 7 of ES 201 873-5 [3] ANSI C language mapping. 61
7.4 Extensions to clause 8 of ES 201 873-5 [3] C++ language mapping . 61
8 TCI Extensions for the Package . 62
8.1 Extensions to clause 7.2.1.1 of ES 201 873-6 [4] Management . 62
8.2 Extensions to clause 7.3.1.1 of ES 201 873-6 [4] TCI TM required . 62
8.3 Extensions to clause 7.3.1.2 of ES 201 873-6 [4] TCI TM provided . 62
8.4 Extensions to clause 7.3.3.1 of ES 201 873-6 [4] TCI CH required . 63
8.5 Extensions to clause 7.3.3.2 of ES 201 873-6 [4] TCI CH provided . 64
8.6 Extensions to clause 7.3.4 of ES 201 873-6 [4] TCI-TL provided . 64
8.7 Extensions to clause 8 of ES 201 873-6 [4] Java language mapping . 66
8.8 Extensions to clause 9 of ES 201 873-6 [4] ANSI C language mapping. 67
8.9 Extensions to clause 10 of ES 201 873-6 [4] C++ language mapping . 68
8.10 Extensions to clause 11 of ES 201 873-6 W3C XML mapping . 69
Annex A (normative): BNF and static semantics . 71
A.1 Additional TTCN-3 terminals . 71
A.2 Modified TTCN-3 syntax BNF productions . 71
A.3 Additional TTCN-3 syntax BNF productions . 72
History . 73

ETSI

---------------------- Page: 6 ----------------------

SIST ES 202 781 V1.1.1:2013
 5 ETSI ES 202 781 V1.1.1 (2010-08)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
The present document relates to the multi-part standard covering the Testing and Test Control Notation version 3, as
identified below:
ES 201 873-1 [1]: "TTCN-3 Core Language";
ES 201 873-2 [i.1]: "TTCN-3 Tabular presentation Format (TFT)";
ES 201 873-3 [i.2]: "TTCN-3 Graphical presentation Format (GFT)";
ES 201 873-4 [2]: "TTCN-3 Operational Semantics";
ES 201 873-5 [3]: "TTCN-3 Runtime Interface (TRI)";
ES 201 873-6 [4]: "TTCN-3 Control Interface (TCI)";
ES 201 873-7 [i.3]: "Using ASN.1 with TTCN-3";
ES 201 873-8 [i.4]: "The IDL to TTCN-3 Mapping";
ES 201 873-9 [i.5]: "Using XML schema with TTCN-3";
ES 201 873-10 [i.6]: "TTCN-3 Documentation Comment Specification".
ETSI

---------------------- Page: 7 ----------------------

SIST ES 202 781 V1.1.1:2013
 6 ETSI ES 202 781 V1.1.1 (2010-08)
1 Scope
The present document defines the Configuration and Deployment Supportpackage of TTCN-3. TTCN-3 can be used for
the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application
are protocol testing (including mobile and Internet protocols), service testing (including supplementary services),
module testing, testing of CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can
be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing.
The specification of test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
This package defines the TTCN-3 support for static test configurations.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[2] ETSI ES 201 873-4: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 4: TTCN-3 Operational Semantics".
[3] ETSI ES 201 873-5: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)".
[4] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 6: TTCN-3 Control Interface (TCI)".
[5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -Conformance testing
methodology and framework; Part 1: General concepts".
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI ES 201 873-2: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 2: TTCN-3 Tabular presentation Format (TFT)".
ETSI

---------------------- Page: 8 ----------------------

SIST ES 202 781 V1.1.1:2013
 7 ETSI ES 202 781 V1.1.1 (2010-08)
[i.2] ETSI ES 201 873-3: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 3: TTCN-3 Graphical presentation Format (GFT)".
[i.3] ETSI ES 201 873-7: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 7: Using ASN.1 with TTCN-3".
[i.4] ETSI ES 201 873-8: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 8: The IDL to TTCN-3 Mapping".
[i.5] ETSI ES 201 873-9: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 9: Using XML with TTCN-3".
[i.6] ETSI ES 201 873-10: "Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 10: TTCN-3 Documentation Comment Specification".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 201 873-1 [1], ES 201 873-4 [2],
ES 201 873-5 [3], ES 201 873-6 [4] and ISO/IEC 9646-1 [5] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 201 873-1 [1], ES 201 873-4 [2],
ES 201 873-5 [3], ES 201 873-6 [4], ISO/IEC 9646-1 [5] and the following apply:
MTC Main Test Component
PTC Parallel Test Component.
4 Package conformance and compatibility
The package presented in the present document is identified by the package tag:
"TTCN-3:2009 Static Test Configurations" - to be used with modules complying with the present
document.
For an implementation claiming to conform to this package version, all features specified in the present document shall
be implemented consistently with the requirements given in the present document and in ES 201 873-1 [1] and
ES 201 873-4 [2].
The package presented in the present document is compatible to:
• ES 201 873-1 [1] version 4.2.1;
• ES 201 873-2 [i.1] version 3.2.1;
• ES 201 873-3 [i.2] version 3.2.1;
• ES 201 873-4 [2] version 4.2.1;
• ES 201 873-5 [3] version 4.2.1;
• ES 201 873-6 [4] version 4.2.1;
• ES 201 873-7 [i.3] version 4.2.1;
• ES 201 873-8 [i.4] version 4.2.1;
ETSI

---------------------- Page: 9 ----------------------

SIST ES 202 781 V1.1.1:2013
 8 ETSI ES 202 781 V1.1.1 (2010-08)
• ES 201 873-9 [i.5] version 4.2.1;
• ES 201 873-10 [i.6] version 4.2.1.
If later versions of those parts are available and should be used instead, the compatibility to the package presented in the
present document has to be checked individually.
5 Package Concepts for the Core Language
This package defines the TTCN-3 means to define static test configurations. A static test configuration is a test
configuration with a lifetime that is not bound to a single test case. The test components of a static test configuration
may be used by several test cases. This package realizes the following concepts:
• A special configuration function is introduced which can only be called in the control part of a TTCN-3
module to create static test configurations. The configuration function returns a handle of the predefined type
configuration to access an existing static test configuration.
• A static test configuration consists of static test components, a test system interface, static connections and
static mappings. These constituents have the following semantics:
- A static test component is a special kind of test component that can only be created during the creation of
a static test configuration and can only be destroyed during the destruction of a static test configuration.
By definition, the MTC of a static test configuration is a static test component.
- The test system interface of a static test configuration plays the same role as the test system interface of a
test configuration created by a test case.
- A static connection is a connection between static test components. It can only be established during the
creation of a static test configuration and only be destroyed during the destruction of a static test
configuration.
- A static mapping is a mapping of a port of a static test component to a port of the test system interface of
a static test configuration. Such a mapping can only be established during the creation of a static test
configuration and only be destroyed during the destruction of a static test configuration.
• A static test configuration can be used by several test cases. For this the test case is started on a previously
created static test configuration. This means:
- The body of the test case is executed on the MTC of the static test configuration.
- The MTC may start behaviour on other static test components of the static test configuration.
- Static test components may create, start, stop and kill normal and alive test components. The lifetime of
these components is bound to the actual test case that is executed on the static test configuration. In case
that a normal and alive test component is not destroyed explicitly by another test component, it is
implicitly destroyed when the test case ends.
- During test case execution non-static connections and non-static mappings may be established. The
lifetime of non-static connections and non-static mappings is bound to the actual test case that is
executed on the static test configuration. In case that a non-static connection or a non-static mapping is
not destroyed explicitly by another test component, it is implicitly destroyed when the test case ends.
• Component timers and variables of static test components are not reset or reininitialized when a test case is
started on a static test configuration. They remain in the same state as when they were left after the creation of
the static test configuration or after the termination of a previous test case. This allows to transfer information
from one test case to another.
• Ports of static test components are not emptied or restarted when a test case is started on a static test
configuration. For example, this allows a delayed handling of SUT responses like e.g. repetitive status
messages, during the test campaign. In addition, all port operations (i.e. clear, start, stop and halt) are
disallowed for ports of static test components. All ports of a static test component remain started during the
whole lifetime of a static test configuration.
ETSI

---------------------- Page: 10 ----------------------

SIST ES 202 781 V1.1.1:2013
 9 ETSI ES 202 781 V1.1.1 (2010-08)
• In contrast to component timers, variables and ports, the verdict and the default handling is reset. This means
all activated defaults are deactiviated, all local verdicts and the global verdict are set to none.
5.1 The special configuration type: configuration
The special configuration type configuration is a handle fo
...

Final draft ETSI ES 202 781 V0.0.4 (2010-05)
ETSI Standard


Methods for Testing and Specification (MTS);
The Testing and Test Control Notation version 3;
TTCN-3 Language Extensions:
Configuration and Deployment Support

---------------------- Page: 1 ----------------------
2 Final draft ETSI ES 202 781 V0.0.4 (2010-05)



Reference
DES/MTS-00112 T3EXT_CONFDEP
Keywords
conformance, testing, TTCN
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2010.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 Final draft ETSI ES 202 781 V0.0.4 (2010-05)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Package conformance and compatibility . 7
5 Package Concepts for the Core Language . 8
5.1 The special configuration type: configuration . 9
5.2 The configuration function . 9
5.3 Starting a static test configuration . 10
5.4 Destruction of static test configurations . 11
5.5 Creation of static test components . 11
5.6 Establishment of static connections and static mappings . 12
5.7 Test case definitions for static test configuration . 13
5.8 Executing test cases on static test configurations . 14
5.9 Further restrictions . 15
6 Package Semantics . 15
6.1 Replacement of short forms. 17
6.2 Order of replacement steps . 18
6.3 Flow graph representation of TTCN-3 behaviour . 18
6.4 Flow graph construction procedure . 19
6.5 Flow graph representation of configuration functions . 19
6.6 Retrieval of start nodes of flow graphs . 20
6.7 Module state . 20
6.8 Accessing the module state . 20
6.9 Configuration state . 21
6.10 Accessing the configuration state . 21
6.11 Entity states . 22
6.12 Accessing entity states . 24
6.13 Handling of connections among ports . 25
6.14 Handling of port states . 25
6.15 The evaluation procedure for a TTCN-3 module . 26
6.16 Evaluation phases . 26
6.17 Phase I: Initialization . 27
6.18 Phase II: Update . 28
6.19 Phase III: Selection . 28
6.20 Phase IV: Execution . 28
6.21 Global functions . 29
6.22 Clear port operation . 29
6.23 Configuration function call. 30
6.24 Connect operation. 31
6.25 Create operation . 32
6.26 Flow graph segment . 34
6.27 Flow graph segment . 35
6.28 Flow graph segment . 36
6.29 Flow graph segment . 36
6.30 Execute statement . 37
6.31 Flow graph segment . 38
6.32 Flow graph segment . 38
ETSI

---------------------- Page: 3 ----------------------
4 Final draft ETSI ES 202 781 V0.0.4 (2010-05)
6.33 Flow graph segment . 38
6.34 Flow graph segment . 40
6.35 Flow graph segment . 42
6.36 Halt port operation. 43
6.37 Kill component operation . 44
3.38 Flow graph segment . 46
6.39 Flow graph segment . 46
6.40 Kill execution statement . 48
6.41 Kill configuration operation . 49
6.42 Map operation . 49
6.43 Start port operation . 50
6.44 Stop component operation . 51
6.45 Flow graph segment . 53
6.46 Flow graph segment . 53
6.47 Flow graph segment . 54
6.48 Stop port operation . 55
6.49 Flow graph segment . 57
6.50 Flow graph segment . 58
6.51 Flow graph segment . 59
7 TRI Extensions for the Package . 59
7.1 Changes and extensions to clause 5.5.2 of ES 201 873-5 [3] Connection handling operations . 59
7.2 Extensions to clause 6 of ES 201 873-5 [3] Java language mapping . 61
7.3 Extensions to clause 7 of ES 201 873-5 [3] ANSI C language mapping. 61
7.4 Extensions to clause 8 of ES 201 873-5 [3] C++ language mapping . 61
8 TCI Extensions for the Package . 62
8.1 Extensions to clause 7.2.1.1 of ES 201 873-6 [4] Management . 62
8.2 Extensions to clause 7.3.1.1 of ES 201 873-6 [4] TCI TM required . 62
8.3 Extensions to clause 7.3.1.2 of ES 201 873-6 [4] TCI TM provided . 62
8.4 Extensions to clause 7.3.3.1 of ES 201 873-6 [4] TCI CH required . 63
8.5 Extensions to clause 7.3.3.2 of ES 201 873-6 [4] TCI CH provided . 64
8.6 Extensions to clause 7.3.4 of ES 201 873-6 [4] TCI-TL provided . 64
8.7 Extensions to clause 8 of ES 201 873-6 [4] Java language mapping . 66
8.8 Extensions to clause 9 of ES 201 873-6 [4] ANSI C language mapping. 67
8.9 Extensions to clause 10 of ES 201 873-6 [4] C++ language mapping . 68
8.10 Extensions to clause 11 of ES 201 873-6 W3C XML mapping . 69
Annex A (normative): BNF and static semantics . 71
A.1 Additional TTCN-3 terminals . 71
A.2 Modified TTCN-3 syntax BNF productions . 71
A.3 Additional TTCN-3 syntax BNF productions . 72
History . 73

ETSI

---------------------- Page: 4 ----------------------
5 Final draft ETSI ES 202 781 V0.0.4 (2010-05)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and
Specification (MTS), and is now submitted for the ETSI standards Membership Approval Procedure.
The present document relates to the multi-part standard covering the Testing and Test Control Notation version 3, as
identified below:
ES 201 873-1 [1]: "TTCN-3 Core Language";
ES 201 873-2 [i.1]: "TTCN-3 Tabular presentation Format (TFT)";
ES 201 873-3 [i.2]: "TTCN-3 Graphical presentation Format (GFT)";
ES 201 873-4 [2]: "TTCN-3 Operational Semantics";
ES 201 873-5 [3]: "TTCN-3 Runtime Interface (TRI)";
ES 201 873-6 [4]: "TTCN-3 Control Interface (TCI)";
ES 201 873-7 [i.3]: "Using ASN.1 with TTCN-3";
ES 201 873-8 [i.4]: "The IDL to TTCN-3 Mapping";
ES 201 873-9 [i.5]: "Using XML schema with TTCN-3";
ES 201 873-10 [i.6]: "TTCN-3 Documentation Comment Specification".
ETSI

---------------------- Page: 5 ----------------------
6 Final draft ETSI ES 202 781 V0.0.4 (2010-05)
1 Scope
The present document defines the Configuration and Deployment Supportpackage of TTCN-3. TTCN-3 can be used for
the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application
are protocol testing (including mobile and Internet protocols), service testing (including supplementary services),
module testing, testing of CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can
be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing.
The specification of test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
This package defines the TTCN-3 support for static test configurations.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[2] ETSI ES 201 873-4: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 4: TTCN-3 Operational Semantics".
[3] ETSI ES 201 873-5: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)".
[4] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 6: TTCN-3 Control Interface (TCI)".
[5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -Conformance testing
methodology and framework; Part 1: General concepts".
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI ES 201 873-2: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 2: TTCN-3 Tabular presentation Format (TFT)".
ETSI

---------------------- Page: 6 ----------------------
7 Final draft ETSI ES 202 781 V0.0.4 (2010-05)
[i.2] ETSI ES 201 873-3: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 3: TTCN-3 Graphical presentation Format (GFT)".
[i.3] ETSI ES 201 873-7: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 7: Using ASN.1 with TTCN-3".
[i.4] ETSI ES 201 873-8: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 8: The IDL to TTCN-3 Mapping".
[i.5] ETSI ES 201 873-9: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 9: Using XML with TTCN-3".
[i.6] ETSI ES 201 873-10: "Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 10: TTCN-3 Documentation Comment Specification".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 201 873-1 [1], ES 201 873-4 [2],
ES 201 873-5 [3], ES 201 873-6 [4] and ISO/IEC 9646-1 [5] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 201 873-1 [1], ES 201 873-4 [2],
ES 201 873-5 [3], ES 201 873-6 [4], ISO/IEC 9646-1 [5] and the following apply:
MTC Main Test Component
PTC Parallel Test Component.
4 Package conformance and compatibility
The package presented in the present document is identified by the package tag:
"TTCN-3:2009 Static Test Configurations" - to be used with modules complying with the present
document.
For an implementation claiming to conform to this package version, all features specified in the present document shall
be implemented consistently with the requirements given in the present document and in ES 201 873-1 [1] and
ES 201 873-4 [2].
The package presented in the present document is compatible to:
• ES 201 873-1 [1] version 4.2.1;
• ES 201 873-2 [i.1] version 3.2.1;
• ES 201 873-3 [i.2] version 3.2.1;
• ES 201 873-4 [2] version 4.2.1;
• ES 201 873-5 [3] version 4.2.1;
• ES 201 873-6 [4] version 4.2.1;
• ES 201 873-7 [i.3] version 4.2.1;
• ES 201 873-8 [i.4] version 4.2.1;
ETSI

---------------------- Page: 7 ----------------------
8 Final draft ETSI ES 202 781 V0.0.4 (2010-05)
• ES 201 873-9 [i.5] version 4.2.1;
• ES 201 873-10 [i.6] version 4.2.1.
If later versions of those parts are available and should be used instead, the compatibility to the package presented in the
present document has to be checked individually.
5 Package Concepts for the Core Language
This package defines the TTCN-3 means to define static test configurations. A static test configuration is a test
configuration with a lifetime that is not bound to a single test case. The test components of a static test configuration
may be used by several test cases. This package realizes the following concepts:
• A special configuration function is introduced which can only be called in the control part of a TTCN-3
module to create static test configurations. The configuration function returns a handle of the predefined type
configuration to access an existing static test configuration.
• A static test configuration consists of static test components, a test system interface, static connections and
static mappings. These constituents have the following semantics:
- A static test component is a special kind of test component that can only be created during the creation of
a static test configuration and can only be destroyed during the destruction of a static test configuration.
By definition, the MTC of a static test configuration is a static test component.
- The test system interface of a static test configuration plays the same role as the test system interface of a
test configuration created by a test case.
- A static connection is a connection between static test components. It can only be established during the
creation of a static test configuration and only be destroyed during the destruction of a static test
configuration.
- A static mapping is a mapping of a port of a static test component to a port of the test system interface of
a static test configuration. Such a mapping can only be established during the creation of a static test
configuration and only be destroyed during the destruction of a static test configuration.
• A static test configuration can be used by several test cases. For this the test case is started on a previously
created static test configuration. This means:
- The body of the test case is executed on the MTC of the static test configuration.
- The MTC may start behaviour on other static test components of the static test configuration.
- Static test components may create, start, stop and kill normal and alive test components. The lifetime of
these components is bound to the actual test case that is executed on the static test configuration. In case
that a normal and alive test component is not destroyed explicitly by another test component, it is
implicitly destroyed when the test case ends.
- During test case execution non-static connections and non-static mappings may be established. The
lifetime of non-static connections and non-static mappings is bound to the actual test case that is
executed on the static test configuration. In case that a non-static connection or a non-static mapping is
not destroyed explicitly by another test component, it is implicitly destroyed when the test case ends.
• Component timers and variables of static test components are not reset or reininitialized when a test case is
started on a static test configuration. They remain in the same state as when they were left after the creation of
the static test configuration or after the termination of a previous test case. This allows to transfer information
from one test case to another.
• Ports of static test components are not emptied or restarted when a test case is started on a static test
configuration. For example, this allows a delayed handling of SUT responses like e.g. repetitive status
messages, during the test campaign. In addition, all port operations (i.e. clear, start, stop and halt) are
disallowed for ports of static test components. All ports of a static test component remain started during the
whole lifetime of a static test configuration.
ETSI

---------------------- Page: 8 ----------------------
9 Final draft ETSI ES 202 781 V0.0.4 (2010-05)
• In contrast to component timers, variables and ports, the verdict and the default handling is reset. This means
all activated defaults are deactiviated, all local verdicts and the global verdict are set to none.
5.1 The special configuration type: configuration
The special configuration type configuration is a handle for static test configurations. The special value null is
available to indicate an undefined configuration reference, e.g. for the initialization of variables to handle a static test
configuration.
Values of type configuration shall be the result of configuration functions, they can be checked for equality,
e.g. to check if two variables store the same value, and they can be used in execute statements for starting a test case
on an existing static test configuration and in kill configuration statements to destroy an existing static test
configuration.
EXAMPLES:
var configuration myStaticConfig := null; // Declaration and initialization of a
      // configuration variable.

myStaticConfig := aStaticConfig();  // Assigns a value to the previously declared
      // configuration variable. It is assumed that
      //aStaticConfig() is a configuration function.

myStaticConfig.kill    // Kills the static test configuration
...