ETSI ES 203 119-1 V1.4.1 (2018-05)

ETSI STANDARD
Methods for Testing and Specification (MTS);
The Test Description Language (TDL);
Part 1: Abstract Syntax and Associated Semantics

�
2 ETSI ES 203 119-1 V1.4.1 (2018-05)

Reference
RES/MTS-203119-1v1.4.1
Keywords
language, MBT, methodology, model, testing,
TSS&TP, TTCN-3, UML
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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
The present document can be downloaded from:
http://www.etsi.org/standards-search
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 ETSI ES 203 119-1 V1.4.1 (2018-05)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 10
4 Basic Principles . 10
4.1 What is TDL? . 10
4.2 Design Considerations . 11
4.3 Principal Design Approach. 12
4.4 Document Structure . 13
4.5 Notational Conventions . 14
4.6 OCL Constraints Requirements . 14
4.7 Conformance . 14
5 Foundation . 15
5.1 Overview . 15
5.2 Abstract Syntax and Classifier Description . 15
5.2.1 Element . 15
5.2.2 NamedElement . 16
5.2.3 PackageableElement . 16
5.2.4 Package . 17
5.2.5 ElementImport . 17
5.2.6 Comment . 18
5.2.7 Annotation . 19
5.2.8 AnnotationType . 20
5.2.9 TestObjective . 20
6 Data . 20
6.1 Overview . 20
6.2 Data Definition - Abstract Syntax and Classifier Description . 21
6.2.1 DataResourceMapping . 21
6.2.2 MappableDataElement . 22
6.2.3 DataElementMapping . 22
6.2.4 ParameterMapping . 23
6.2.5 DataType . 24
6.2.6 DataInstance . 24
6.2.7 SimpleDataType . 25
6.2.8 SimpleDataInstance . 25
6.2.9 StructuredDataType . 26
6.2.10 Member . 26
6.2.11 StructuredDataInstance . 27
6.2.12 MemberAssignment . 28
6.2.13 CollectionDataType . 29
6.2.14 CollectionDataInstance . 29
6.2.15 ProcedureSignature . 30
6.2.16 ProcedureParameter . 30
6.2.17 ParameterKind . 31
6.2.18 Parameter . 32
6.2.19 FormalParameter . 32
6.2.20 Variable . 32
ETSI
4 ETSI ES 203 119-1 V1.4.1 (2018-05)
6.2.21 Action . 33
6.2.22 Function . 33
6.2.23 UnassignedMemberTreatment . 33
6.2.24 PredefinedFunction . 34
6.3 Data Use - Abstract Syntax and Classifier Description . 35
6.3.1 DataUse . 35
6.3.2 ParameterBinding . 36
6.3.3 MemberReference . 37
6.3.4 StaticDataUse . 38
6.3.5 DataInstanceUse . 38
6.3.6 SpecialValueUse . 39
6.3.7 AnyValue . 40
6.3.8 AnyValueOrOmit . 40
6.3.9 OmitValue. 40
6.3.10 DynamicDataUse . 41
6.3.11 FunctionCall . 42
6.3.12 FormalParameterUse . 42
6.3.13 VariableUse . 42
6.3.14 PredefinedFunctionCall . 43
7 Time . 44
7.1 Overview . 44
7.2 Abstract Syntax and Classifier Description . 44
7.2.1 Time . 44
7.2.2 TimeLabel . 45
7.2.3 TimeLabelUse . 45
7.2.4 TimeLabelUseKind . 46
7.2.5 TimeConstraint . 46
7.2.6 TimeOperation . 49
7.2.7 Wait . 50
7.2.8 Quiescence . 50
7.2.9 Timer . 52
7.2.10 TimerOperation . 52
7.2.11 TimerStart . 52
7.2.12 TimerStop . 53
7.2.13 TimeOut . 53
8 Test Configuration . 54
8.1 Overview . 54
8.2 Abstract Syntax and Classifier Description . 54
8.2.1 GateType . 54
8.2.2 GateTypeKind . 55
8.2.3 GateInstance . 55
8.2.4 ComponentType . 56
8.2.5 ComponentInstance . 56
8.2.6 ComponentInstanceRole . 57
8.2.7 GateReference . 57
8.2.8 Connection . 58
8.2.9 TestConfiguration . 59
9 Test Behaviour . 60
9.1 Overview . 60
9.2 Test Description - Abstract Syntax and Classifier Description . 60
9.2.1 TestDescription . 60
9.2.2 BehaviourDescription . 61
9.3 Combined Behaviour - Abstract Syntax and Classifier Description . 62
9.3.1 Behaviour . 62
9.3.2 Block . 63
9.3.3 LocalExpression . 64
9.3.4 CombinedBehaviour . 65
9.3.5 SingleCombinedBehaviour . 65
9.3.6 CompoundBehaviour . 66
9.3.7 BoundedLoopBehaviour . 66
ETSI
5 ETSI ES 203 119-1 V1.4.1 (2018-05)
9.3.8 UnboundedLoopBehaviour . 67
9.3.9 OptionalBehaviour . 67
9.3.10 MultipleCombinedBehaviour . 69
9.3.11 AlternativeBehaviour . 69
9.3.12 ConditionalBehaviour . 72
9.3.13 ParallelBehaviour . 72
9.3.14 ExceptionalBehaviour . 73
9.3.15 DefaultBehaviour . 76
9.3.16 InterruptBehaviour . 76
9.3.17 PeriodicBehaviour . 77
9.4 Atomic Behaviour - Abstract Syntax and Classifier Description . 78
9.4.1 AtomicBehaviour . 78
9.4.2 Break . 79
9.4.3 Stop . 79
9.4.4 VerdictAssignment . 80
9.4.5 Assertion . 80
9.4.6 Interaction . 81
9.4.7 Message . 83
9.4.8 ProcedureCall . 84
9.4.9 Target . 87
9.4.10 ValueAssignment . 88
9.4.11 TestDescriptionReference . 89
9.4.12 ComponentInstanceBinding . 91
9.4.13 ActionBehaviour . 92
9.4.14 ActionReference . 93
9.4.15 InlineAction . 94
9.4.16 Assignment . 94
10 Predefined TDL Model Instances . 95
10.1 Overview . 95
10.2 Predefined Instances of the 'SimpleDataType' Element . 95
10.2.1 Boolean . 95
10.2.2 Integer . 95
10.2.3 String . 95
10.2.4 Verdict . 95
10.3 Predefined Instances of 'SimpleDataInstance' Element . 96
10.3.1 true . 96
10.3.2 false . 96
10.3.3 pass . 96
10.3.4 fail . 96
10.3.5 inconclusive . 96
10.4 Predefined Instances of 'Time' Element . 96
10.4.1 Second . 96
10.5 Predefined Instances of the 'PredefinedFunction' Element . 96
10.5.1 Overview . 96
10.5.2 Functions of Return Type 'Boolean' . 97
10.5.3 Functions of Return Type 'Integer' . 97
10.5.4 Functions of Return Type of Instance of 'Time' . 98
Annex A (informative): Technical Representation of the TDL Meta-Model . 99
Annex B (informative): Examples of a TDL Concrete Syntax . 100
B.1 Introduction . 100
B.2 A 3GPP Conformance Example in Textual Syntax . 100
B.3 An IMS Interoperability Example in Textual Syntax . 102
B.4 An Example Demonstrating TDL Data Concepts . 104
B.5 TDL Textual Syntax Reference . 106
B.5.1 Conventions for the TDLan Syntax Definition . 106
B.5.2 TDL Textual Syntax EBNF Production Rules . 106
ETSI
6 ETSI ES 203 119-1 V1.4.1 (2018-05)
Annex C (informative): Bibliography . 111
History . 112

ETSI
7 ETSI ES 203 119-1 V1.4.1 (2018-05)
Intellectual Property Rights
Essential patents
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
server (https://ipr.etsi.org/).
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.
Trademarks
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.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
The present document is part 1 of a multi-part deliverable covering the Test Description Language, as identified below:
Part 1: "Abstract Syntax and Associated Semantics";
Part 2: "Graphical Syntax";
Part 3: "Exchange Format";
Part 4: "Structured Test Objective Specification (Extension)";
Part 5: "UML Profile for TDL";
Part 6: "Mapping to TTCN-3";
Part 7: "Extended Test Configurations".
Modal verbs terminology
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
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
8 ETSI ES 203 119-1 V1.4.1 (2018-05)
1 Scope
The present document specifies the abstract syntax of the Test Description Language (TDL) in the form of a ®
meta-model based on the OMG Meta Object Facility™ (MOF) [1]. It also specifies the semantics of the individual
elements of the TDL meta-model. The intended use of the present document is to serve as the basis for the development
of TDL concrete syntaxes aimed at TDL users and to enable TDL tools such as documentation generators, specification
analysers and code generators.
The specification of concrete syntaxes for TDL is outside the scope of the present document. However, for illustrative
purposes, an example of a possible textual syntax together with its application on some existing ETSI test descriptions
are provided.
® ®
NOTE: OMG , UML , OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.
2 References
2.1 Normative 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
referenced 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.
The following referenced documents are necessary for the application of the present document.
[1] OMG® formal/13-06-01: "OMG Meta Object Facility™ (MOF) Core Specification V2.4.1".
NOTE: Available at http://www.omg.org/spec/MOF/2.4.1/.
[2] OMG® formal/11-08-06: "OMG Unified Modeling Language™ (OMG UML) Superstructure,
Version 2.4.1".
NOTE: Available at http://www.omg.org/spec/UML/2.4.1/.
[3] OMG® formal/14-02-03: "Object Constraint Language™ (OCL), Version 2.4".
NOTE: Available at http://www.omg.org/spec/OCL/2.4/.
[4] Void.
[5] ETSI ES 203 119-3 (V1.2.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 3: Exchange Format".
[6] ETSI ES 203 119-4 (V1.2.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 4: Structured Test Objective Specification (Extension)".
[7] ISO/IEC 9646-1:1994: "Information technology - Open Systems Interconnection -- Conformance
testing methodology and framework -- Part 1: General concepts".
ETSI
9 ETSI ES 203 119-1 V1.4.1 (2018-05)
2.2 Informative 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
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
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-1 (V4.5.1): "Methods for Testing and Specification (MTS); The Testing and
Test Control Notation version 3; Part 1: TTCN-3 Core Language".
[i.2] ETSI TS 136 523-1 (V10.2.0): "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification (3GPP TS 36.523-1 version 10.2.0 Release 10)".
[i.3] ETSI TS 186 011-2: "Core Network and Interoperability Testing (INT); IMS NNI Interoperability
Test Specifications (3GPP Release 10); Part 2: Test descriptions for IMS NNI Interoperability".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
abstract syntax: graph structure representing a TDL specification in an independent form of any particular encoding
action: any procedure carried out by a component of a test configuration or an actor during test execution
actor: abstraction of entities outside a test configuration that interact directly with the components of that test
configuration
component: active element of a test configuration that is either in the role tester or system under test
concrete syntax: particular representation of a TDL specification, encoded in a textual, graphical, tabular or any other
format suitable for the users of this language
interaction: any form of communication between components that is accompanied with an exchange of data
meta-model: modelling elements representing the abstract syntax of a language
system under test (SUT): role of a component within a test configuration whose behaviour is validated when executing
a test description
TDL model: instance of the TDL meta-model
TDL specification: representation of a TDL model given in a concrete syntax
test configuration: specification of a set of components that contains at least one tester component and one system
under test component plus their interconnections via gates and connections
test description: specification of test behaviour that runs on a given test configuration
test verdict: result from executing a test description
tester: role of a component within a test configuration that controls the execution of a test description against the
components in the role system under test
ETSI
10 ETSI ES 203 119-1 V1.4.1 (2018-05)
tester-input event: event that occurs at a component in the role tester and determines the subsequent behaviour of this
tester component
NOTE: Tester-input events in the present document are the following:
Quiescence.
TimeOut.
An 'Interaction' with a 'Target' that in turn—via its 'GateReference'—refers to a
'ComponentInstance' in the role 'Tester'. If the source of an 'Interaction' is also a tester then it is not
a tester-input event.
: semantical concept denoting an undefined data value
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ADT Abstract Data Type
EBNF Extended Backus-Naur Form
IEC International Electrotechnical Commission
IMS IP Multimedia Subsystem
ISO International Organization for Standardization
MBT Model-Based Testing
MOF Meta-Object Facility™
OCL Object Constraint Language™
OMG Object Management Group®
SUT System Under Test
TDD Test Driven Development
TDL Test Description Language
TTCN-3 Testing and Test Control Notation version 3
UML Unified Modelling Language®
URI Unified Resource Identifier
XML eXtensible Markup Language
4 Basic Principles
4.1 What is TDL?
TDL is a language that supports the design and documentation of formal test descriptions that may be the basis for the
implementation of executable tests in a given test framework, such as TTCN-3 [i.1]. Application areas of TDL that will
benefit from this homogeneous approach to the test design phase include:
• Manual design of test descriptions from a test purpose specification, user stories in test driven development or
other sources.
• Representation of test descriptions derived from other sources such as MBT test generation tools, system
simulators, or test execution traces from test runs.
TDL supports the design of black-box tests for distributed, concurrent real-time systems. It is applicable to a wide range
of tests including conformance tests, interoperability tests, tests of real-time properties and security tests based on attack
traces.
TDL clearly separates the specification of tests from their implementation by providing an abstraction level that lets
users of TDL focus on the task of describing tests that cover the given test objectives rather than getting involved in
implementing these tests to ensure their fault detection capabilities onto an execution framework.
ETSI
11 ETSI ES 203 119-1 V1.4.1 (2018-05)
TDL is designed to support different abstraction levels of test specification. On one hand, the concrete syntax of the
TDL meta-model may hide meta-model elements that are not needed for a declarative (more abstract) style of
specifying test descriptions. For example, a declarative test description could work with the time operations wait and
quiescence instead of explicit timers and operations on timers (see clause 9).
On the other hand, an imperative (less abstract or refined) style of a test description supported by a dedicated concrete
syntax could provide additional means necessary to derive executable test descriptions from declarative test
descriptions. For example, an imperative test description could include timers and timer operations necessary to
implement the reception of SUT output at a tester component and further details. It is expected that most details of a
refined, imperative test description can be generated automatically from a declarative test description. Supporting
different levels of abstraction by a single TDL meta-model offers the possibility of working within a single language
and using the same tools, simplifying the test development process that way.
4.2 Design Considerations
TDL makes a clear distinction between concrete syntax that is adjustable to different application domains and a
common abstract syntax, which a concrete syntax is mapped to (an example concrete syntax is provided in annex B).
The definition of the abstract syntax for a TDL specification plays the key role in offering interchangeability and
unambiguous semantics of test descriptions. It is defined in the present document in terms of a MOF meta-model.
A TDL specification consists of the following major parts that are also reflected in the meta-model:
• A test configuration consisting of at least one tester and at least one SUT component and connections among
them reflecting the test environment.
• A set of test descriptions, each of them describing one test scenario based on interactions between the
components of a given test configuration and actions of components or actors. The control flow of a test
description is expressed in terms of sequential, alternative, parallel, iterative, etc. behaviour.
• A set of data definitions that are used in interactions and as parameters of test description invocations.
• Behavioural elements used in test descriptions that operate on time.
Using these major ingredients, a TDL specification is abstract in the following sense:
• Interactions between tester and SUT components of a test configuration are considered to be atomic and not
detailed further. For example, an interaction can represent a message exchange, a remote function/procedure
call, or a shared variable access.
• All behavioural elements within a test description are totally ordered, unless it is specified otherwise. That is,
there is an implicit synchronization mechanism assumed to exist between the components of a test
configuration.
• The behaviour of a test description represents the expected, foreseen behaviour of a test scenario assuming an
implicit test verdict mechanism, if it is not specified otherwise. If the specified behaviour of a test description
is executed, the 'pass' test verdict is assumed. Any deviation from this expected behaviour is considered to be a
failure of the SUT, therefore the 'fail' verdict is assumed.
• An explicit verdict assignment may be used if in a certain case there is a need to override the implicit verdict
setting mechanism (e.g. to assign 'inconclusive' or any user-d
...

SLOVENSKI STANDARD
01-januar-2019
0HWRGH]DSUHVNXãDQMHLQVSHFLILFLUDQMH076-H]LN]DRSLVSUHVNXVD7'/
GHO$EVWUDNWQDVNODGQMDLQSULSDGDMRþHSRPHQRVORYMH
Methods for Testing and Specification (MTS) - The Test Description Language (TDL) -
Part 1: Abstract Syntax and Associated Semantics
Ta slovenski standard je istoveten z: ETSI ES 203 119-1 V1.4.1 (2018-05)
ICS:
35.060 Jeziki, ki se uporabljajo v Languages used in
informacijski tehniki in information technology
tehnologiji
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI STANDARD
Methods for Testing and Specification (MTS);
The Test Description Language (TDL);
Part 1: Abstract Syntax and Associated Semantics

�
2 ETSI ES 203 119-1 V1.4.1 (2018-05)

Reference
RES/MTS-203119-1v1.4.1
Keywords
language, MBT, methodology, model, testing,
TSS&TP, TTCN-3, UML
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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
The present document can be downloaded from:
http://www.etsi.org/standards-search
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3 ETSI ES 203 119-1 V1.4.1 (2018-05)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 10
4 Basic Principles . 10
4.1 What is TDL? . 10
4.2 Design Considerations . 11
4.3 Principal Design Approach. 12
4.4 Document Structure . 13
4.5 Notational Conventions . 14
4.6 OCL Constraints Requirements . 14
4.7 Conformance . 14
5 Foundation . 15
5.1 Overview . 15
5.2 Abstract Syntax and Classifier Description . 15
5.2.1 Element . 15
5.2.2 NamedElement . 16
5.2.3 PackageableElement . 16
5.2.4 Package . 17
5.2.5 ElementImport . 17
5.2.6 Comment . 18
5.2.7 Annotation . 19
5.2.8 AnnotationType . 20
5.2.9 TestObjective . 20
6 Data . 20
6.1 Overview . 20
6.2 Data Definition - Abstract Syntax and Classifier Description . 21
6.2.1 DataResourceMapping . 21
6.2.2 MappableDataElement . 22
6.2.3 DataElementMapping . 22
6.2.4 ParameterMapping . 23
6.2.5 DataType . 24
6.2.6 DataInstance . 24
6.2.7 SimpleDataType . 25
6.2.8 SimpleDataInstance . 25
6.2.9 StructuredDataType . 26
6.2.10 Member . 26
6.2.11 StructuredDataInstance . 27
6.2.12 MemberAssignment . 28
6.2.13 CollectionDataType . 29
6.2.14 CollectionDataInstance . 29
6.2.15 ProcedureSignature . 30
6.2.16 ProcedureParameter . 30
6.2.17 ParameterKind . 31
6.2.18 Parameter . 32
6.2.19 FormalParameter . 32
6.2.20 Variable . 32
ETSI
4 ETSI ES 203 119-1 V1.4.1 (2018-05)
6.2.21 Action . 33
6.2.22 Function . 33
6.2.23 UnassignedMemberTreatment . 33
6.2.24 PredefinedFunction . 34
6.3 Data Use - Abstract Syntax and Classifier Description . 35
6.3.1 DataUse . 35
6.3.2 ParameterBinding . 36
6.3.3 MemberReference . 37
6.3.4 StaticDataUse . 38
6.3.5 DataInstanceUse . 38
6.3.6 SpecialValueUse . 39
6.3.7 AnyValue . 40
6.3.8 AnyValueOrOmit . 40
6.3.9 OmitValue. 40
6.3.10 DynamicDataUse . 41
6.3.11 FunctionCall . 42
6.3.12 FormalParameterUse . 42
6.3.13 VariableUse . 42
6.3.14 PredefinedFunctionCall . 43
7 Time . 44
7.1 Overview . 44
7.2 Abstract Syntax and Classifier Description . 44
7.2.1 Time . 44
7.2.2 TimeLabel . 45
7.2.3 TimeLabelUse . 45
7.2.4 TimeLabelUseKind . 46
7.2.5 TimeConstraint . 46
7.2.6 TimeOperation . 49
7.2.7 Wait . 50
7.2.8 Quiescence . 50
7.2.9 Timer . 52
7.2.10 TimerOperation . 52
7.2.11 TimerStart . 52
7.2.12 TimerStop . 53
7.2.13 TimeOut . 53
8 Test Configuration . 54
8.1 Overview . 54
8.2 Abstract Syntax and Classifier Description . 54
8.2.1 GateType . 54
8.2.2 GateTypeKind . 55
8.2.3 GateInstance . 55
8.2.4 ComponentType . 56
8.2.5 ComponentInstance . 56
8.2.6 ComponentInstanceRole . 57
8.2.7 GateReference . 57
8.2.8 Connection . 58
8.2.9 TestConfiguration . 59
9 Test Behaviour . 60
9.1 Overview . 60
9.2 Test Description - Abstract Syntax and Classifier Description . 60
9.2.1 TestDescription . 60
9.2.2 BehaviourDescription . 61
9.3 Combined Behaviour - Abstract Syntax and Classifier Description . 62
9.3.1 Behaviour . 62
9.3.2 Block . 63
9.3.3 LocalExpression . 64
9.3.4 CombinedBehaviour . 65
9.3.5 SingleCombinedBehaviour . 65
9.3.6 CompoundBehaviour . 66
9.3.7 BoundedLoopBehaviour . 66
ETSI
5 ETSI ES 203 119-1 V1.4.1 (2018-05)
9.3.8 UnboundedLoopBehaviour . 67
9.3.9 OptionalBehaviour . 67
9.3.10 MultipleCombinedBehaviour . 69
9.3.11 AlternativeBehaviour . 69
9.3.12 ConditionalBehaviour . 72
9.3.13 ParallelBehaviour . 72
9.3.14 ExceptionalBehaviour . 73
9.3.15 DefaultBehaviour . 76
9.3.16 InterruptBehaviour . 76
9.3.17 PeriodicBehaviour . 77
9.4 Atomic Behaviour - Abstract Syntax and Classifier Description . 78
9.4.1 AtomicBehaviour . 78
9.4.2 Break . 79
9.4.3 Stop . 79
9.4.4 VerdictAssignment . 80
9.4.5 Assertion . 80
9.4.6 Interaction . 81
9.4.7 Message . 83
9.4.8 ProcedureCall . 84
9.4.9 Target . 87
9.4.10 ValueAssignment . 88
9.4.11 TestDescriptionReference . 89
9.4.12 ComponentInstanceBinding . 91
9.4.13 ActionBehaviour . 92
9.4.14 ActionReference . 93
9.4.15 InlineAction . 94
9.4.16 Assignment . 94
10 Predefined TDL Model Instances . 95
10.1 Overview . 95
10.2 Predefined Instances of the 'SimpleDataType' Element . 95
10.2.1 Boolean . 95
10.2.2 Integer . 95
10.2.3 String . 95
10.2.4 Verdict . 95
10.3 Predefined Instances of 'SimpleDataInstance' Element . 96
10.3.1 true . 96
10.3.2 false . 96
10.3.3 pass . 96
10.3.4 fail . 96
10.3.5 inconclusive . 96
10.4 Predefined Instances of 'Time' Element . 96
10.4.1 Second . 96
10.5 Predefined Instances of the 'PredefinedFunction' Element . 96
10.5.1 Overview . 96
10.5.2 Functions of Return Type 'Boolean' . 97
10.5.3 Functions of Return Type 'Integer' . 97
10.5.4 Functions of Return Type of Instance of 'Time' . 98
Annex A (informative): Technical Representation of the TDL Meta-Model . 99
Annex B (informative): Examples of a TDL Concrete Syntax . 100
B.1 Introduction . 100
B.2 A 3GPP Conformance Example in Textual Syntax . 100
B.3 An IMS Interoperability Example in Textual Syntax . 102
B.4 An Example Demonstrating TDL Data Concepts . 104
B.5 TDL Textual Syntax Reference . 106
B.5.1 Conventions for the TDLan Syntax Definition . 106
B.5.2 TDL Textual Syntax EBNF Production Rules . 106
ETSI
6 ETSI ES 203 119-1 V1.4.1 (2018-05)
Annex C (informative): Bibliography . 111
History . 112

ETSI
7 ETSI ES 203 119-1 V1.4.1 (2018-05)
Intellectual Property Rights
Essential patents
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
server (https://ipr.etsi.org/).
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.
Trademarks
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.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
The present document is part 1 of a multi-part deliverable covering the Test Description Language, as identified below:
Part 1: "Abstract Syntax and Associated Semantics";
Part 2: "Graphical Syntax";
Part 3: "Exchange Format";
Part 4: "Structured Test Objective Specification (Extension)";
Part 5: "UML Profile for TDL";
Part 6: "Mapping to TTCN-3";
Part 7: "Extended Test Configurations".
Modal verbs terminology
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
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
8 ETSI ES 203 119-1 V1.4.1 (2018-05)
1 Scope
The present document specifies the abstract syntax of the Test Description Language (TDL) in the form of a ®
meta-model based on the OMG Meta Object Facility™ (MOF) [1]. It also specifies the semantics of the individual
elements of the TDL meta-model. The intended use of the present document is to serve as the basis for the development
of TDL concrete syntaxes aimed at TDL users and to enable TDL tools such as documentation generators, specification
analysers and code generators.
The specification of concrete syntaxes for TDL is outside the scope of the present document. However, for illustrative
purposes, an example of a possible textual syntax together with its application on some existing ETSI test descriptions
are provided.
® ®
NOTE: OMG , UML , OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.
2 References
2.1 Normative 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
referenced 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.
The following referenced documents are necessary for the application of the present document.
[1] OMG® formal/13-06-01: "OMG Meta Object Facility™ (MOF) Core Specification V2.4.1".
NOTE: Available at http://www.omg.org/spec/MOF/2.4.1/.
[2] OMG® formal/11-08-06: "OMG Unified Modeling Language™ (OMG UML) Superstructure,
Version 2.4.1".
NOTE: Available at http://www.omg.org/spec/UML/2.4.1/.
[3] OMG® formal/14-02-03: "Object Constraint Language™ (OCL), Version 2.4".
NOTE: Available at http://www.omg.org/spec/OCL/2.4/.
[4] Void.
[5] ETSI ES 203 119-3 (V1.2.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 3: Exchange Format".
[6] ETSI ES 203 119-4 (V1.2.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 4: Structured Test Objective Specification (Extension)".
[7] ISO/IEC 9646-1:1994: "Information technology - Open Systems Interconnection -- Conformance
testing methodology and framework -- Part 1: General concepts".
ETSI
9 ETSI ES 203 119-1 V1.4.1 (2018-05)
2.2 Informative 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
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
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-1 (V4.5.1): "Methods for Testing and Specification (MTS); The Testing and
Test Control Notation version 3; Part 1: TTCN-3 Core Language".
[i.2] ETSI TS 136 523-1 (V10.2.0): "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 1: Protocol
conformance specification (3GPP TS 36.523-1 version 10.2.0 Release 10)".
[i.3] ETSI TS 186 011-2: "Core Network and Interoperability Testing (INT); IMS NNI Interoperability
Test Specifications (3GPP Release 10); Part 2: Test descriptions for IMS NNI Interoperability".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
abstract syntax: graph structure representing a TDL specification in an independent form of any particular encoding
action: any procedure carried out by a component of a test configuration or an actor during test execution
actor: abstraction of entities outside a test configuration that interact directly with the components of that test
configuration
component: active element of a test configuration that is either in the role tester or system under test
concrete syntax: particular representation of a TDL specification, encoded in a textual, graphical, tabular or any other
format suitable for the users of this language
interaction: any form of communication between components that is accompanied with an exchange of data
meta-model: modelling elements representing the abstract syntax of a language
system under test (SUT): role of a component within a test configuration whose behaviour is validated when executing
a test description
TDL model: instance of the TDL meta-model
TDL specification: representation of a TDL model given in a concrete syntax
test configuration: specification of a set of components that contains at least one tester component and one system
under test component plus their interconnections via gates and connections
test description: specification of test behaviour that runs on a given test configuration
test verdict: result from executing a test description
tester: role of a component within a test configuration that controls the execution of a test description against the
components in the role system under test
ETSI
10 ETSI ES 203 119-1 V1.4.1 (2018-05)
tester-input event: event that occurs at a component in the role tester and determines the subsequent behaviour of this
tester component
NOTE: Tester-input events in the present document are the following:
Quiescence.
TimeOut.
An 'Interaction' with a 'Target' that in turn—via its 'GateReference'—refers to a
'ComponentInstance' in the role 'Tester'. If the source of an 'Interaction' is also a tester then it is not
a tester-input event.
: semantical concept denoting an undefined data value
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ADT Abstract Data Type
EBNF Extended Backus-Naur Form
IEC International Electrotechnical Commission
IMS IP Multimedia Subsystem
ISO International Organization for Standardization
MBT Model-Based Testing
MOF Meta-Object Facility™
OCL Object Constraint Language™
OMG Object Management Group®
SUT System Under Test
TDD Test Driven Development
TDL Test Description Language
TTCN-3 Testing and Test Control Notation version 3
UML Unified Modelling Language®
URI Unified Resource Identifier
XML eXtensible Markup Language
4 Basic Principles
4.1 What is TDL?
TDL is a language that supports the design and documentation of formal test descriptions that may be the basis for the
implementation of executable tests in a given test framework, such as TTCN-3 [i.1]. Application areas of TDL that will
benefit from this homogeneous approach to the test design phase include:
• Manual design of test descriptions from a test purpose specification, user stories in test driven development or
other sources.
• Representation of test descriptions derived from other sources such as MBT test generation tools, system
simulators, or test execution traces from test runs.
TDL supports the design of black-box tests for distributed, concurrent real-time systems. It is applicable to a wide range
of tests including conformance tests, interoperability tests, tests of real-time properties and security tests based on attack
traces.
TDL clearly separates the specification of tests from their implementation by providing an abstraction level that lets
users of TDL focus on the task of describing tests that cover the given test objectives rather than getting involved in
implementing these tests to ensure their fault detection capabilities onto an execution framework.
ETSI
11 ETSI ES 203 119-1 V1.4.1 (2018-05)
TDL is designed to support different abstraction levels of test specification. On one hand, the concrete syntax of the
TDL meta-model may hide meta-model elements that are not needed for a declarative (more abstract) style of
specifying test descriptions. For example, a declarative test description could work with the time operations wait and
quiescence instead of explicit timers and operations on timers (see clause 9).
On the other hand, an imperative (less abstract or refined) style of a test description supported by a dedicated concrete
syntax could provide additional means necessary to derive executable test descriptions from declarative test
descriptions. For example, an imperative test description could include timers and timer operations necessary to
implement the reception of SUT output at a tester component and further details. It is expected that most details of a
refined, imperative test description can be generated automatically from a declarative test description. Supporting
different levels of abstraction by a single TDL meta-model offers the possibility of working within a single language
and using the same tools, simplifying the test development process that way.
4.2 Design Considerations
TDL makes a clear distinction between concrete syntax that is adjustable to different application domains and a
common abstract syntax, which a concrete syntax is mapped to (an example concrete syntax is provided in annex B).
The definition of the abstract syntax for a TDL specification plays the key role in offering interchangeability and
unambiguous semantics of test descriptions. It is defined in the present document in terms of a MOF meta-model.
A TDL specification consists of the following major parts that are also reflected in the meta-model:
• A test configuration consisting of at least one tester and at least one SUT component and connections among
them reflecting the test environment.
• A set of test descriptions, each of them describing one test scenario based on interactions between the
components of a given test configuration and actions of components or actors. The control flow of a test
description is expressed in terms of sequential, alternative, parallel, iterative, etc. behaviour.
• A set of data definitions that are used in interactions and as parameters of test description invocations.
• Behavioural elements used in test descripti
...