ETSI TR 103 119 V1.2.1 (2020-09)

Methods for Testing and Specification (MTS); The Test Description Language (TDL); Reference Implementation

RTR/MTS-TDL103119v121

General Information

• Status: Not Published
• Technical Committee: MTS TDL - Test Description Language
• Current Stage: 12 - Completion
• Due Date: 25-Sep-2020
• Completion Date: 18-Sep-2020

Standards Content (Sample)

ETSI TR 103 119 V1.2.1 (2020-09)






TECHNICAL REPORT
Methods for Testing and Specification (MTS);
The Test Description Language (TDL);
Reference Implementation

---------------------- Page: 1 ----------------------
2 ETSI TR 103 119 V1.2.1 (2020-09)



Reference
RTR/MTS-TDL103119v121
Keywords
MBT
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
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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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 2020.
All rights reserved.

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
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TR 103 119 V1.2.1 (2020-09)
Contents
Intellectual Property Rights . 5
Foreword. 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Basic Principles . 9
4.1 Introduction. 9
4.2 Implementation Scope . 9
4.3 Document Structure . 10
5 Graphical Representation Editor . 10
5.1 Scope and Requirements . 10
5.2 Architecture and Technology Foundation . 10
5.2.1 Graphical Editor . 10
5.2.2 Structured Test Objective Representation . 11
5.3 Implemented Facilities . 12
5.3.1 Creating Models . 12
5.3.2 Viewing and Editing Models . 16
5.3.3 Exporting Structured Test Objectives . 24
5.3.4 Validating Models . 26
5.4 Usage Instructions . 26
5.4.1 Development Environment . 26
5.4.2 End-user Instructions. 27
6 Using TDL with TOP . 29
6.1 Usage Scenarios . 29
6.2 Defining Structured Test Objectives . 29
6.2.0 Overview . 29
6.2.1 Domain part of TDL-TO . 30
6.2.2 Data definitions . 30
6.2.3 Configuration . 30
6.2.4 Test purpose behaviour . 31
6.3 Transforming Test Objectives into Test Descriptions . 32
6.3.1 Overview . 32
6.3.2 Data . 32
6.3.3 Configurations . 34
6.3.4 Behaviour . 35
6.4 Defining Test Descriptions . 36
6.4.1 Overview . 36
6.4.2 Data and Configuration . 36
6.4.3 Test Behaviour and Time . 37
6.5 Transforming Test Descriptions into TTCN-3 Test Cases. 38
6.5.1 Overview . 38
6.5.2 Data . 39
6.5.3 Configuration . 40
6.5.4 Behaviour . 41
7 UML Profile Editor . 42
7.1 Scope and Requirements . 42
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TR 103 119 V1.2.1 (2020-09)
7.2 Architecture and Technology Foundation . 42
7.3 Implemented Facilities . 43
7.3.1 Applying the Profile . 43
7.3.2 Hints for the Transformation of UP4TDL Models into TDL Models . 44
7.3.3 Editing Models with the Model Explorer . 44
7.3.4 Editing TDL-specific Properties with the TDL Property View . 45
7.3.5 Editing Models with TDL-specific Diagrams . 45
Annex A (informative): Technical Realization of the Reference Implementation . 49
History . 50


ETSI

---------------------- Page: 4 ----------------------
5 ETSI TR 103 119 V1.2.1 (2020-09)
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 Technical Report (TR) has been produced by ETSI Technical Committee Methods for Testing and Specification
(MTS).
NOTE: Eclipse™, Xtext™, Sirius™, EMF™, Papyrus™, GMF™, Epsilon™, EVL™ are the trade names of a
product supplied by the Eclipse Foundation. OMG®, XMI™, UML™, OCL™, MOF™ are the trade
names of a product supplied by 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
product named.
The present document is complementary to the multi-part deliverable covering the Test Description Language (TDL).
Full details of the entire series can be found in part 1 of the multi-part deliverable [i.13].
Modal verbs terminology
In the present document "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

---------------------- Page: 5 ----------------------
6 ETSI TR 103 119 V1.2.1 (2020-09)
1 Scope
The present document summarizes technical aspects related to the implementation of TDL within the TDL Open Source
Project (TOP). It describes the implementation details needed for the further development and integration of the tools. It
also provides usage instructions for end users.
The following tools and components are covered in the present document:
• implementation of the TDL meta-model;
• editor for the graphical representation format of TDL;
• multiple types of TDL model editors;
• facilities for checking the semantic validity of models according to the constraints specified in the TDL meta-
model;
• implementation and tool-support for the mapping TDL elements to TTCN-3 code;
• implementation of the UML profile for TDL; and
• editor supporting the creation and manipulation of UML models applying the UML profile for TDL.
NOTE: The implementation of the UML profile for TDL and the corresponding editor descriptions are not
aligned with the referenced versions of the TDL specification parts, but are related to an earlier release of
the TDL specification parts.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
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] Eclipse Foundation™ Eclipse IDE Website (last visited 08.04.2020).
NOTE: Available at https://eclipse.org.
[i.2] Eclipse Foundation™: Eclipse Xtext™ Website (last visited 08.04.2020).
NOTE: Available at https://eclipse.org/Xtext/index.html.
[i.3] Eclipse Foundation™: Eclipse Sirius™ Website (last visited 08.04.2020).
NOTE: Available at http://www.eclipse.org/sirius/index.html.
[i.4] Eclipse Foundation™: Eclipse Modeling Framework (EMF™) Website (last visited 08.04.2020).
NOTE: Available at http://www.eclipse.org/modeling/emf/.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TR 103 119 V1.2.1 (2020-09)
[i.5] Eclipse Foundation™: Eclipse Papyrus™ Modeling Environment Website (last visited
08.04.2020).
NOTE: Available at https://www.eclipse.org/papyrus/.
[i.6] Eclipse Foundation™: UML™ Profiles Repository Website (last visited 04.08.2020).
NOTE: Available at https://projects.eclipse.org/projects/modeling.upr.
[i.7] Eclipse Foundation™: Graphical Modeling Framework (GMF™) Website (last visited
08.04.2020).
NOTE: Available at http://www.eclipse.org/modeling/gmp/.
[i.8] "Object Constraint Language™ (OMG® OCL™), Version 2.4", formal/2014-02-03.
NOTE: Available at http://www.omg.org/spec/OCL/2.4/.
[i.9] Eclipse Foundation™: Eclipse OCL™ Website (last visited 08.04.2020).
NOTE: Available at https://projects.eclipse.org/projects/modeling.mdt.ocl.
[i.10] Plutext Pty Ltd: Docx4j Website (last visited 08.04.2020).
NOTE: Available at http://www.docx4java.org/trac/docx4j.
[i.11] "OMG® XML™ Metadata Interchange (XMI™) Specification", Version 2.4.2, formal/
2014-04-04.
NOTE: Available at http://www.omg.org/spec/MOF/2.4.2/.
[i.12] Eclipse FoundationTM: Epsilon™ Validation Language (EVL™) Website (last visited
08.04.2020).
NOTE: Available at http://www.eclipse.org/epsilon/doc/evl/.
[i.13] ETSI ES 203 119-1 (V1.5.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 1: Abstract Syntax and Associated Semantics".
[i.14] ETSI ES 203 119-2 (V1.4.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 2: Graphical Syntax".
[i.15] ETSI ES 203 119-3 (V1.4.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 3: Exchange Format".
[i.16] ETSI ES 203 119-4 (V1.4.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 4: Structured Test Objective Specification (Extension)".
[i.17] ETSI ES 203 119-5 (V1.1.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 5: UML Profile for TDL".
[i.18] ETSI ES 203 119-6 (V1.2.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 6: Mapping to TTCN-3".
[i.19] ETSI ES 203 119-7 (V1.2.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 7: Extended Test Configurations".
[i.20] ETSI ES 203 119-1 (V1.3.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 1: Abstract Syntax and Associated Semantics".
[i.21] ETSI EG 203 130 (V1.1.1): "Methods for Testing and Specification (MTS); Model-Based Testing
(MBT); Methodology for standardized test specification development".
[i.22] The Apache Software Foundation: Apache POI Website (last visited 08.04.2020).
NOTE: Available at https://poi.apache.org.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TR 103 119 V1.2.1 (2020-09)
[i.23] ETSI: The TDL Website (last visited 08.04.2020).
NOTE: Available at https://tdl.etsi.org.
[i.24] ETSI: The TDL Open Source Project Website (last visited 08.04.2020).
NOTE: Available at https://tdl.etsi.org/index.php/open-source.
[i.25] ETSI TS 136 321: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access
Control (MAC) protocol specification (3GPP TS 36.321)".
[i.26] ETSI TS 103 029: "IMS Network Testing (INT); IMS & EPC Interoperability test descriptions
(3GPP Release 10)".
[i.27] ETSI TS 129 214: "Universal Mobile Telecommunications System (UMTS); LTE; Policy and
charging control over Rx reference point (3GPP TS 29.214 version 15.6.0 Release 15)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
abstract syntax: graph structure representing a TDL specification in an independent form of any particular encoding
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
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
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
API Application Programming Interface
EBNF Extended Backus-Naur Form
EMF Eclipse Modelling Framework
EVL Epsilon Validation Language
GMF Graphical Modelling Framework
MBT Model-Based Testing
MOF Meta-Object Facility
OCL Object Constraint Language
OMG Object Management Group®
SUT System Under Test
TDL Test Description Language
TOP TDL Open Source Project
UML Unified Modelling Language
URI Unified Resource Identifier
XMI eXtensible Markup Language Metadata Interchange
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TR 103 119 V1.2.1 (2020-09)
4 Basic Principles
4.1 Introduction
To accelerate the adoption of TDL, an implementation of TDL is provided within TOP in order to lower the barrier to
entry for both users and tool vendors in getting started with using TDL. The implementation comprises graphical and
textual editors, as well as validation facilities, transformation functionalities, and other tools. In addition, the UML
profile for TDL and supporting editing facilities are implemented in order to enable application of TDL in UML-based
working environments and model-based testing approaches.
4.2 Implementation Scope
The implementation scope includes a graphical editor according to ETSI ES 203 119-2 [i.14] based on the Eclipse
platform [i.1] and related technologies, covering essential constructs of TDL. For creating and manipulating models, a
textual editor for ETSI ES 203 119-1 [i.13], annex B is implemented based on the Eclipse platform and related
technologies. The applicability of general purpose model editing facilities provided by the Eclipse platform and related
technologies is discussed as well.
For tools that need to import and export TDL models according to ETSI ES 203 119-3 [i.15], corresponding facilities
are implemented based on the Eclipse platform and related technologies. These facilities can be used to transform
textual representations based on ETSI ES 203 119-1 [i.13] into XMI [i.11] serializations according to ETSI
ES 203 119-3 [i.15] and can be integrated in custom tooling that builds on the Eclipse platform.
An implementation of ETSI ES 203 119-4 [i.16] includes a dedicated textual editor for structured test objectives, which
can be integrated in the textual editor for TDL. The implementation also includes facilities for exporting structured test
objectives to Word documents using customisable tabular templates.
An implementation of the UML profile for TDL includes a specification of the TDL UML profile abstract syntax
according to the mapping from the TDL meta-model to TDL stereotypes and UML meta-classes in ETSI
ES 203 119-5 [i.17]. It is integrated with the open source UML modelling environment Eclipse Papyrus [i.5] as an open
TDL UML profile implementation.
An implementation of ETSI ES 203 119-6 [i.18] includes a partial prototypical implementation of the TDL to TTCN-3
mapping based on the Eclipse platform.

Figure 4.2-1: TDL tool infrastructure
An schematic overview of the implementation is shown in Figure 4.2-1. The TDL exchange format specified in ETSI
ES 203 119-3 [i.15] serves as a bridge between the different tool components. Textual editors enable the creation and
manipulation of TDL models. The graphical editor is used to edit and visualize TDL models as diagrams.
Documentation generation, in particular for structured test objectives, can be plugged in to produce Word documents
for presenting parts of a TDL model in a format suitable for standardization documents. Test code generation, e.g. for
TTCN-3 can be plugged in to produce executable TTCN-3 code or TTCN-3 skeletons to be refined afterwards.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TR 103 119 V1.2.1 (2020-09)
The implementation is published as part of the TOP [i.24] on the TDL [i.23] website serving as a central hub for the
TDL community.
4.3 Document Structure
The present document contains three main technical clauses focusing on relevant technical details. The Graphical
Representation editor implementing ETSI ES 203 119-2 [i.14], as well as related facilities implementing ETSI
ES 203 119-1 [i.13], ETSI ES 203 119-3 [i.15] and ETSI ES 203 119-4 [i.16] are described in clause 5. Illustrative
examples and guidelines for the use of TDL to address common use cases with the help of the TOP are described in
clause 6. The UML Profile Editor implementing ETSI ES 203 119-5 [i.17] is described in clause 7.
NOTE: The UML Profile Editor for TDL complies to an earlier release of the TDL specification parts.
5 Graphical Representation Editor
5.1 Scope and Requirements
TDL graphical editor implementation has two major requirements. The main objective is to provide means to visualize
TDL models according to the graphical notation. The second objective is to facilitate layout of diagrams in a way that is
suitable for documentation. For the second purpose, it is essential to provide graphical editing capabilities. Although
often provided by modelling frameworks, the ability to graphically edit the underlying models (that is, to create new
elements and set their properties) is not considered essential for this implementation.
Eclipse provides several graphical modelling tools to help build editors. Sirius [i.3] was chosen for its declarative
approach that provides separation between meta-model mappings and implementations of graphical elements. With the
existence of predefined common graphical elements, such as containers and connectors, the effort of implementing a
graphical editor with a custom syntax in Sirius is only spent on the parts that diverge from those common elements.
Another area that requires a custom implementation is the layout of graphical elements. This covers both the absolute
placement of nodes on the diagram as well as the size and internal contents of each node. Due to the rather hierarchical
nature of the TDL graphical syntax, several additional base graphical elements are introduced. Some peculiar
limitations of Sirius have also been identified prior to the implementation, which also need appropriate workarounds.
The goal of implementing a diagram layout is to automate diagram creation to the extent that the sizes and contents of
graphical elements are adjusted by layout algorithms while the absolute placement of diagram elements is solved by
using built in layout implementations. This will guarantee that only minimal user interaction with the diagram editor is
needed for achieving the desired layouts.
Diagram export for documentation purposes is provided by the framework. The implementation can provide
complimentary export to the Word document format.
Due to the peculiarities and intended use of structured test objectives, it was determined that instead of graphical shapes
that can be exported as images, the graphical representation are realized as tables exported directly in a Word document
according to user-defined templates. These tables can then be manipulated further as necessary to fit in within an
existing document.
5.2 Architecture and Technology Foundation
5.2.1 Graphical Editor
The TDL graphical editor is built on top of the Eclipse platform to benefit from its wide range of modelling tools. The
main Eclipse projects that are used as basis for this implementation are shown in Figure 5.2.1-1. Sirius is a technology
that allows declarative creation of graphical editors that work with EMF models. It uses GMF [i.7] to create visual
diagram elements and link those to model objects. Model management and serialization is done by EMF [i.4].
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TR 103 119 V1.2.1 (2020-09)
Eclipse platform
EMF
TDL (XF)
TDL Ecore
Sirius
Diagram
Diagram
specification
GMF
TDL
Image
graphical
editor

NOTE: Components with grey background are part of the implementation that is covered by the present
document.

Figure 5.2.1-1: Dependencies and data flows of the TDL graphical editor
Every EMF model is based on a meta-model that
...