ETSI GR CIM 015 V3.1.1 (2025-07)

Context Information Management (CIM); NGSI-LD Testing Environment Validation

RGR/CIM-0015v311

General Information

• Status: Not Published
• Technical Committee: CIM - cross-cutting Context Information Management
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 16-Jun-2025
• Completion Date: 30-Jul-2025

Standards Content (Sample)

GROUP REPORT
Context Information Management (CIM);
NGSI-LD Testing Environment Validation
Disclaimer
The present document has been produced and approved by the cross-cutting Context Information Management (CIM) 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 GR CIM 015 V3.1.1 (2025-07)

Reference
RGR/CIM-0015v311
Keywords
API, IoT, NGSI-LD, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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 2025.
All rights reserved.
ETSI
3 ETSI GR CIM 015 V3.1.1 (2025-07)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Executive summary . 5
Introduction . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Tests Execution Options . 8
4.1 Introduction . 8
4.2 Executing all tests . 8
4.3 Executing tests subsets from a folder . 8
4.4 Executing tests from a single Test Case . 8
4.5 Results output . 8
4.6 Overriding base URL . 9
4.7 Executing tests by specific tag . 9
4.8 Rerun failed tests . 9
4.9 Generate log file of failed tests . 9
4.10 Management of Test Cases . 9
4.10.0 Foreword . 9
4.10.1 Installation . 10
4.10.2 Execution . 10
5 Permutations . 11
5.1 Introduction . 11
5.2 Data driven approach . 11
5.3 Keyword approach . 12
6 Tags . 12
6.1 Introduction . 12
6.2 Resource and request tags . 12
6.3 Section reference tags . 15
6.4 Configuration reference tags . 15
6.5 Distributed Operations reference tags . 15
7 Test Suite Maintenance . 15
8 Test Suite Usability . 15
9 Future work . 16
9.1 Introduction . 16
9.2 Test Suite usability . 16
9.2.1 Identification of failed checks when comparing results . 16
9.3 Test Suite coverage of the specification . 16
9.4 Test Suite improvements . 17
9.4.1 Severity of the errors. 17
9.4.2 Optional and mandatory requests . 17
9.5 Test Suite maintenance . 17
Annex A: NGSI-LD Implementations . 19
ETSI
4 ETSI GR CIM 015 V3.1.1 (2025-07)
Annex B: Change history . 20
History . 21

ETSI
5 ETSI GR CIM 015 V3.1.1 (2025-07)
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 Report (GR) has been produced by ETSI Industry Specification Group (ISG) cross-cutting Context
Information Management (CIM).
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.
Executive summary
The present document presents the results of the validation of the NGSI-LD Test Suite and its test environment. Besides
the testing environment validation, it also provides experts who are implementing the NGSI-LD API specification a
description of how to efficiently run the Test Suite and how it can be extended to add more permutations in the Test
Cases. The present document concludes by listing the envisioned future work on the Test Suite to extend it and improve
it as well as to maintain it for future versions of the NGSI-LD API.
ETSI
6 ETSI GR CIM 015 V3.1.1 (2025-07)
Introduction
The ISG CIM group has defined an API for exchange of information contextualized in time, space and relation to other
information using a property graph model with the intent that the associated protocol (called NGSI-LD) becomes the
"glue" between all kinds of applications and databases associated with services for Smart Cities, Smart Agriculture,
Smart Manufacturing, etc.
To be successful, the NGSI-LD API specification needs to be well understood and well implemented. The community
of users will not be solely highly professional engineers employed by big companies but will include many small teams
and SMEs and even hobbyists. Therefore, it is essential that the developers have access to not only the standard but also
a test specification and a testing environment to check that their work is (and remains) conform to the ETSI NGSI LD
specification.
The developers will usually write integration tests to validate the behaviour of their NGSI-LD implementation, but it is
important to assert compliance to the specification based on a test suite agreed by the group creating the API
specification, i.e. ETSI ISG CIM. Therefore, it is very important to create a set of ETSI-approved test cases.
What is more, the existence of such a test suite will likely help to increase the adoption of the NGSI-LD specification
by giving developers a ready to use and extensive set of sample tests.

ETSI
7 ETSI GR CIM 015 V3.1.1 (2025-07)
1 Scope
The present document presents the experience of running the Test Suite against a set of open-source context brokers
implementing the NGSI-LD specifications.
It also gives some guidelines on how to use the Test Suite and how to extend it for simple use-cases like adding new
permutations in a Test Case.
Finally, it presents some ideas for later improvements of the Test Suite.
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 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 GS CIM 009 (V1.5.1): "Context Information Management (CIM); NGSI-LD API".
[i.2] Void.
[i.3] ETSI GS CIM 027 (V1.1.1): "Context Information Management (CIM); NGSI-LD Testing
Framework: Test Purposes Description Language (TPDL)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
Void.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
API Application Programming Interface
HTML HyperText Markup Language
HTTP HyperText Transfer Protocol
NGSI-LD Next Generation Service Interfaces Linked Data
PICS Profile Implementation Conformance Statement
ETSI
8 ETSI GR CIM 015 V3.1.1 (2025-07)
SME Small Medium Enterprise
TC Test Case
TTF Testing Task Force
XML eXtensible Markup Language
4 Tests Execution Options
4.1 Introduction
All the NGSI-LD Test Cases can be executed by launching one single command, but it is also possible to run subsets of
those tests.
By specifying a folder when launching the Test Suite, all the tests inside that folder and subsequent subfolders will be
executed. Folder selection is an easy way of selecting different tests groups. That also makes the folder structure an
important asset on how to run tests subsets.
The generic command to execute tests is:
robot [options] robot_files
Where the arguments are:
• options: options that can be included in the command;
• robot_files: path to the file or folder where the tests files are stored.
4.2 Executing all tests
The easiest way to run all the tests is to select a folder that has all the tests inside of it or inside of all its subfolders. In
that case, the folder path "./TP/NGSI-LD" is a good choice.
The matching command is:
robot ./TP/NGSI-LD
4.3 Executing tests subsets from a folder
When a folder is selected, it will only run the tests inside of it or inside of all its subfolders. For instance, to run all the
tests related to the creation of an entity, the command is:
robot ./TP/NGSI-LD/ContextInformation/Provision/Entities/CreateEntity
4.4 Executing tests from a single Test Case
To run all the tests in a specific Test Case file, e.g. 001_01.robot, the command is:
robot ./TP/NGSI-
LD/ContextInformation/Provision/Entities/CreateEntity/001_01.robot
4.5 Results output
An important feature is to output results when running tests. The results are comprised of three different files:
• log.html: logs information from the executed tests in HTML format
• output.xml: logs information from the executed tests in XML format
ETSI
9 ETSI GR CIM 015 V3.1.1 (2025-07)
• report.html: shows information about the success/failures of the executed tests
In case the ErrorListener has been activated (see clause 4.8 for a description of it
...