|
TECHNICAL SPECIFICATION
Methods for Testing and Specification (MTS);
TTCN-3 Conformance Test Suite;
Part 3: Abstract Test Suite (ATS) and
Implementation eXtra Information for Testing (IXIT)
---------------------- Page: 1 ----------------------
2 ETSI TS 102 950-3 V1.7.1 (2018-11)
Reference
RTS/MTS-102950-3ed171T3Conf
Keywords
ATS, conformance, testing, TTCN
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:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
If you find errors in the present document, please send your comment to one of the following services:
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 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 TS 102 950-3 V1.7.1 (2018-11)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 6
3 Definition of terms and abbreviations . 6
3.1 Terms . 6
3.2 Abbreviations . 7
4 Abstract Test Method (ATM) . 7
5 The ATS development process . . 8
5.1 Requirements and test purposes . 8
5.2 ATS structure . 8
5.2.1 Test case grouping . 8
5.2.2 Test case identifiers . 9
5.3 ATS specification framework . 10
5.3.1 Use of TTCN-3 . 10
5.3.1.1 General . 10
5.3.1.2 TTCN-3 naming conventions . 10
5.3.1.3 TTCN-3 comment tags . 11
5.4 ATS archive . 14
6 PIXIT conformance . 14
7 ATS conformance . 14
Annex A (normative): Abstract Test Suite (ATS) . 15
A.1 The ATS in TTCN-3 core (text) format . 15
Annex B (normative): Partial IXIT pro forma . 16
B.0 The right to copy . 16
B.1 Introduction . 16
History . 17
ETSI
---------------------- Page: 3 ----------------------
4 ETSI TS 102 950-3 V1.7.1 (2018-11)
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 Specification (TS) has been produced by ETSI Technical Committee Methods for Testing and
Specification (MTS).
The present document is part 3 of a multi-part deliverable covering a TTCN-3 conformance test suite, as identified
below:
Part 1: "Implementation Conformance Statement (ICS)";
Part 2: "Test Suite Structure and Test Purposes (TSS & TP)";
Part 3: "Abstract Test Suite (ATS) and Implementation eXtra Information for Testing (IXIT)".
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
---------------------- Page: 4 ----------------------
5 ETSI TS 102 950-3 V1.7.1 (2018-11)
1 Scope
The present document specifies the Abstract Test Suite (ATS) for the TTCN-3 conformance test suite, as defined in
ETSI ES 201 873-1 [1] in compliance with the relevant guidance given in the pro forma for TTCN-3 reference test suite
ETSI TS 102 950-2 [8].
The objective of the present document is to provide a basis for conformance tests for TTCN-3 tools giving a high
probability of standard conformance with respect to TTCN-3 tools from different vendors. In the present document only
the core language features, specified in ETSI ES 201 873-1 [1] have been considered but not the tool implementation
(see [i.1] and [i.2]), language mapping (see [i.3], [i.4] and [i.5]) and language extension (see e.g. [i.6], [i.7] and [i.8])
aspects. The test notation used in the ATS attached in a zipped file is in TTCN-3 and it is part of the present document.
Annex A provides the Tree and Tabular Combined Notation (TTCN-3) part of the ATS.
Annex B provides the Partial Implementation Extra Information for Testing (PIXIT) pro forma of the ATS.
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 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[2] ETSI ES 201 873-10: "Methods for Testing and Specification (MTS); The Testing and Test
Control Notation version 3; Part 10: TTCN-3 Documentation Comment Specification".
[3] ETSI TS 102 351: "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT);
IPv6 Testing: Methodology and Framework".
[4] ISO/IEC 9646-1: "Information Technology - Open Systems Interconnection - Conformance
Testing Methodology and Framework - Part 1: General concepts".
[5] ISO/IEC 9646-4: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 4: Test realization".
[6] ISO/IEC 9646-5: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 5: Requirements on test laboratories and clients for the
conformance assessment process".
[7] ISO/IEC 9646-7: "Conformance testing methodology and framework - Part 7: Implementation
Conformance Statement".
[8] ETSI TS 102 950-2: "Methods for Testing and Specification (MTS); TTCN-3 Conformance Test
Suite; Part 2: Test Suite Structure and Test Purposes (TSS & TP)".
ETSI
---------------------- Page: 5 ----------------------
6 ETSI TS 102 950-3 V1.7.1 (2018-11)
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-5: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)".
[i.2] ETSI ES 201 873-6: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 6: TTCN-3 Control Interface (TCI)".
[i.3] ETSI ES 201 873-7: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 7: Using ASN.1 with TTCN-3".
[i.4] ETSI ES 201 873-8: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 8: The IDL to TTCN-3 Mapping".
[i.5] ETSI ES 201 873-9: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 9: Using XML schema with TTCN-3".
[i.6] ETSI ES 202 781: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Configuration and Deployment Support".
[i.7] ETSI ES 202 784: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Advanced Parameterization".
[i.8] ETSI ES 202 785: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; TTCN-3 Language Extensions: Behaviour Types".
3 Definition of terms and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ISO/IEC 9646-1 [4], ISO/IEC 9646-7 [7],
ETSI ES 201 873-1 [1](TTCN-3) and the following apply:
Abstract Test Method (ATM): description of how an IUT is to be tested, given at an appropriate level of abstraction to
make the description independent of any particular realization of a Means of Testing, but with enough detail to enable
abstract test cases to be specified for this method
Abstract Test Suite (ATS): test suite composed of abstract test cases
Implementation Conformance Statement (ICS): statement made by the supplier of an implementation claimed to
conform to a given specification, stating which capabilities have been implemented
ICS pro forma: document, in the form of a questionnaire, which when completed for an implementation or system
becomes an ICS
Implementation eXtra Information for Testing (IXIT): statement made by a supplier or implementor of an IUT
which contains or references all of the information related to the IUT and its testing environment, which will enable the
test laboratory to run an appropriate test suite against the IUT
Implementation Under Test (IUT): implementation of one or more OSI protocols in an adjacent user/provider
relationship, being part of a real open system which is to be studied by testing
ETSI
---------------------- Page: 6 ----------------------
7 ETSI TS 102 950-3 V1.7.1 (2018-11)
IXIT pro forma: document, in the form of a questionnaire, which when completed for the IUT becomes the IXIT
Means Of Testing (MOT): combination of equipment and procedures that can perform the derivation, selection,
parameterization and execution of test cases, in conformance with a reference standardized ATS and can produce a
conformance log
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
BNF Backus Naur Form
ETS Executable Test Suite
ICS Implementation Conformance Statement
IUT Implementation under Test
IXIT Implementation eXtra Information for Testing
MOT Means Of Testing
SUT System Under Test
TC Test Case
TCI TTCN-3 Control Interface
TP Test Purpose
TRI TTCN-3 Runtime Interface
TS Test System
TSS & TP Test Suite Structure and Test Purposes
TSS Test Suite Structure
TTCN-3 Testing and Test Control Notation edition 3
4 Abstract Test Method (ATM)
This clause describes the ATM used to test the conformance of TTCN-3 tool implementations as described in part 1 of
the TTCN-3 core language standard ETSI ES 201 873-1 [1]. In the ATM, the work is performed on two levels:
• The TTCN-3 tool level. In TTCN-3 conformance tests, it is the TTCN-3 tool which is under test, i.e. the IUT.
However, unlike in protocol conformance testing, it is not standardized how test inputs, i.e. TTCN-3 modules,
are provided. Neither are there any standardized interfaces to monitor the reaction of the TTCN-3 tool to the
test input. Outputs can only be observed indirectly by monitoring tool outputs such as tool specific command
line information, graphical user interfaces, or test execution logs. The tool output is processed further in the
tool output evaluation level in order to derive the tool conformance verdicts.
• The TTCN-3 tool output evaluation level. Here, the output of a TTCN-3 tool is indirectly observed,
e.g. rejection of TTCN-3 code due to a compile-time error in a command line notification, logging of one or
multiple test verdicts in a tool specific window or an execution trace. The observation is evaluated to assess
the tool conformance as a result of stimulating the tool with the TTCN-3 modules. Compliance or support of
the logging interface specified as part of the TTCN-3 Control Interface standard (TCI) is not required.
NOTE: The loading of the TTCN-3 modules and presentation of the output by the TTCN-3 tools is beyond the
scope of the present document.
The ATS document contains the test inputs, i.e. TTCN-3 modules, for TTCN-3 tools do not automate the execution of
TTCN-3 tool conformance tests. TTCN-3 tool conformance test decisions shall be made on the basis of expected
outputs as specified in the test purposes provided in the documentation and as part of the documentation of TTCN-3
tests in the ATS. Three different tool output classifications for TTCN-3 inputs exist:
• Rejection as invalid, i.e. the TTCN-3 input is declared syntactically or semantically incorrect by the tool. This
can either happen at compile-time or at runtime.
• Rejection to execute, i.e. an ETS is produced from the test input, but an execution does not take place.
• Execution with results, i.e. the compiled or interpreted TTCN-3 code is executed and different kinds of outputs
are produced that can be subject of an evaluation, for example, a logged TTCN-3 test verdict in a test
ETSI
---------------------- Page: 7 ----------------------
8 ETSI TS 102 950-3 V1.7.1 (2018-11)
execution trace (none, pass, fail, inconc) in a file or the console output. The respective tool outputs has to
specify the expected execution results in order to be able to evaluate whether the conformance test is
successful.
A TTCN-3 tool conformance test can attempt to trigger every kind of such outputs in a controlled way, i.e. a test input
that is rejected as invalid does not imply a failing conformance test verdict, but instead results in a pass verdict for the
conformance test if the test is designed to trigger the rejection. More generally: a TTCN-3 tool conformance test passes
if the tool output corresponds to the expected output. The range of expected outputs is described by the tool output
classification above.
For a detailed description on how test verdict and test purposes are encoded and how they shall be evaluated with the
ATS of annex A, please refer to clause 5.3.1.3 and the descriptions for the document tags @verdict and @purpose.
5 The ATS development process
5.1 Requirements and test purposes
For each test purpose there is a table defined in clause A.2 of ETSI TS 102 950-2 [8]. The requirements applicable to
this TP are given by a reference to ETSI ES 201 873-1 [1]. There are no explicit formulations of requirements.
5.2 ATS structure
5.2.1 Test case grouping
The ATS structure defined in table 1 is based on the structuring of Test Purposes in clause A.2 of ETSI
TS 102 950-2[8]. The group names in columns 1 to 3 of table 1 are those assigned in the ATS; they are based on the
names provided in clause A.2 of ETSI TS 102 950-2 [8], but use the naming conventions defined for the ATS (see
clause 5.3.1.2). The test case identifier naming scheme differentiates between positive and negative tests as well as
syntactical and semantics tests:
• Syntactical tests are tests that refer to annex A of ETSI ES 201 873-1 [1]. They include pure syntactical tests
and tests regarding the static semantics to the degree of detail that annex A provides.
• Semantic tests are tests that refer to the checking of properties regarding the static and dynamic semantics of
TTCN-3 according to the specific clauses of ETSI ES 201 873-1 [1].
• Po
...