SIST ES 202 785 V1.6.1:2019

SLOVENSKI STANDARD
SIST ES 202 785 V1.6.1:2019
01-januar-2019

Metode za preskušanje in specificiranje (MTS) - 3. različica zapisa preskušanja in

Methods for Testing and Specification (MTS) - The Testing and Test Control Notation

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

The present document may be made available in electronic versions and/or in print. The content of any electronic and/or

print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any

existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the

print of the Portable Document Format (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

If you find errors in the present document, please send your comment to one of the following services:

No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying

The content of the PDF version shall not be modified without the written authorization of ETSI.

DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and

Intellectual Property Rights ................................................................................................................................ 4

Foreword ............................................................................................................................................................. 4

Modal verbs terminology .................................................................................................................................... 5

1 Scope ........................................................................................................................................................ 6

2 References ................................................................................................................................................ 6

2.1 Normative references ......................................................................................................................................... 6

2.2 Informative references ........................................................................................................................................ 7

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 Extension to ETSI ES 201 873-1, clause 5 (Basic language elements) .............................................................. 8

5.2 Extension to ETSI ES 201 873-1, clause 6 (Types and values).......................................................................... 9

5.3 Extension to ETSI ES 201 873-1, clause 7 (Expressions) ................................................................................ 14

5.4 Extension to ETSI ES 201 873-1, clause 8 (Modules) ..................................................................................... 15

5.5 Extension to ETSI ES 201 873-1, clause 10 (Declaring constants) .................................................................. 15

5.6 Extension to ETSI ES 201 873-1, clause 11 (Declaring variables) .................................................................. 15

5.7 Extension to ETSI ES 201 873-1, clause 15 (Declaring templates) ................................................................. 16

5.8 Extension to ETSI ES 201 873-1, clause 16 (Functions, altsteps and test cases) ............................................. 16

5.9 Extension to ETSI ES 201 873-1, clause 19 (Basic program statements) ........................................................ 17

5.10 Extension to ETSI ES 201 873-1, clause 20 (Statements and operations for alternative behaviours) .............. 18

5.11 Extension to ETSI ES 201 873-1, clause 21 (Configuration Operations) ........................................................ 18

5.12 Extension to ETSI ES 201 873-1, clause 26 (Module control) ........................................................................ 19

5.13 Extension to ETSI ES 201 873-1, annex A (BNF and static semantics) .......................................................... 20

5.13.0 New keywords and TTCN-3 syntax BNF productions ............................................................................... 20

5.13.1 Changes to ETSI ES 201 873-1, clause A.1.6 (TTCN-3 syntax BNF productions) ................................... 20

6 Package semantics .................................................................................................................................. 21

6.1 Replacements ................................................................................................................................................... 21

6.2 Activate statement ............................................................................................................................................ 21

6.3 Replacements in Execute statement's operational semantics ............................................................................ 22

6.3.0 Execute statement ....................................................................................................................................... 22

6.3.1 Flow graph segment ....................................................................................... 23

6.4 Replacements in Function call's operational semantics .................................................................................... 24

6.4.0 Function call ............................................................................................................................................... 24

6.4.1 Flow graph segment .................................................................................................. 26

6.4.2 Flow graph segment ............................................................................................... 26

6.5 Start component operation ................................................................................................................................ 26

7 TRI extensions for the package .............................................................................................................. 29

8 TCI extensions for the package .............................................................................................................. 29

8.1 Extensions to ETSI ES 201 873-6, clause 7 (TTCN-3 control interface and operations)................................. 29

8.2 Extensions to ETSI ES 201 873-6, clause 8 (Java language mapping) ............................................................ 30

8.3 Extensions to ETSI ES 201 873-6, clause 9 (ANSI C language mapping) ...................................................... 31

8.4 Extensions to ETSI ES 201 873-6, clause 10 (C++ language mapping) .......................................................... 31

8.5 Extensions to ETSI ES 201 873-6, clause 11 (W3C XML mapping) .............................................................. 33

9 Extensions to TTCN-3 documentation comment specification for the package .................................... 43

9.1 Extensions to ETSI ES 201 873-10, annex A (Where Tags can be used) ........................................................ 43

History .............................................................................................................................................................. 45

IPRs essential or potentially essential to normative deliverables 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

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

The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.

ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no

right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does

not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.

This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification

The use of underline (additional text) highlights the differences between base document and extended

The present document relates to the multi-part standard ETSI ES 201 873 covering the Testing and Test Control

NOTE: Part 2 of the multi-part deliverable ETSI ES 201 873 is in status "historical" and is not maintained.

In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and

"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of

"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

The present document defines the Behaviour Types package 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

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

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

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

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

Referenced documents which are not found to be publicly available in the expected location might be found at

NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee

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

[2] ETSI ES 201 873-4: "Methods for Testing and Specification (MTS); The Testing and Test Control

[3] ETSI ES 201 873-5: "Methods for Testing and Specification (MTS); The Testing and Test Control

[4] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control

[5] ISO/IEC 9646-1: "Information technology -- Open Systems Interconnection -- Conformance

[6] ETSI ES 202 784: "Methods for Testing and Specification (MTS); The Testing and Test Control

[7] 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".

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

NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee

The following referenced documents are not necessary for the application of the present document but they assist the

[i.1] ETSI ES 201 873-7: "Methods for Testing and Specification (MTS); The Testing and Test Control

[i.2] ETSI ES 201 873-8: "Methods for Testing and Specification (MTS); The Testing and Test Control

[i.3] ETSI ES 201 873-9: "Methods for Testing and Specification (MTS); The Testing and Test Control

For the purposes of the present document, the terms and definitions given in ETSI ES 201 873-1 [1], ETSI

ES 201 873-4 [2], ETSI ES 201 873-5 [3], ETSI ES 201 873-6 [4], ISO/IEC 9646-1 [5] and the following apply:

behaviour definition: definition of an altstep, function, or testcase that can be called explicitly

NOTE: A control part is not considered a behaviour definition, because it cannot be called explicitly.

For the purposes of the present document, the abbreviations given in ETSI ES 201 873-1 [1], ETSI ES 201 873-4 [2],

"TTCN-3:2009 Behaviour Types" - 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; in ETSI ES 201 873-1 [1] and ETSI

ES 201 873-4 [2]. All features marked [AdvancedParameterization] have to be implemented only in case that this

If later versions of those parts are available and should be used instead, the compatibility to the package presented in the

If later versions of those packages are available and should be used instead, the compatibility to the package presented

module Value parameterization Static at start of run-time all basic types, all user-defined types and address

type Value parameterization Static at compile-time all basic types, all user-defined types and address

template Value and template Dynamic at run-time all basic types, all user-defined types, address

function Value, template, port and Dynamic at run-time all basic types, all user-defined types, address

altstep Value, template, port and Dynamic at run-time all basic types, all user-defined types, address

testcase Value, template, port and Dynamic at run-time all basic types and of all user-defined types,

signature Value and template Dynamic at run-time all basic types, all user-defined types and address

NOTE: Record of, set of, enumerated, port, component and sub-type definitions do not allow parameterization.

Behaviour types such as altstep, function, and testcase may be used to define flexible behaviour of TTCN-3

Behaviour types are the set of identifiers of altstep, function, and testcase definitions with a specific parameter list, runs

on, system and return clauses. They denote those altsteps, functions, and testcases, respectively, defined in the test suite

"(" [ { ( FormalValuePar | FormalTimerPar | FormalTemplatePar | FormalPortPar ) [","] } ] ")"

"(" [ { ( FormalValuePar | FormalTimerPar | FormalTemplatePar | FormalPortPar ) [","] } ] ")"

NOTE 1: [AdvancedParameterization] If the advanced parameterization package [6] is also supported, behaviour

NOTE 2: runs on self indicates a specific compatibility check, see extension of clause 6.3.

a) The rules for formal parameter lists shall be followed as defined in the TTCN-3 Core Language [1] clause 5.4

b) Behaviour types of kind altstep may have a runs on clause, behaviour types of type function may

have a runs on clause and a return clause, behaviour types of kind testcase shall have a runs on

EXAMPLE 2: Function type with one parameter, a runs on clause and a return value.

EXAMPLE 4: Testcase type without parameter, with a runs on clause and a system clause.

The values of a behaviour type are the identifiers of altsteps, functions, and testcases with compatible parameters and

runs on, system and return clauses. Both predefined and user-defined, including external, functions can be used

as values. Type compatibility of behaviour types is defined in the extension to clause 6.3.5 within the present document.

The literal behaviour values are the identifiers of the predefined and user-defined altsteps, (external) functions, and

testcases and the special value null. The special value null is available to indicate an undefined behaviour value,

e.g. for the initialization of variables. Behaviour values can be passed around as parameters and behaviour values can be

stored. Behaviour values can be used, together with a corresponding list of actual parameters, to invoke the behaviours

in statements and expressions. Behaviour values can also be used, again together with a corresponding list of actual

The only operators (see clause 7.1 of the TTCN-3 core language [1]) on behaviour values that are defined are the check

a) Values of a behaviour type with a runs on self clause shall not be sent to another test component.

b) Values of a behaviour type with a runs on self clause shall not be used in a start test component

Deferred behaviour types are the set of altstep, function, and testcase behaviors with possible runs on, system and mtc

clauses paired with their actual parameter list which can be passed to the activate, start and execute operations,

respectively. They denote those instantiations of altsteps, functions, and testcases defined in the test suite that have

Deferred behaviour types define references to executable behaviors. Deferred function behaviour types define the set of

behaviours that can be started on a ptc. Deferred altstep behaviour types define the set of behaviours that can be

activated as default alternatives. Deferred testcase behaviour types define the set of behaviours that can be executed

The actual parameters of a deferred behaviour value are evaluated when creating the value.

a) The same restrictions apply for the start, activate and execute operations that apply for functions, altsteps and

The values of a deferred behaviour type are the un-executed instantiations of altsteps, functions, and testcases together

with their compatible actual parameters which have compatible runs on, system and mtc clauses to those in the

behaviour type. Type compatibility of deferred behaviour types is defined in the extension to clause 6.3.5 within the

The literal deferred behaviour values are the function instance expressions of the user-defined altsteps, (external)