ETSI ES 203 119-4 V1.4.1 (2020-08)
Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 4: Structured Test Objective Specification (Extension)
Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 4: Structured Test Objective Specification (Extension)
RES/MTS-TDL4v141
Metode za preskušanje in specificiranje (MTS) - Jezik za opis preskusa (TDL) - 4. del: Specifikacija cilja strukturiranega preskušanja (razširitev)
General Information
Buy Standard
Standards Content (Sample)
ETSI ES 203 119-4 V1.4.1 (2020-08)
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Test Description Language (TDL);
Part 4: Structured Test Objective Specification (Extension)
---------------------- Page: 1 ----------------------
2 ETSI ES 203 119-4 V1.4.1 (2020-08)
Reference
RES/MTS-TDL4v141
Keywords
language, MBT, methodology, 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 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 ES 203 119-4 V1.4.1 (2020-08)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Basic principles . 7
4.1 Structured Test Objective Specification . 7
4.2 Document Structure . 8
4.3 Notational Conventions . 8
4.4 Element Operations . 8
4.5 Conformance . 9
5 Meta-Model Extensions . 9
5.1 Overview . 9
5.2 Foundation Abstract Syntax and Classifier Description . 9
5.2.1 Entity . 9
5.2.2 Event . 10
5.2.3 PICS . 10
5.3 Test Objective Abstract Syntax and Classifier Description . 11
5.3.1 StructuredTestObjective . 11
5.3.2 PICSReference . 12
5.3.3 InitialConditions . 12
5.3.4 ExpectedBehaviour . 13
5.3.5 FinalConditions . 13
5.4 Events Abstract Syntax and Classifier Description . 14
5.4.1 EventSequence . 14
5.4.2 RepeatedEventSequence . 15
5.4.3 EventOccurrence . 15
5.4.4 EventOccurrenceSpecification . 16
5.4.5 EntityReference . 17
5.4.6 EventReference . 17
5.5 Data Abstract Syntax and Classifier Description . 18
5.5.1 Value . 18
5.5.2 LiteralValue . 18
5.5.3 Content . 19
5.5.4 LiteralValueReference . 19
5.5.5 ContentReference . 20
5.5.6 DataReference . 20
5.6 Event Templates Abstract Syntax and Classifier Description . 21
5.6.1 EventSpecificationTemplate . 21
5.6.2 EventTemplateOccurrence . 22
5.6.3 EntityBinding . 22
6 Graphical Syntax Extensions. 23
6.1 Foundation . 23
6.1.1 Entity . 23
6.1.2 Event . 23
ETSI
---------------------- Page: 3 ----------------------
4 ETSI ES 203 119-4 V1.4.1 (2020-08)
6.1.3 PICS . 24
6.1.4 Comment . 24
6.2 Test Objective . 26
6.2.1 StructuredTestObjective . 26
6.3 Events . 28
6.3.1 EventSequence . 28
6.3.2 RepeatedEventSequence . 29
6.3.3 EventOccurrence . 29
6.3.4 EventOccurrenceSpecification . 30
6.3.5 EntityReference . 30
6.3.6 EventReference . 31
6.4 Data . 32
6.4.1 Value . 32
6.4.2 LiteralValue . 32
6.4.3 Content . 33
6.4.4 LiteralValueReference . 34
6.4.5 ContentReference . 34
6.4.6 DataReference . 35
6.4.7 StaticDataUse . 35
6.4.8 AnyValue . 36
6.4.9 AnyValueOrOmit . 36
6.4.10 OmitValue. 37
6.4.11 DataInstanceUse . 37
6.4.12 ArgumentSpecification . 37
6.5 Time . 38
6.5.1 TimeLabel . 38
6.5.2 TimeConstraint . 38
6.6 Event Templates . 39
6.6.1 EventSpecificationTemplate . 39
6.6.2 EventTemplateOccurrence . 40
6.6.3 EntityBinding . 41
7 Exchange Format Extensions . 41
Annex A (informative): Textual Syntax. 42
A.0 Overview . 42
A.1 A 3GPP Test Objective in Textual Syntax . 42
A.2 An IMS Test Objective in Textual Syntax . 43
Annex B (informative): Textual Syntax BNF Production Rules . 44
B.0 Overview . 44
B.1 Conventions . 44
B.2 Production Rules . 44
History . 49
ETSI
---------------------- Page: 4 ----------------------
5 ETSI ES 203 119-4 V1.4.1 (2020-08)
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 4 of a multi-part deliverable. Full details of the entire series can be found in part 1 [1].
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.
Introduction
Test purposes play an essential role in test specification processes at ETSI. Currently, TDL treats test purposes, and test
objectives in general as informal text without any additional structural constraints. This extension package for TDL
refines and formalizes test objective specification within TDL by introducing relevant meta-model concepts and a
corresponding syntactical notation, both of which are related to TPLan ETSI ES 202 553 [i.1] and TPLan-like notations
already established at ETSI. This enables test purpose specification to enter the modelling world and paves the way for
improved tool support and better structured test objectives, as well as additional formal verification and validation
facilities down the road by integrating and unifying the means for the specification of test purposes and test
descriptions, while relying on the same underlying meta-model and benefiting from other related technologies built
around this meta-model.
The present document describes the relevant abstract syntax (meta-model) extensions as well as the corresponding
concrete syntactical notation.
NOTE: The use of underline (additional text) and strikethrough (deleted text) highlights the differences between
base document and extended documents.
ETSI
---------------------- Page: 5 ----------------------
6 ETSI ES 203 119-4 V1.4.1 (2020-08)
1 Scope
The present document specifies an extension of the Test Description Language (TDL) enabling the specification of
structured test objectives. The extension covers the necessary additional constructs in the abstract syntax, their
semantics, as well as the concrete graphical syntactic notation for the added constructs. In addition textual syntax
examples of the TDL Structured Test Objectives extensions as well as BNF rules for a textual syntax for TDL with the
Structured Test Objectives extensions are provided. The intended use of the present document is to serve both as a
foundation for TDL tools implementing support for the specification of structured test objectives, as well as a reference
for end users applying the standardized syntax for the specification of structured test objectives with TDL.
® ®
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
https://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] 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".
[2] ETSI ES 203 119-2 (V1.4.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 2: Graphical Syntax".
[3] ETSI ES 203 119-3 (V1.4.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 3: Exchange Format".
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 202 553 (V1.2.1): "Methods for Testing and Specification (MTS); TPLan: A notation for
expressing Test Purposes".
[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)".
ETSI
---------------------- Page: 6 ----------------------
7 ETSI ES 203 119-4 V1.4.1 (2020-08)
[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 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI ES 203 119-1 [1] and the following apply:
context: set of circumstances related to the occurrence of an event
entity: object that may be involved in the occurrence of an event as part of a specific context
entity type: alias for additional meta-information that may be used to describe one or more entities
event: observable phenomenon or state that may occur in a specific context
NOTE: Related to a term of the same name defined in ETSI ES 202 553 [i.1].
event occurrence: description of the occurrence of an event in a specific context
event type: alias for additional meta-information that may be used to describe one or more events
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
BNF Backus-Naur Form
EBNF Extended Backus-Naur Form
IMS IP Multimedia Subsystem
IUT Implementation Under Test
OCL Object Constraint Language
PICS Protocol Implementation Conformance Statement
SUT System Under Test
TDL Test Description Language
TPLan Test Purpose Notation
4 Basic principles
4.1 Structured Test Objective Specification
The present document defines an extension for TDL enabling the specification of structured test objectives. Rather than
rely on external documents or informal text provided by the default test objective specification facilities of TDL, this
extension enables users to describe test objectives in a more structured and formalized manner which may enable
subsequent generation of test description skeletons and consistency checking against test descriptions realizing a given
test objective. In addition, the structured approach to test objective specification also enables syntactical and semantical
consistency checking of the test objectives themselves.
The abstract concepts and the concrete syntax are based on TPLan ETSI ES 202 553 [i.1] to a large extent, as they also
reflect concepts and practices already established at ETSI. The fundamental concept in the specification of a structured
test objectives is the event occurrence which describes the occurrence of an abstract event in a specific context,
comprising one or more involved entities, an event argument, as well as a time label and/or a time constraint.
ETSI
---------------------- Page: 7 ----------------------
8 ETSI ES 203 119-4 V1.4.1 (2020-08)
Events and entities referenced in an event occurrence shall be defined in advance as part of a domain description which
may then be reused across all structured test objective specifications in that domain. An entity is an abstract
representation of an object involved in an event occurrence that may be realized as a component instance or a gate
instance within a test description realizing the structured test objective.
An event argument may either refer to a data instance for data already defined with the facilities provided by TDL, or,
following a more light weight approach, describe data inline without the need to define all data types and instances in
advance. Pre-defined data and inline data may be integrated to a certain degree. Inline data may refer to pre-defined
data, but pre-defined data shall not refer to inline data.
Event occurrence specifications are organized in the different compartments of a structured test objective, including
initial conditions, expected behaviour, and final conditions. Multiple event occurrences are combined by means of an
'and' or 'or' operand indicating how subsequent event occurrences are related to each other (as a sequence or as
alternatives, respectively).
Structured test objectives may also include references to PICS which may be used as selection criteria for the concrete
realization of the test objectives. The PICS shall be defined in advance as part of the domain description. Multiple PICS
references within the same structured test objective are combined by means of an 'and' or 'or' operand indicating how
subsequent referenced PICS are related to each other.
4.2 Document Structure
The present document defines the structured test objective specification extension for TDL comprising:
• Meta-model extension describing additional concepts required for the specification of structured test objectives
(clause 5).
• Concrete syntax extension describing corresponding shapes for the representation of the additional concepts
(clause 6).
• An informative annex with examples in a textual concrete syntax (annex A).
• An informative annex with production rules for the example textual syntax (annex B).
4.3 Notational Conventions
The present document inherits the notational conventions defined in ETSI ES 203 119-1 [1] and ETSI
ES 203 119-2 [2].
The abstract syntax specification and the classifier descriptions follow the notational conventions defined in clause 4.5
of Abstract Syntax and Associated Semantics [1]. The concrete syntax notation specification follows the notational
conventions described in clause 4.5 of the Graphical Syntax [2].
4.4 Element Operations
The following operations shall be
...
Final draft ETSI ES 203 119-4 V1.4.1 (2020-06)
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Test Description Language (TDL);
Part 4: Structured Test Objective Specification (Extension)
---------------------- Page: 1 ----------------------
2 Final draft ETSI ES 203 119-4 V1.4.1 (2020-06)
Reference
RES/MTS-TDL4v141
Keywords
language, MBT, methodology, 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 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 Final draft ETSI ES 203 119-4 V1.4.1 (2020-06)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Basic principles . 7
4.1 Structured Test Objective Specification . 7
4.2 Document Structure . 8
4.3 Notational Conventions . 8
4.4 Element Operations . 8
4.5 Conformance . 9
5 Meta-Model Extensions . 9
5.1 Overview . 9
5.2 Foundation Abstract Syntax and Classifier Description . 9
5.2.1 Entity . 9
5.2.2 Event . 10
5.2.3 PICS . 10
5.3 Test Objective Abstract Syntax and Classifier Description . 11
5.3.1 StructuredTestObjective . 11
5.3.2 PICSReference . 12
5.3.3 InitialConditions . 12
5.3.4 ExpectedBehaviour . 13
5.3.5 FinalConditions . 13
5.4 Events Abstract Syntax and Classifier Description . 14
5.4.1 EventSequence . 14
5.4.2 RepeatedEventSequence . 15
5.4.3 EventOccurrence . 15
5.4.4 EventOccurrenceSpecification . 16
5.4.5 EntityReference . 17
5.4.6 EventReference . 17
5.5 Data Abstract Syntax and Classifier Description . 18
5.5.1 Value . 18
5.5.2 LiteralValue . 18
5.5.3 Content . 19
5.5.4 LiteralValueReference . 19
5.5.5 ContentReference . 20
5.5.6 DataReference . 20
5.6 Event Templates Abstract Syntax and Classifier Description . 21
5.6.1 EventSpecificationTemplate . 21
5.6.2 EventTemplateOccurrence . 22
5.6.3 EntityBinding . 22
6 Graphical Syntax Extensions. 23
6.1 Foundation . 23
6.1.1 Entity . 23
6.1.2 Event . 23
ETSI
---------------------- Page: 3 ----------------------
4 Final draft ETSI ES 203 119-4 V1.4.1 (2020-06)
6.1.3 PICS . 24
6.1.4 Comment . 24
6.2 Test Objective . 26
6.2.1 StructuredTestObjective . 26
6.3 Events . 28
6.3.1 EventSequence . 28
6.3.2 RepeatedEventSequence . 29
6.3.3 EventOccurrence . 29
6.3.4 EventOccurrenceSpecification . 30
6.3.5 EntityReference . 30
6.3.6 EventReference . 31
6.4 Data . 32
6.4.1 Value . 32
6.4.2 LiteralValue . 32
6.4.3 Content . 33
6.4.4 LiteralValueReference . 34
6.4.5 ContentReference . 34
6.4.6 DataReference . 35
6.4.7 StaticDataUse . 35
6.4.8 AnyValue . 36
6.4.9 AnyValueOrOmit . 36
6.4.10 OmitValue. 37
6.4.11 DataInstanceUse . 37
6.4.12 ArgumentSpecification . 37
6.5 Time . 38
6.5.1 TimeLabel . 38
6.5.2 TimeConstraint . 38
6.6 Event Templates . 39
6.6.1 EventSpecificationTemplate . 39
6.6.2 EventTemplateOccurrence . 40
6.6.3 EntityBinding . 41
7 Exchange Format Extensions . 41
Annex A (informative): Textual Syntax. 42
A.0 Overview . 42
A.1 A 3GPP Test Objective in Textual Syntax . 42
A.2 An IMS Test Objective in Textual Syntax . 43
Annex B (informative): Textual Syntax BNF Production Rules . 44
B.0 Overview . 44
B.1 Conventions . 44
B.2 Production Rules . 44
History . 49
ETSI
---------------------- Page: 4 ----------------------
5 Final draft ETSI ES 203 119-4 V1.4.1 (2020-06)
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 final draft 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 is part 4 of a multi-part deliverable. Full details of the entire series can be found in part 1 [1].
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.
Introduction
Test purposes play an essential role in test specification processes at ETSI. Currently, TDL treats test purposes, and test
objectives in general as informal text without any additional structural constraints. This extension package for TDL
refines and formalizes test objective specification within TDL by introducing relevant meta-model concepts and a
corresponding syntactical notation, both of which are related to TPLan ETSI ES 202 553 [i.1] and TPLan-like notations
already established at ETSI. This enables test purpose specification to enter the modelling world and paves the way for
improved tool support and better structured test objectives, as well as additional formal verification and validation
facilities down the road by integrating and unifying the means for the specification of test purposes and test
descriptions, while relying on the same underlying meta-model and benefiting from other related technologies built
around this meta-model.
The present document describes the relevant abstract syntax (meta-model) extensions as well as the corresponding
concrete syntactical notation.
NOTE: The use of underline (additional text) and strikethrough (deleted text) highlights the differences between
base document and extended documents.
ETSI
---------------------- Page: 5 ----------------------
6 Final draft ETSI ES 203 119-4 V1.4.1 (2020-06)
1 Scope
The present document specifies an extension of the Test Description Language (TDL) enabling the specification of
structured test objectives. The extension covers the necessary additional constructs in the abstract syntax, their
semantics, as well as the concrete graphical syntactic notation for the added constructs. In addition textual syntax
examples of the TDL Structured Test Objectives extensions as well as BNF rules for a textual syntax for TDL with the
Structured Test Objectives extensions are provided. The intended use of the present document is to serve both as a
foundation for TDL tools implementing support for the specification of structured test objectives, as well as a reference
for end users applying the standardized syntax for the specification of structured test objectives with TDL.
® ®
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
https://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] 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".
[2] ETSI ES 203 119-2 (V1.4.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 2: Graphical Syntax".
[3] ETSI ES 203 119-3 (V1.4.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 3: Exchange Format".
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 202 553 (V1.2.1): "Methods for Testing and Specification (MTS); TPLan: A notation for
expressing Test Purposes".
[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)".
ETSI
---------------------- Page: 6 ----------------------
7 Final draft ETSI ES 203 119-4 V1.4.1 (2020-06)
[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 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI ES 203 119-1 [1] and the following apply:
context: set of circumstances related to the occurrence of an event
entity: object that may be involved in the occurrence of an event as part of a specific context
entity type: alias for additional meta-information that may be used to describe one or more entities
event: observable phenomenon or state that may occur in a specific context
NOTE: Related to a term of the same name defined in ETSI ES 202 553 [i.1].
event occurrence: description of the occurrence of an event in a specific context
event type: alias for additional meta-information that may be used to describe one or more events
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
BNF Backus-Naur Form
EBNF Extended Backus-Naur Form
IMS IP Multimedia Subsystem
IUT Implementation Under Test
OCL Object Constraint Language
PICS Protocol Implementation Conformance Statement
SUT System Under Test
TDL Test Description Language
TPLan Test Purpose Notation
4 Basic principles
4.1 Structured Test Objective Specification
The present document defines an extension for TDL enabling the specification of structured test objectives. Rather than
rely on external documents or informal text provided by the default test objective specification facilities of TDL, this
extension enables users to describe test objectives in a more structured and formalized manner which may enable
subsequent generation of test description skeletons and consistency checking against test descriptions realizing a given
test objective. In addition, the structured approach to test objective specification also enables syntactical and semantical
consistency checking of the test objectives themselves.
The abstract concepts and the concrete syntax are based on TPLan ETSI ES 202 553 [i.1] to a large extent, as they also
reflect concepts and practices already established at ETSI. The fundamental concept in the specification of a structured
test objectives is the event occurrence which describes the occurrence of an abstract event in a specific context,
comprising one or more involved entities, an event argument, as well as a time label and/or a time constraint.
ETSI
---------------------- Page: 7 ----------------------
8 Final draft ETSI ES 203 119-4 V1.4.1 (2020-06)
Events and entities referenced in an event occurrence shall be defined in advance as part of a domain description which
may then be reused across all structured test objective specifications in that domain. An entity is an abstract
representation of an object involved in an event occurrence that may be realized as a component instance or a gate
instance within a test description realizing the structured test objective.
An event argument may either refer to a data instance for data already defined with the facilities provided by TDL, or,
following a more light weight approach, describe data inline without the need to define all data types and instances in
advance. Pre-defined data and inline data may be integrated to a certain degree. Inline data may refer to pre-defined
data, but pre-defined data shall not refer to inline data.
Event occurrence specifications are organized in the different compartments of a structured test objective, including
initial conditions, expected behaviour, and final conditions. Multiple event occurrences are combined by means of an
'and' or 'or' operand indicating how subsequent event occurrences are related to each other (as a sequence or as
alternatives, respectively).
Structured test objectives may also include references to PICS which may be used as selection criteria for the concrete
realization of the test objectives. The PICS shall be defined in advance as part of the domain description. Multiple PICS
references within the same structured test objective are combined by means of an 'and' or 'or' operand indicating how
subsequent referenced PICS are related to each other.
4.2 Document Structure
The present document defines the structured test objective specification extension for TDL comprising:
• Meta-model extension describing additional concepts required for the specification of structured test objectives
(clause 5).
• Concrete syntax extension describing corresponding shapes for the representation of the additional concepts
(clause 6).
• An informative annex with examples in a textual concrete syntax (annex A).
• An informative annex with production rules for the example textual syntax (annex B).
4.3 Notational Conventions
The present document inherits the notational conventions defined in ETSI ES 203 119-1 [1] and ETSI
ES 203 119-2 [2].
The abstract syntax specification and the classifier descriptions follow the notational conventions defined in clause 4.5
of Abstract Syntax and Associated Semantics
...
SLOVENSKI STANDARD
SIST ES 203 119-4 V1.4.1:2020
01-november-2020
Metode za preskušanje in specificiranje (MTS) - Jezik za opis preskusa (TDL) - 4.
del: Specifikacija cilja strukturiranega preskušanja (razširitev)
Methods for Testing and Specification (MTS) - The Test Description Language (TDL) -
Part 4: Structured Test Objective Specification (Extension)
Ta slovenski standard je istoveten z: ETSI ES 203 119-4 V1.4.1 (2020-08)
ICS:
35.060 Jeziki, ki se uporabljajo v Languages used in
informacijski tehniki in information technology
tehnologiji
SIST ES 203 119-4 V1.4.1:2020 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ES 203 119-4 V1.4.1:2020
---------------------- Page: 2 ----------------------
SIST ES 203 119-4 V1.4.1:2020
ETSI ES 203 119-4 V1.4.1 (2020-08)
ETSI STANDARD
Methods for Testing and Specification (MTS);
The Test Description Language (TDL);
Part 4: Structured Test Objective Specification (Extension)
---------------------- Page: 3 ----------------------
SIST ES 203 119-4 V1.4.1:2020
2 ETSI ES 203 119-4 V1.4.1 (2020-08)
Reference
RES/MTS-TDL4v141
Keywords
language, MBT, methodology, 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 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: 4 ----------------------
SIST ES 203 119-4 V1.4.1:2020
3 ETSI ES 203 119-4 V1.4.1 (2020-08)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Basic principles . 7
4.1 Structured Test Objective Specification . 7
4.2 Document Structure . 8
4.3 Notational Conventions . 8
4.4 Element Operations . 8
4.5 Conformance . 9
5 Meta-Model Extensions . 9
5.1 Overview . 9
5.2 Foundation Abstract Syntax and Classifier Description . 9
5.2.1 Entity . 9
5.2.2 Event . 10
5.2.3 PICS . 10
5.3 Test Objective Abstract Syntax and Classifier Description . 11
5.3.1 StructuredTestObjective . 11
5.3.2 PICSReference . 12
5.3.3 InitialConditions . 12
5.3.4 ExpectedBehaviour . 13
5.3.5 FinalConditions . 13
5.4 Events Abstract Syntax and Classifier Description . 14
5.4.1 EventSequence . 14
5.4.2 RepeatedEventSequence . 15
5.4.3 EventOccurrence . 15
5.4.4 EventOccurrenceSpecification . 16
5.4.5 EntityReference . 17
5.4.6 EventReference . 17
5.5 Data Abstract Syntax and Classifier Description . 18
5.5.1 Value . 18
5.5.2 LiteralValue . 18
5.5.3 Content . 19
5.5.4 LiteralValueReference . 19
5.5.5 ContentReference . 20
5.5.6 DataReference . 20
5.6 Event Templates Abstract Syntax and Classifier Description . 21
5.6.1 EventSpecificationTemplate . 21
5.6.2 EventTemplateOccurrence . 22
5.6.3 EntityBinding . 22
6 Graphical Syntax Extensions. 23
6.1 Foundation . 23
6.1.1 Entity . 23
6.1.2 Event . 23
ETSI
---------------------- Page: 5 ----------------------
SIST ES 203 119-4 V1.4.1:2020
4 ETSI ES 203 119-4 V1.4.1 (2020-08)
6.1.3 PICS . 24
6.1.4 Comment . 24
6.2 Test Objective . 26
6.2.1 StructuredTestObjective . 26
6.3 Events . 28
6.3.1 EventSequence . 28
6.3.2 RepeatedEventSequence . 29
6.3.3 EventOccurrence . 29
6.3.4 EventOccurrenceSpecification . 30
6.3.5 EntityReference . 30
6.3.6 EventReference . 31
6.4 Data . 32
6.4.1 Value . 32
6.4.2 LiteralValue . 32
6.4.3 Content . 33
6.4.4 LiteralValueReference . 34
6.4.5 ContentReference . 34
6.4.6 DataReference . 35
6.4.7 StaticDataUse . 35
6.4.8 AnyValue . 36
6.4.9 AnyValueOrOmit . 36
6.4.10 OmitValue. 37
6.4.11 DataInstanceUse . 37
6.4.12 ArgumentSpecification . 37
6.5 Time . 38
6.5.1 TimeLabel . 38
6.5.2 TimeConstraint . 38
6.6 Event Templates . 39
6.6.1 EventSpecificationTemplate . 39
6.6.2 EventTemplateOccurrence . 40
6.6.3 EntityBinding . 41
7 Exchange Format Extensions . 41
Annex A (informative): Textual Syntax. 42
A.0 Overview . 42
A.1 A 3GPP Test Objective in Textual Syntax . 42
A.2 An IMS Test Objective in Textual Syntax . 43
Annex B (informative): Textual Syntax BNF Production Rules . 44
B.0 Overview . 44
B.1 Conventions . 44
B.2 Production Rules . 44
History . 49
ETSI
---------------------- Page: 6 ----------------------
SIST ES 203 119-4 V1.4.1:2020
5 ETSI ES 203 119-4 V1.4.1 (2020-08)
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 4 of a multi-part deliverable. Full details of the entire series can be found in part 1 [1].
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.
Introduction
Test purposes play an essential role in test specification processes at ETSI. Currently, TDL treats test purposes, and test
objectives in general as informal text without any additional structural constraints. This extension package for TDL
refines and formalizes test objective specification within TDL by introducing relevant meta-model concepts and a
corresponding syntactical notation, both of which are related to TPLan ETSI ES 202 553 [i.1] and TPLan-like notations
already established at ETSI. This enables test purpose specification to enter the modelling world and paves the way for
improved tool support and better structured test objectives, as well as additional formal verification and validation
facilities down the road by integrating and unifying the means for the specification of test purposes and test
descriptions, while relying on the same underlying meta-model and benefiting from other related technologies built
around this meta-model.
The present document describes the relevant abstract syntax (meta-model) extensions as well as the corresponding
concrete syntactical notation.
NOTE: The use of underline (additional text) and strikethrough (deleted text) highlights the differences between
base document and extended documents.
ETSI
---------------------- Page: 7 ----------------------
SIST ES 203 119-4 V1.4.1:2020
6 ETSI ES 203 119-4 V1.4.1 (2020-08)
1 Scope
The present document specifies an extension of the Test Description Language (TDL) enabling the specification of
structured test objectives. The extension covers the necessary additional constructs in the abstract syntax, their
semantics, as well as the concrete graphical syntactic notation for the added constructs. In addition textual syntax
examples of the TDL Structured Test Objectives extensions as well as BNF rules for a textual syntax for TDL with the
Structured Test Objectives extensions are provided. The intended use of the present document is to serve both as a
foundation for TDL tools implementing support for the specification of structured test objectives, as well as a reference
for end users applying the standardized syntax for the specification of structured test objectives with TDL.
® ®
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
https://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] 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".
[2] ETSI ES 203 119-2 (V1.4.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 2: Graphical Syntax".
[3] ETSI ES 203 119-3 (V1.4.1): "Methods for Testing and Specification (MTS); The Test
Description Language (TDL); Part 3: Exchange Format".
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 202 553 (V1.2.1): "Methods for Testing and Specification (MTS); TPLan: A notation for
expressing Test Purposes".
[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)".
ETSI
---------------------- Page: 8 ----------------------
SIST ES 203 119-4 V1.4.1:2020
7 ETSI ES 203 119-4 V1.4.1 (2020-08)
[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 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI ES 203 119-1 [1] and the following apply:
context: set of circumstances related to the occurrence of an event
entity: object that may be involved in the occurrence of an event as part of a specific context
entity type: alias for additional meta-information that may be used to describe one or more entities
event: observable phenomenon or state that may occur in a specific context
NOTE: Related to a term of the same name defined in ETSI ES 202 553 [i.1].
event occurrence: description of the occurrence of an event in a specific context
event type: alias for additional meta-information that may be used to describe one or more events
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
BNF Backus-Naur Form
EBNF Extended Backus-Naur Form
IMS IP Multimedia Subsystem
IUT Implementation Under Test
OCL Object Constraint Language
PICS Protocol Implementation Conformance Statement
SUT System Under Test
TDL Test Description Language
TPLan Test Purpose Notation
4 Basic principles
4.1 Structured Test Objective Specification
The present document defines an extension for TDL enabling the specification of structured test objectives. Rather than
rely on external documents or informal text provided by the default test objective specification facilities of TDL, this
extension enables users to describe test objectives in a more structured and formalized manner which may enable
subsequent generation of test description skeletons and consistency checking against test descriptions realizing a given
test objective. In addition, the structured approach to test objective specification also enables syntactical and semantical
consistency checking of the test objectives themselves.
The abstract concepts and the concrete syntax are based on TPLan ETSI ES 202 553 [i.1] to a large extent, as they also
reflect concepts and practices already established at ETSI. The fundamental concept in the specification of a structured
test objectives is the event occurrence which describes the occurrence of an abstract event in a specific context,
comprising one or more involved entities, an event argument, as well as a time label and/or a time constraint.
ETSI
---------------------- Page: 9 ----------------------
SIST ES 203 119-4 V1.4.1:2020
8 ETSI ES 203 119-4 V1.4.1 (2020-08)
Events and entities referenced in an event occurrence shall be defined in advance as part of a domain description which
may then be reused across all structured test objective specifications in that domain. An entity is an abstract
representation of an object involved in an event occurrence that may be realized as a component instance or a gate
instance within a test description realizing the structured test objective.
An event argument may either refer to a data instance for data already defined with the facilities provided by TDL, or,
following a more light weight approach, describe data inline without the need to define all data types and instances in
advance. Pre-defined data and inline data may be integrated to a certain degree. Inline data may refer to pre-defined
data, but pre-defined data shall not refer to inline data.
Event occurrence specifications are organized in the different compartments of a structured test objective, including
initial conditions, expected behaviour, and final conditions. Multiple event occurrences are combined by means of an
'and' or 'or' operand indicating how subsequent event occurrences are related to each other (as a sequence or as
alternatives, respectively).
Structured test objectives may also include references to PICS which may be used as selection criteria for the concrete
realization of the test objectives. The PICS shall be defined in advance as part of the domain description. Multiple PICS
references within the same structured test objective are combined by means of an 'and' or 'or' operand indicating how
subsequent refere
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.