Multi-access Edge Computing (MEC); API Conformance Test Specification; Part 3: Abstract Test Suite (ATS)

RGS/MEC-DEC32-3v321ApiTest

General Information

Status
Not Published
Current Stage
12 - Citation in the OJ (auto-insert)
Due Date
15-Nov-2024
Completion Date
06-Nov-2024
Ref Project

Buy Standard

Standard
ETSI GS MEC-DEC 032-3 V3.2.1 (2024-11) - Multi-access Edge Computing (MEC); API Conformance Test Specification; Part 3: Abstract Test Suite (ATS)
English language
15 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


GROUP SPECIFICATION
Multi-access Edge Computing (MEC);
API Conformance Test Specification;
Part 3: Abstract Test Suite (ATS)
Disclaimer
The present document has been produced and approved by the Multi-access Edge Computing (MEC) ETSI Industry
Specification Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

2 ETSI GS MEC-DEC 032-3 V3.2.1 (2024-11)

Reference
RGS/MEC-DEC32-3v321ApiTest
Keywords
API, conformance, MEC, testing

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 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
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 on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2024.
All rights reserved.
ETSI
3 ETSI GS MEC-DEC 032-3 V3.2.1 (2024-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, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 ATS conventions . 7
4.1 Introduction . 7
4.2 Testing conventions . 7
4.2.1 TTCN-3 Testing conventions . 7
4.2.1.1 Testing states . 7
4.2.1.1.1 Initial state . 7
4.2.1.1.2 Final state . 8
4.2.1.2 Message types - JSON definitions . 8
4.2.2 Robot Testing conventions . 8
4.3 Naming conventions . 8
4.3.1 TTCN-3 Naming conventions. 8
4.3.1.1 Introduction . 8
4.3.1.2 General guidelines . 8
4.3.2 Usage of Log statements . 9
4.3.3 Robot Naming conventions . 10
Annex A (normative): TTCN-3 Abstract Test Suite (ATS) . 11
Annex B (normative): Robot Framework Abstract Test Suite (ATS) . 12
Annex C (informative): Test System Execution . 13
C.1 Information on execution of the TTCN-3 test suite . 13
C.2 Information on execution of the Robot Framework test suite . 13
Annex D (informative): Change history . 14
History . 15

ETSI
4 ETSI GS MEC-DEC 032-3 V3.2.1 (2024-11)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G logo 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.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Multi-access Edge
Computing (MEC).
The present document is part 3 of a multi-part deliverable. Full details of the entire series can be found in part 1 [i.7].
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
5 ETSI GS MEC-DEC 032-3 V3.2.1 (2024-11)
1 Scope
Based on the testing methodology guidelines and framework specified in ETSI GR MEC-DEC 025 [i.1], the present
document specifies part 3 of a multi-part deliverable on conformance test specification. Part 3 (the present document)
provides the Abstract Test Suites (ATS) in TTCN-3 [i.3] and the Robot Framework [i.5] for:
• Application Package Management and Application Lifecycle Management as specified in ETSI
GS MEC 010-2 [2];
• the MEC Application Enablement API specified in ETSI GS MEC 011 [3]; and
• the MEC service APIs.
The MEC service APIs in scope of the present document are specified in:
• ETSI GS MEC 012 [4];
• ETSI GS MEC 013 [5];
• ETSI GS MEC 014 [6];
• ETSI GS MEC 015 [7];
• ETSI GS MEC 016 [8];
• ETSI GS MEC 021 [9];
• ETSI GS MEC 028 [10];
• ETSI GS MEC 029 [11];
• ETSI GS MEC 030 [12].
• ETSI GS MEC 033 [14]; and
• ETSI GS MEC 040 [15].
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] Void.
[2] ETSI GS MEC 010-2 (V3.1.1): "Multi-access Edge Computing (MEC); MEC Management;
Part 2: Application lifecycle, rules and requirements management".
[3] ETSI GS MEC 011 (V3.2.1): "Multi-access Edge Computing (MEC); Edge Platform Application
Enablement".
ETSI
6 ETSI GS MEC-DEC 032-3 V3.2.1 (2024-11)
[4] ETSI GS MEC 012 (V2.2.1): "Multi-access Edge Computing (MEC); Radio Network Information
API".
[5] ETSI GS MEC 013 (V3.1.1): "Multi-access Edge Computing (MEC); Location API".
[6] ETSI GS MEC 014 (V3.1.1): "Multi-access Edge Computing (MEC); UE Identity API".
[7] ETSI GS MEC 015 (V2.2.1): "Multi-access Edge Computing (MEC); Traffic Management APIs".
[8] ETSI GS MEC 016 (V2.2.1): "Multi-access Edge Computing (MEC); Device application
interface".
[9] ETSI GS MEC 021 (V3.1.1): "Multi-access Edge Computing (MEC); Application Mobility
Service API ".
[10] ETSI GS MEC 028 (V2.3.1): "Multi-access Edge Computing (MEC); WLAN Access Information
API".
[11] ETSI GS MEC 029 (V2.2.1): "Multi-access Edge Computing (MEC); Fixed Access Information
API".
[12] ETSI GS MEC 030 (V3.1.1): "Multi-access Edge Computing (MEC); V2X Information Services
API".
[13] ETSI GS MEC-DEC 032-2 (V3.2.1): "Multi-access Edge Computing (MEC); API Conformance
Test Specification; Part 2: Test Purposes (TP)".
[14] ETSI GS MEC 033 (V3.1.1): "Multi-access Edge Computing (MEC); IoT API".
[15] ETSI GS MEC 040 (V3.1.1): "Multi-access Edge Computing (MEC); Federation enablement
APIs".
2.2 Informative references
References are either specific (identified by date of publicatio
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.