Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • specifications/ts/ts-0019
  • reinaortega/ts-0019
2 results
Show changes
Commits on Source (3)
Hide whitespace changes
Inline Side-by-side
TS-0019-Abstract_Test_Suite_&_implementation_eXtra_Information_for_Test.md
View file @ 059f901d
......@@ -7,13 +7,29 @@
|**oneM2M**<br />**Technical** **Specification** |**oneM2M**<br />**Technical** **Specification** |
|-|-|
|Document Number |oneM2M-TS-0019-V-2.9.1 |
|Document Name: |Abstract Test Suite and Implementation eXtra Information for Test |
|Date: |2024 February 15 |
|Abstract: |Abstract Test Suite and Implementation eXtra Information for Test consists of :<br />- Definition of the Abstract Protocol Tester (APT)<br />- Definition of TTCN-3 test architecture<br />- Development of TTCN-3 test suite, e.g. naming conventions, code documentation, test case structure.<br />- IXIT proforma;<br /> |
|Template Version:23 February 2015 (Do not modify) |Template Version:23 February 2015 (Do not modify) |
+----------------------------------------------------------------+
|**oneM2M** **Technical** **Specification** |
+:================+:=============================================+
|Document Number |oneM2M-TS-0019-V-2.9.2 |
+-----------------+----------------------------------------------+
|Document Name: |Abstract Test Suite and Implementation |
| |eXtra Information for Test |
+-----------------+----------------------------------------------+
|Date: |2025 February 13 |
+-----------------+----------------------------------------------+
|Abstract: |Abstract Test Suite and Implementation eXtra |
| |Information for Test consists of: |
| | |
| |- Definition of the Abstract Protocol Tester |
| | (APT) |
| |- Definition of TTCN-3 test architecture |
| |- Development of TTCN-3 test suite, e.g. |
| | naming conventions, code documentation, test|
| | case structure. |
| |- IXIT proforma; |
+-----------------+----------------------------------------------+
|Template Version:23 February 2015 (Do not modify) |
+----------------------------------------------------------------+
......@@ -26,8 +42,7 @@
This Specification is provided for future development work within oneM2M only. The Partners accept no liability for any use of this Specification.
<br />This Specification is provided for future development work within oneM2M only. The Partners accept no liability for any use of this Specification.
The present document has not been subject to any approval process by the oneM2M Partners Type 1. Published oneM2M specifications and reports for implementation should be obtained via the oneM2M Partners' Publications Offices.
......@@ -43,7 +58,7 @@ More information about oneM2M may be found at: http//www.oneM2M.org
Copyright Notification
(c) 2019, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).
(c) 2025, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).
All rights reserved.
......@@ -59,66 +74,14 @@ NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURA
# Contents
[Contents](#contents)
[1 Scope](#1-scope)
[2 References](#2-references)
&nbsp;&nbsp;&nbsp;&nbsp;[2.1 Normative references](#21-normative-references)
&nbsp;&nbsp;&nbsp;&nbsp;[2.2 Informative references](#22-informative-references)
[3 Definition of terms, symbols and abbreviations](#3-definition-of-terms-symbols-and-abbreviations)
&nbsp;&nbsp;&nbsp;&nbsp;[3.1 Terms](#31-terms)
&nbsp;&nbsp;&nbsp;&nbsp;[3.2 Symbols](#32-symbols)
&nbsp;&nbsp;&nbsp;&nbsp;[3.2 Abbreviations](#32-abbreviations)
[4 Conventions](#4-conventions)
[5 Abstract Test Method (ATM)](#5-abstract-test-method-atm)
&nbsp;&nbsp;&nbsp;&nbsp;[5.1 Abstract protocol tester](#51-abstract-protocol-tester)
&nbsp;&nbsp;&nbsp;&nbsp;[5.2 Test Configuration](#52-test-configuration)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.2.1 AE Test Configuration](#521-ae-test-configuration)
&nbsp;&nbsp;&nbsp;&nbsp;[5.3 Test architecture](#53-test-architecture)
&nbsp;&nbsp;&nbsp;&nbsp;[5.4 Ports and ASPs (Abstract Services Primitives)](#54-ports-and-asps-abstract-services-primitives)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.0 Introduction](#540-introduction)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.1 mcaPort, mcaPortIn, mccPort, mccPortIn](#541-mcaport-mcaportin-mccport-mccportin)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.2 utPort](#542-utport)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.2.0 Introduction](#5420-introduction)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.2.1 Usage for Automated AE Testing](#5421-usage-for-automated-ae-testing)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.2.2 Upper Tester Control Primitives](#5422-upper-tester-control-primitives)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.2.2.1 Introduction](#54221-introduction)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.2.2.2 UtTrigger and UtTriggerAck Primitives](#54222-uttrigger-and-uttriggerack-primitives)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.2.2.3 Control Communication Protocol](#54223-control-communication-protocol)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.2.2.4 Control Message Serialization](#54224-control-message-serialization)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.3 acPort](#543-acport)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.4.4 infoPort](#544-infoport)
&nbsp;&nbsp;&nbsp;&nbsp;[5.5 Test components](#55-test-components)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.5.1 Tester](#551-tester)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.5.2 AeSimu](#552-aesimu)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[5.5.3 CseSimu](#553-csesimu)
&nbsp;&nbsp;&nbsp;&nbsp;[5.6 Test strategy](#56-test-strategy)
[6 Untestable Test Purposes](#6-untestable-test-purposes)
[7 ATS Conventions](#7-ats-conventions)
&nbsp;&nbsp;&nbsp;&nbsp;[7.0 Introduction](#70-introduction)
&nbsp;&nbsp;&nbsp;&nbsp;[7.1 Testing conventions](#71-testing-conventions)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[7.1.1 Testing states](#711-testing-states)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[7.1.1.1 Initial state](#7111-initial-state)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[7.1.1.2 Final state](#7112-final-state)
&nbsp;&nbsp;&nbsp;&nbsp;[7.2 Naming conventions](#72-naming-conventions)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[7.2.1 General guidelines](#721-general-guidelines)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[7.2.2 oneM2M specific TTCN-3 naming conventions](#722-onem2m-specific-ttcn-3-naming-conventions)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[7.2.3 Usage of Log statements](#723-usage-of-log-statements)
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[7.2.4 Test Case (TC) identifier](#724-test-case-tc-identifier)
&nbsp;&nbsp;&nbsp;&nbsp;[7.3 IXIT](#73-ixit)
[8 TTCN-3 Verifications](#8-ttcn-3-verifications)
[Annex A (normative): TTCN-3 library modules](#annex-a-normative-ttcn-3-library-modules)
&nbsp;&nbsp;&nbsp;&nbsp;[A.1 Electronic annex, zip file with TTCN-3 code](#a1-electronic-annex-zip-file-with-ttcn-3-code)
[Annex B (informative): Bibliography](#annex-b-informative-bibliography)
[History](#history)
# 1 Scope
The present document contains the Abstract Test Suite (ATS) for oneM2M as defined in oneM2M TS-0001 <a href="#_ref_1">[1]</a> and oneM2M TS-0004 <a href="#_ref_2">[2]</a> in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 96467 <a href="#_ref_5">[5]</a>.
The present document contains the Abstract Test Suite (ATS) for oneM2M as defined in oneM2M TS-0001 <a href="#_ref_1">[1]</a> and oneM2M TS-0004 <a href="#_ref_2">[2]</a> in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 96467 <a href="#_ref_i_6">[i.6]</a>.
The objective of the present document is to provide a basis for conformance tests for oneM2M products giving a high probability of interoperability between different manufacturers' equipment.
The ISO standard for the methodology of conformance testing (ISO/IEC 96461 <a href="#_ref_3">[3]</a> and ISO/IEC 96462 <a href="#_ref_4">[4]</a>) as well as oneM2M TS-0015 Testing Framework <a href="#_ref_i.2">[i.2]</a> are used as a basis for the test methodology.
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 <a href="#_ref_i_4">[i.4]</a> and ISO/IEC 9646-2 <a href="#_ref_i_5">[i.5]</a>) as well as oneM2M TS-0015 <a href="#_ref_i.2">[i.2]</a> are used as a basis for the test methodology.
# 2 References
......@@ -131,11 +94,8 @@ The following referenced documents are necessary for the application of the pres
- <a name="_ref_1">[1]</a> oneM2M TS-0001: "Functional Architecture".
- <a name="_ref_2">[2]</a> oneM2M TS-0004: "Service Layer Core Protocol".
- <a name="_ref_3">[3]</a> ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts".
- <a name="_ref_4">[4]</a> ISO/IEC 9646-2 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification".
- <a name="_ref_5">[5]</a> ISO/IEC 9646-7 (1995): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements".
- <a name="_ref_6">[6]</a> ETSI ES 201 873-1 (V4.5.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language".
- <a name="_ref_7">[7]</a> oneM2M TS-0018: "Test Suite Structure and Test Purposes".
- <a name="_ref_3">[3]</a> ETSI ES 201 873-1 (V4.5.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language".
- <a name="_ref_4">[4]</a> oneM2M TS-0018: "Test Suite Structure and Test Purposes".
## 2.2 Informative references
......@@ -149,12 +109,15 @@ The following referenced documents are not necessary for the application of the
- <a name="_ref_i.2">[i.2]</a> oneM2M TS-0015: "Testing Framework".
- <a name="_ref_i.3">[i.3]</a> oneM2M TS-0025: "Product profiles".
- <a name="_ref_i_4">[i.4]</a> ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts".
- <a name="_ref_i_5">[i.5]</a> ISO/IEC 9646-2 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification".
- <a name="_ref_i_6">[i.6]</a> ISO/IEC 9646-7 (1995): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements".
# 3 Definition of terms, symbols and abbreviations
## 3.1 Terms
For the purposes of the present document, the terms given in ISO/IEC 96461 <a href="#_ref_3">[3]</a>, ISO/IEC 96467 <a href="#_ref_5">[5]</a> and oneM2M TS-0015 <a href="#_ref_i.2">[i.2]</a> apply.
For the purposes of the present document, the terms given in ISO/IEC 9646-1 <a href="#_ref_i_4">[i.4]</a>, ISO/IEC 9646-7 <a href="#_ref_i_6">[i.6]</a> and oneM2M TS-0015 <a href="#_ref_i.2">[i.2]</a> apply.
## 3.2 Symbols
......@@ -167,6 +130,7 @@ For the purposes of the present document, the following abbreviations apply:
`AE Application Entity`
`APT Abstract Protocol Tester`
`ASP Abstract Service Primitives`
`ATM Abstract Test Method`
`ATS Abstract Test Suite`
`CoAP Constrained Application Protocol`
......@@ -176,12 +140,13 @@ For the purposes of the present document, the following abbreviations apply:
`IUT Implementation Under Test`
`IXIT Implementation eXtra Information for Test`
`JSON JavaScript Object Notation`
`M2M Machine to machine`
`MN Middle Node`
`MQTT Message Queuing Telemetry Transport`
`MTC Main Test Component`
`PA Platform Adaptor`
`PICS Protocol Implementation Conformance Statement`
`PTC Paralell Test Component`
`PX PiXit`
`SA System Adaptor`
`SUT System Under Test`
`TC Test Case`
......@@ -201,7 +166,7 @@ The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in
# 5 Abstract Test Method (ATM)
## 5.1 Abstract protocol tester
## 5.1 Abstract protocol tester (APT)
An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address a single test objective.
APTs used by the oneM2M test suite are described in figure 5.1-1. The test system will simulate valid and invalid protocol behaviour, and will analyse the reaction of the IUT.
......@@ -238,18 +203,17 @@ Following this recommendation the oneM2M tester architecture comprises a non-pla
![Figure 5.3-1: High level oneM2M Test Architecture](media/image7.png)
> NOTE: However, it can be implemented in a semi-independent manner, which will minimize the dependency to those elements.
>
**Figure 5.3-1: High level oneM2M Test Architecture**
> NOTE: However, it can be implemented in a semi-independent manner, which will minimize the dependency to those elements.
- **oneM2M** **TTCN** **-3** **Abstract** **Test Suite:** the test suite is platform independent, and it is the cornerstone of the architecture. It allows a complete decoupling between the test suite and the rest of the test system. The test suite is composed of a complete set of test cases covering oneM2M requirements specified by oneM2M TS0001 <a href="#_ref_1">[1]</a> and oneM2M TS-0004 <a href="#_ref_2">[2]</a>.
- **oneM2M System Adaptor** **:** this is the platform dependent part that includes adaptors and codecs (out of the scope of the present document). This part of the architecture definition depends on the specific platform (e.g. Windows or Linux) and test tool on which the tester is going to run.
- **oneM2M System Adaptor** **:** this is the platform dependent part that includes adaptors and codecs (out of the scope of the present document). This part of the architecture definition depends on the specific platform (e.g. Windows&reg; or Linux&reg;) and test tool on which the tester is going to run.
Figure 5.3-2 shows the oneM2M TTCN-3 test architecture design used for the oneM2M ATS. The Test Suite needs to interact with the System Adaptor to implement the collection of TTCN-3 test cases that are intended to be used to test the oneM2M IUTs.
The oneM2M TTCN-3 test cases implement the test algorithms specified in the TSS&TP document oneM2M TS0018 <a href="#_ref_7">[7]</a>, including verdict logic that allows pass/fail diagnosis.
The oneM2M TTCN-3 test cases implement the test algorithms specified in the TSS&TP document oneM2M TS0018 <a href="#_ref_4">[4]</a>, including verdict logic that allows pass/fail diagnosis.
The test algorithms use the interfaces defined in <a href="#_ref_1">[1]</a> and <a href="#_ref_2">[2]</a> (mca, mcc) in order to:
......@@ -305,11 +269,11 @@ Two primitives are currently defined for these ports indicated as table 5.4.1-1:
1. The M2MRequestPrimitive - to send or receive oneM2M messages to/from the IUT. Depending on the IUT to be tested:
1. If the IUT is an AE, these messages are either received or sent by the tester which is associated with the CSE role through the mcaPortIn or the mcaPort respectively.
1. If the IUT is a CSE, these messages are either sent or received by the tester when it plays the AE role through the mcaPort or the mcaPortIn respectively, or sent or received by the tester when it plays the CSE role through the mccPort or the mccPortIn respectively.
- If the IUT is an AE, these messages are either received or sent by the tester which is associated with the CSE role through the mcaPortIn or the mcaPort respectively.
- If the IUT is a CSE, these messages are either sent or received by the tester when it plays the AE role through the mcaPort or the mcaPortIn respectively, or sent or received by the tester when it plays the CSE role through the mccPort or the mccPortIn respectively.
1. The M2MResponsePrimitive - to send or receive oneM2M messages to/from the IUT. Depending on the IUT to be tested:
1. If the IUT is an AE, these messages are either sent or received by the tester which is associated with the CSE role through the mcaPortIn or the mcaPort respectively.
1. If the IUT is a CSE, these messages are either sent or received by the tester when it plays the CSE role through the mccPortIn or the mccPort respectively, sent or received by the tester when it plays the AE role through the mcaPortIn or mcaPort respectively.
- If the IUT is an AE, these messages are either sent or received by the tester which is associated with the CSE role through the mcaPortIn or the mcaPort respectively.
- If the IUT is a CSE, these messages are either sent or received by the tester when it plays the CSE role through the mccPortIn or the mccPort respectively, sent or received by the tester when it plays the AE role through the mcaPortIn or mcaPort respectively.
Both primitives contain another parameters that permits to dynamically configure the test adaptor for every single sending. These parameters are:
......@@ -322,12 +286,17 @@ Both primitives contain another parameters that permits to dynamically configure
**Table 5.4.1-1: Mapping of TTCN-3 Primitives to oneM2M Service Primitives**<a name="table_5.4.1-1"></a>
|TTCN-3 Primitive |oneM2M Message |Direction |IUT |
|-|-|-|-|
|M2MRequestPrimitive |Request Primitive |<=> |AE |
|M2MRequestPrimitive |Request Primitive |<=> |CSE |
|M2MResponsePrimitive |Response Primitive |<=> |AE |
|M2MResponsePrimitive |Response Primitive |<=> |CSE |
+----------------------+-------------------+-------------+-----+
|TTCN-3 Primitive |oneM2M Message | Direction | IUT |
+:====================:+:=================:+:===========:+:===:+
| | | &larr;&rarr;| AE |
| M2MRequestPrimitive |Request Primitive +-------------+-----+
| | | &larr;&rarr;| CSE |
+----------------------+-------------------+-------------+-----+
| | | &larr;&rarr;| AE |
| M2MResponsePrimitive |Respomse Primitive +-------------+-----+
| | | &larr;&rarr;| CSE |
+----------------------+-------------------+-------------+-----+
......@@ -373,11 +342,10 @@ The upper tester triggering message type maps to particular message formats for
**Table 5.4.2.2.1-1: Mapping of TTCN-3 Primitives to oneM2M Service Primitives**<a name="table_5.4.2.2.1-1"></a>
|Upper Tester Control Message Type |TTCN-3 Primitives |Direction |Direction |
|-|-|-|-|
|Trigger |UtTrigger Primitive |TS |UT |
|Trigger Acknowledgement |UtTriggerAck Primitive |UT |TS |
|Upper Tester Control Message Type |TTCN-3 Primitives |Direction |
|-|-|-|
|Trigger |UtTrigger Primitive |TS &rarr; UT |
|Trigger Acknowledgement |UtTriggerAck Primitive |UT &rarr; TS |
......@@ -397,15 +365,81 @@ Table 5.4.2.2.2-1 defines UtTrigger and UtTriggerAck primitives including oneM2M
**Table 5.4.2.2.2-1: UtTrigger and UtTriggerAck Primitive**<a name="table_5.4.2.2.2-1"></a>
|Ut Control Primitive |Mapping to oneM2M data types |Description |Reference |Triggering Message |HTTP message |
|-|-|-|-|-|-|
|_UtTrigger_ _Primitive_ |_requestPrimitive_ |ONLY essential parameters included for certain test case<br /><br />See note 1 |oneM2M<br />TS-0004 <a href="#_ref_2">[2]</a> |**EXAMPLE** **1** **:**<br />If the test objective is to test **_"_** **_Test_** **_System_** **_triggers_** **_IUT_** **_to_** **_execute_** **_a_** **_test_** **_case_** **_for_** **_creation_** **_of_** **_&lt;_** **_AE_** **_>_** **_with_** **_labels_** **_attribute_** **_under_** **_a_** **_CSEBase_** **_resource_** ", then the triggering message would be serialized as following. |**EXAMPLE** **1** **:**<br />If the test objective is to test **_"_** **_Test_** **_System_** **_triggers_** **_IUT_** **_to_** **_execute_** **_a_** **_test_** **_case_** **_for_** **_creation_** **_of_** **_&lt;_** **_AE_** **_>_** **_with_** **_labels_** **_attribute_** **_under_** **_a_** **_CSEBase_** **_resource_** ", then the triggering message would be serialized as following. |
|_UtTrigger_ _Primitive_ |_requestPrimitive_ |ONLY essential parameters included for certain test case<br /><br />See note 1 |oneM2M<br />TS-0004 <a href="#_ref_2">[2]</a> |**Request**<br />{<br />"m2m:rqp" :{<br /> "op": 1, //indicate CREATE operation<br /> "ty": 2, //indicate AE resource type<br /> "to": {TEST\_SYSTEM\_ADDRESS},<br /> "pc": {<br /> "m2m:ae": {<br /> "lbl":"UNINITIALIZED" //indicate that attribute labels needs to be included<br /> },<br /> }<br /> "rvi": "2a"<br />}<br />} |**Reques** **t**<br />**POST** /{SUT\_UT\_APPLICATION\_URL} HTTP/1.1<br />**Host** : {SUT\_IP\_ADDRESS:PORT}<br />**Content-Length** : {PAYLOAD\_LENGTH}<br />**Content-Type** : **application/** **json**<br /><br />{<br />"m2m:rqp" :{<br /> "op": 1, //indicate CREATE operation<br /> "ty": 2, //indicate AE resource type<br /> "to": {TEST\_SYSTEM\_ADDRESS},<br /> "pc": {<br /> "m2m:ae": {<br /> "lbl":"UNINITIALIZED" //indicate that attribute labels needs to be included<br /> }<br /> },<br /> "rvi": "2a"<br />}<br />} |
|_UtTrigger_ _Primitive_ |_requestPrimitive_ |ONLY essential parameters included for certain test case<br /><br />See note 1 |oneM2M<br />TS-0004 <a href="#_ref_2">[2]</a> |**EXAMPLE** **2** **:** <br />If the test objective is to test "**_Test_** **_System_** **_triggers_** **_IUT_** **_to_** **_execute_** **_a_** **_test_** **_case_** **_for_** **_delete_** **_of_** **_a_** **_&lt;_** **_AE_** **_>_** **_resource._** ", then the triggering message would be serialized as following. |**EXAMPLE** **2** **:** <br />If the test objective is to test "**_Test_** **_System_** **_triggers_** **_IUT_** **_to_** **_execute_** **_a_** **_test_** **_case_** **_for_** **_delete_** **_of_** **_a_** **_&lt;_** **_AE_** **_>_** **_resource._** ", then the triggering message would be serialized as following. |
|_UtTrigger_ _Primitive_ |_requestPrimitive_ |ONLY essential parameters included for certain test case<br /><br />See note 1 |oneM2M<br />TS-0004 <a href="#_ref_2">[2]</a> |**Request**<br />{<br />"m2m:rqp" :{<br /> "op": 4, //indicate DELETE operation<br /> "to": {TARGET\_AE\_RESOURCE\_ADDRESS}, //indicate Target AE resource address<br /> "rvi": "2a"<br />}<br />} |**Request**<br />**POST** /{SUT\_UT\_APPLICATION\_URL} HTTP/1.1<br />**Host** : {SUT\_IP\_ADDRESS:PORT}<br />**Content-Length** : {PAYLOAD\_LENGTH}<br />**Content-Type** : **application/** **json**<br /><br />{<br />"m2m:rqp" :{<br /> "op": 4, //indicate DELETE operation<br /> "to": {TARGET\_AE\_RESOURCE\_ADDRESS}, //indicate Target AE resource address<br /> "rvi": "2a"<br />}<br />} |
|_UtTrigger_ _Ack_ _Primitive_ |_responsePrimitive_ |ONLY responseStatusCode attribute included<br /><br />See note 2 |oneM2M TS-0004 <a href="#_ref_2">[2]</a> |**Response**<br />{<br /> "m2m:rsp": {<br /> "rsc": 2000<br /> }<br /><br />}<br />For any triggering response, it only contains a response status code, and the response status code for the triggering operation can only be set to either 2000 (OK) or 4000 (BAD\_REQUEST) according to the rules for triggering operations. |**Response**<br />HTTP/1.1 200 OK<br />X-M2M-RSC: 2000 |
|NOTE 1: Additional rules defined in table 5.4.2.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.2.2.2-3. |NOTE 1: Additional rules defined in table 5.4.2.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.2.2.2-3. |NOTE 1: Additional rules defined in table 5.4.2.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.2.2.2-3. |NOTE 1: Additional rules defined in table 5.4.2.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.2.2.2-3. |NOTE 1: Additional rules defined in table 5.4.2.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.2.2.2-3. |NOTE 1: Additional rules defined in table 5.4.2.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.2.2.2-3. |
+--------------------+-------------------+------------------+-------------------------+---------------------------------------+----------------------------------------+
|Ut Control Primitive|Mapping to oneM2M |Description |Reference |Triggering Message |HTTP |
|message |data types | | | | |
+:===================+:==================+:=================+:========================+:======================================+:=======================================+
|_UtTrigger_ |_requestPrimitive_ |ONLY essential |oneM2M TS-0004 |**EXAMPLE** **1:** If the test objective is to test **_"Test |
|_Primitive_ | |parameters |<a href="#_ref_2">[2]</a>|triggers_ _IUT_ _to execute a test case for creation of &lt;_ _AE_ _> |
| | |included for | |with abels attribute under a_ _CSEBase_ _resource_\"**, then |
| | |certain test | |triggering message would be serialized as following. |
| | |case \ | | |
| | |See NOTE 1 | | |
| | | | +---------------------------------------+----------------------------------------+
| | | | |**Request** \ |**Request** \ |
| | | | |{ \ |**POST** /{SUT\_UT\_APPLICATION\_URL} |
| | | | |"m2m:rqp" :{ \ |HTTP/1.1 \ |
| | | | |"op": 1, //indicate CREATE operation \ |**Host**: {SUT\_IP\_ADDRESS:PORT} \ |
| | | | |"ty": 2, //indicate AE resource type \ |**Content-Length**: {PAYLOAD\_LENGTH} \ |
| | | | |"to": {TEST\_SYSTEM\_ADDRESS}, \ |**Content-Type**: **application/json** \|
| | | | |"pc": { \ | \ |
| | | | |"m2m:ae": { \ |{"m2m:rqp" :{ \ |
| | | | |"lbl":"UNINITIALIZED" //indicate that |"op": 1, //indicate CREATE operation \ |
| | | | |attribute labels needs to be included \|"ty": 2, //indicate AE resource type \ |
| | | | |}, \ |"to": {TEST\_SYSTEM\_ADDRESS}, \ |
| | | | |} \ |"pc": { \ |
| | | | |"rvi": "2a" \ } |"m2m:ae": { \ |
| | | | |} \ |"lbl":"UNINITIALIZED" //indicate that |
| | | | |} |attribute labels needs to be included \ |
| | | | | |} \ |
| | | | | |}, \ |
| | | | | |"rvi": "2a" \ |
| | | | | |} \ |
| | | | | |} \ |
| | | | +---------------------------------------+----------------------------------------+
| | | | |**EXAMPLE** **2:** If the test objective is to test **_"Test System |
| | | | |triggers_ _IUT_ _to execute a test case for delete of &lt;_ _AE_ _> |
| | | | |_resource_\"**, then triggering message would be serialized as following. |
| | | | +---------------------------------------+----------------------------------------+
| | | | |**Request** \ |**Request** \ |
| | | | |{ \ |**POST** /{SUT\_UT\_APPLICATION\_URL} |
| | | | |"m2m:rqp" :{ \ |HTTP/1.1 \ |
| | | | |"op": 4, //indicate DELETE operation \ |**Host**: {SUT\_IP\_ADDRESS:PORT} \ |
| | | | |"to":{TARGET\_AE\_RESOURCE\_ADDRESS}, \|**Content-Length**: {PAYLOAD\_LENGTH} \ |
| | | | |//indicate Target AE resource address |**Content-Type**: **application/json** \|
| | | | |"rvi": "2a" \ | \ |
| | | | |} \ |{"m2m:rqp" :{ \ |
| | | | |} |"op": 4, //indicate DELETE peration\ |
| | | | | |"to":{TARGET\_AE\_RESOURCE\_ADDRESS}, \ |
| | | | | |//indicate Target AE resource address \ |
| | | | | |"rvi": "2a" \ |
| | | | | |} \ |
| | | | | |} \ |
| +-------------------+------------------+-------------------------+---------------------------------------+----------------------------------------+
| |N/A |Special upper |N/A |**"RESET"** |**Request** \ |
| | |tester | | |**POST** /{SUT\_UT\_APPLICATION\_URL} |
| | |commands | | |HTTP/1.1 \ |
| | | | | |**Host** : {SUT\_IP\_ADDRESS:PORT} \ |
| | | | | |**X-M2M-UTCMD: Reset** \ |
+--------------------+-------------------+------------------+-------------------------+---------------------------------------+----------------------------------------+
|_UtTrigger_ |_responsePrimitive_|ONLY |oneM2M TS-0004 |**Response** \ |**Response** \ |
|_Ack_ _Primitive_ | |responseStatusCode|<a href="#_ref_2">[2]</a>|{ \ |HTTP/1.1 200 OK \ |
| | |attribute | |"m2m:rsp": { \ |X-M2M-RSC: 2000 \ |
| | | included \ | |"rsc": 2000 \ | |
| | | \ | |} \ | |
| | | See Note 2. | |} \ | |
| | | | | \ | |
| | | | |For any triggering response, it only | |
| | | | |contains aresponse status code, and the| |
| | | | |response status code for the triggering| |
| | | | |operation can only be set to either | |
| | | | |either 2000 (OK) or 4000 (BAD\_REQUEST)| |
| | | | |according to the rules for triggering | |
| | | | | operations. | |
+--------------------+-------------------+------------------+-------------------------+---------------------------------------+----------------------------------------+
|NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied. \ |
|NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
......@@ -431,17 +465,23 @@ The rules for defining UtTrigger and UtTriggerAck primitives are:
**Table 5.4.2.2.2-3: Definition of ResponseStatusCode for UtTriggerAck primitive**<a name="table_5.4.2.2.2-3"></a>
|Response Status Code Description |Response Status Code Value |Interpretation |
|-|-|-|
|OK |2000 |The SUT receives successfully the triggering message from Test System |
|BAD\_REQUEST |4000 |The SUT does not interpret correctly the UtTrigger primitive |
|NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. |NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. |NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. |
+------------------------+-----------------+--------------------------------------------------+
|Response Status |Response Status |Interpretation |
|Code Description |Code Value | |
+:=======================+:================+:=================================================+
|OK |2000 |The SUT receives successfully the triggering |
| | |message from Test System |
+------------------------+-----------------+--------------------------------------------------+
|BAD\_REQUEST |4000 |The SUT does not interpret correctly the UtTrigger|
| | |primitive |
+------------------------+-----------------+--------------------------------------------------+
|NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. |
+------------------------+-----------------+--------------------------------------------------+
##### 5.4.2.2.3 Control Communication Protocol
Protocol used for proceeding communications between Test System and Upper Tester Application is designated to the Hypertext Transfer Protocol (HTTP) protocol owning it is an application protocol that is widely supported by most all IoT devices and various intrinsic features such as persistent connection, ease of programming, flexibility, etc.
Protocol used for proceeding communications between Test System and Upper Tester Application is designated to the Hypertext Transfer Protocol (HTTP) protocol owning it is an application protocol that is widely supported and various intrinsic features such as persistent connection, ease of programming, flexibility, etc.
##### 5.4.2.2.4 Control Message Serialization
......@@ -464,30 +504,71 @@ The Tester test component includes a set of ports, timers and variables that are
**Table 5.5.1-1: Tester component elements**<a name="table_5.5.1-1"></a>
|Name |Instance type |Element type |Description |
|-|-|-|-|
|acPort |port |AdapterControlPort |Port that communicates with the adapter for sending configuration parameters |
|infoPort |port |InfoPort |Port between test components for exchanging information |
|utPort |port |UpperTesterPort |Port that communicates with the UT Application for triggering actions on the IUT |
|tc\_ac |timer |N/A |Timer for the reception of a message |
|tc\_wait |timer |N/A |Timer for the reaction of the IUT to an upper tester primitive |
|tc\_done |Timer |N/A |Timer for waiting completion of a component behaviour |
|vc\_config |variable |Configurations |Configuration being used for the given test case |
|vc\_testSystemRole |variable |TestSystemRole |Role of the test component |
|vc\_componentRegistered |variable |boolean |Flag to indicate that AeSimu/CseSimu is registered to IUT |
|vc\_resourcesList |variable |MyResourcesList |List of all resources created by the test system on the IUT |
|vc\_resourcesIndexToBeDeleted |variable |IntegerList |List of indexes of resources created by the test system on the IUT that need to be deleted |
|vc\_acpIndex |variable |integer |Index of accessControlPolicy resource used by the test system by default (when required) |
|vc\_request |variable |MsgIn |Latest request primitive received/sent |
|vc\_response |variable |MsgIn |Latest response primitive received/sent |
|vc\_aeSimu |variable |default |Reference to the default behaviour for an AeSimu component |
|vc\_cseSimu |variable |default |Reference to the default behaviour for an CseSimu component |
|vc\_primitiveContentRetrievedResource |variable |PrimitiveContent |Latest content of a RETRIEVE operation |
|vc\_myInterfaces |variable |Interfaces |Parameters for the ports of the given component:<br />Port (mcaPort, mcaPortIn, mccPort, mccPortIn)<br />Host (SUT IP address :port)<br />Protocol binding<br />Serialization |
Note that vc\_aeSimu and vc\_cseSimu are not common to the other defined test components, but those variables are required in Tester for the correct activation/deactivation of default behaviours.
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|Name |Instance type |Element type |Description |
+:========================================+:=============+:==================+:=======================================+
|acPort |port |AdapterControlPort |Port that communicates with the adapter |
| | | |for sending configuration parameters |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|infoPort |port |InfoPort |Port between test components for |
| | | |exchanging information |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|utPort |port |UpperTesterPort |Port that communicates with the UT |
| | | |Application for triggering actions on |
| | | |the IUT |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|tc\_ac |timer |N/A |Timer for the reception of a message |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|tc\_wait |timer |N/A |Timer for the reaction of the IUT to an |
| | | |upper tester primitive |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|tc\_done |timer |N/A |Timer for waiting completion of a |
| | | |component behaviour |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_config |variable |Configurations |Configuration being used for the given |
| | | |test case |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_testSystemRole |variable |TestSystemRole |Role of the test component |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_componentRegistered |variable |boolean |Flag to indicate when a component has |
| | | |registered to the IUT |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_resourcesList |variable |MyResourcesList |List of all resources created by the |
| | | |test system on the IUT |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_resourcesIndexToBeDeleted |variable |IntegerList |List of indexes of resources created by |
| | | |the test system on the IUT that need to |
| | | |be deleted |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_acpIndex |variable |integer |Index of accessControlPolicy resource |
| | | |used by the test system by default |
| | | |(when required) |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_request |variable |MsgIn |Latest request primitive received/sent |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_response |variable |MsgIn |Latest response primitive received/sent |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_aeSimu |variable |default |Reference to the default behaviour for |
| | | |an AeSimu component |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_cseSimu |variable |default |Reference to the default behaviour for |
| | | |an CseSimu component |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_primitiveContentRetrievedResource |variable |PrimitiveContent |Latest content of a RETRIEVE operation |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|vc\_myInterfaces |variable |Interfaces |Parameters for the ports of the given |
| | | |component: |
| | | | |
| | | |- Port (mcaPort, mcaPortIn, mccPort, |
| | | |mccPortIn) |
| | | |- Host (SUT IP address :port) |
| | | |- Protocol binding |
| | | |- Serialization |
+-----------------------------------------+--------------+-------------------+----------------------------------------+
|Note that vc\_aeSimu and vc\_cseSimu are not common to the other defined test components, but those variables are |
|required in Tester for the correct activation/deactivation of default behaviours. |
+---------------------------------------------------------------------------------------------------------------------+
### 5.5.2 AeSimu
......@@ -690,30 +771,33 @@ Furthermore, the following rules are applied too:
**Table 7.2.4-1: TC naming convention**<a name="table_7.2.4-1"></a>
|Identifier: |TC\_&lt;root>\_&lt;gr>\_&lt;sgr>\_&lt;nn>\_&lt;per> | | |
|-|-|-|-|
| |&lt;root> = root |ONEM2M |oneM2M |
| |&lt;gr> = group |CSE |CSE testing |
| | |AE |AE testing |
| |&lt;sgr> = subgroup |REG |Registration |
| | |DMR |Data Management and Repository |
| | |SUB |Subscription and Notification |
| | |GMG |Group Management |
| | |DIS |Discovery |
| | |LOC |Location |
| | |DMG |Device Management |
| | |CMDH |Communication Management and Delivery Handling |
| | |SEC |Security |
| |&lt;nn> = sequential number | |001 to 999 |
| |&lt;per> = permutation |P1\_P2\_..PN |Permutation parameters |
+-----------------------------------------------------------------------------------------------+
|Identifier: TC\_&lt;root>\_&lt;gr>\_&lt;sgr>\_&lt;nn>\_&lt;per> |
+:===========================+:===============+:================================================+
|&lt;root> = root |ONEM2M |oneM2M |
+----------------------------+----------------+-------------------------------------------------+
|&lt;gr> = group |CSE \ |CSE testing \ |
| |AE |AE testing |
+----------------------------+----------------+-------------------------------------------------+
|&lt;sgr> = subgroup |REG \ |Registration \ |
| |DMR \ |Data Management and Repository \ |
| |SUB \ |Subscription and Notification \ |
| |GMG \ |Group Management \ |
| |DIS \ |Discovery \ |
| |LOC \ |Location \ |
| |DMG \ |Device Management \ |
| |CMDH \ |Communication Management and Delivery Handling \ |
| |SEC |Security |
+----------------------------+----------------+-------------------------------------------------+
|&lt;nn> = sequential number | |001 to 999 |
+----------------------------+----------------+-------------------------------------------------+
|&lt;per> = permutation |P1\_P2\_..PN |Permutation parameters |
+----------------------------+----------------+-------------------------------------------------+
|`EXAMPLE: TP identifier: TP/oneM2M/CSE/DMR/CRE/001` \ |
|`TC identifier: TC\_ONEM2M\_CSE\_DMR\_CRE\_001.` |
+-----------------------------------------------------------------------------------------------+
`EXAMPLE: TP identifier: TP/oneM2M/CSE/DMR/CRE/001`
`TC identifier: TC\_ONEM2M\_CSE\_DMR\_CRE\_001.`
## 7.3 IXIT
The following parameters are used by the oneM2M ATS for the correct execution of the test cases.
......@@ -748,7 +832,7 @@ The following parameters are used by the oneM2M ATS for the correct execution of
|IutParameters |PX\_XML\_NAMESPACE |XML Namespace |"m2m=""http://www.onem2m.org/xml/protocols""" |
|IutParameters |PX\_ACOR |AccessControlOriginators |{"all"} |
|IutParameters |PX\_TCONFIG\_IUT |Time to configure IUT after a requested action |10.0 |
|TesterParameters |PX\_TS\_AE1 |AE1 component settings |aeIdStem = ""<br />appId = "NMyApp1Id"<br />mcaPort and mcaPortIn settings which include per port the following info:<br />Binding:<br /> - bindingProtocol<br /> - bindingDesc:<br /> - tsAddress<br /> - localPort<br /> - sutAddress<br /> - remotePort<br />Serialization |
|TesterParameters |PX\_TS\_AE1 |AE1 component settings |aeIdStem = ""<br />appId = "NMyApp1Id"<br />mcaPort and mcaPortIn settings which include per port the following info:<br />Binding:<br />- bindingProtocol<br />- bindingDesc:<br /> - tsAddress<br /> - localPort<br /> - sutAddress<br /> - remotePort<br />Serialization |
|TesterParameters |PX\_TS\_AE2 |AE2 component settings |aeIdStem = ""<br />appId = "NMyApp2Id"<br />mcaPort and mcaPortIn settings which include per port the following info:<br />Binding:<br /> - bindingProtocol<br /> - bindingDesc:<br /> - tsAddress<br /> - localPort<br /> - sutAddress<br /> - remotePort<br />Serialization |
|TesterParameters |PX\_TS\_CSE1 |CSE1 component settings |cseName = "CSE1\_NAME"<br />cseId = "/CSE1\_ID"<br />cseResourceId = "CSE1\_RESOURCE\_ID"<br />spId = "//onem2m.org"<br />supportedResourceType = {int1, int2, int3, int16}<br />mcaPort, mcaPortIn, mccPort and mccPortIn settings which include per port the following info:<br />Binding:<br /> - bindingProtocol<br /> - bindingDesc:<br /> - tsAddress<br /> - localPort<br /> - sutAddress<br /> - remotePort<br />Serialization |
| |PX\_TS\_UT |UpperTester settings |url = "http://127.0.0.1:43000/" |
......@@ -773,7 +857,7 @@ This test suite has been compiled error-free using two different commercial TTCN
The TTCN-3 library modules, which form parts of the present document, are contained in the following gitLab tag:
[https://git.onem2m.org/TST/ATS/-/tags/TS-0019-baseline-v2\_8\_0](https://git.onem2m.org/TST/ATS/-/tags/TS-0019-baseline-v2\_8\_0)<br />
[https://git.onem2m.org/TST/ATS/-/tags/TS-0019-baseline-v2\_9\_2](https://git.onem2m.org/TST/ATS/-/tags/TS-0019-baseline-v2\_9\_2)<br />
# Annex B (informative): Bibliography
......@@ -786,17 +870,52 @@ oneM2M TS-0031: "Feature catalogue".
# History
|**Version** |**Date** |**Publication history** |
|-|-|-|
|V2.0.0 |2018-07-27 |Base document from TS-0019 v1.0.0 |
|V2.1.0 |2018-11-20 |Integrated approved contributions:<br />TST-2018-0147-TS-0019\_Test\_strategy\_and\_test\_component\_details\_R2 |
|V2.2.0 |2019-04-24 |Integrated approved contributions:<br />TDE-2019-0050-TS-0019\_Test\_strategy\_and\_pixits\_R2 |
|V2.3.1 |July 2019 |Partners pre-processing done by **_editHelp!_** <br />e-mail: [mailto:edithelp@etsi.org](mailto:edithelp@etsi.org) |
|V2.4.0 |Sep 2019 |Integrated approved contributions:<br />TDE-2019-0162-TTCN-3\_Test\_cases |
|V2.5.0 |May 2020 |Integrated approved contributions:<br />TDE-2020-0043-[TS-0019\_TTCN-3\_Test\_cases\_R2](TS-0019\_TTCN-3\_Test\_cases\_R2)<br />[TDE-2020-0044R01](TDE-2020-0044R01)-[TS-0019\_Update\_Test\_components\_variables\_R2](TS-0019\_Update\_Test\_components\_variables\_R2) |
|V2.6.0 |Jan 2021 |Integrated approved contributions:<br />TDE-2020-0105-TS-0019\_TTCN3\_Test\_cases\_R2 |
|V2.7.0 |Jan 2022 |Integrated approved contributions:<br />TDE-2021-0070-TS-0019\_TTCN3\_Test\_cases\_R2 <br />TDE-2022-0001-TS-0019_Update_Test_components_variables_R2|
|V2.8.0 |Apr 2023|Integrated approved contributions:<br />TDE-2023-0001-TS-0019\_TTCN3\_Test\_cases\_R2|
|V2.9.0 |Jan 2024 |Integrated approved contributions:<br />TDE-2023-0050-TS-0019-Adaptation\_from\_converted\_version\_R2 |
+-----------------------------------------------------------------------------------------------+
|**Document history** |
+:======+:==========+:==========================================================================+
|V2.0.0 |2018-07-27 |Base document from TS-0019 v1.0.0 |
+-------+-----------+---------------------------------------------------------------------------+
|V2.1.0 |2018-11-20 |Integrated approved contributions: |
| | | |
| | |- TST-2018-0147-TS-0019\_Test\_strategy\_and\_test\_component\_details\_R2 |
+-------+-----------+---------------------------------------------------------------------------+
|V2.2.0 |2019-04-24 |Integrated approved contributions: |
| | | |
| | |- TDE-2019-0050-TS-0019\_Test\_strategy\_and\_pixits\_R2 |
+-------+-----------+---------------------------------------------------------------------------+
|V2.3.1 |July 2019 |Partners pre-processing done by **_editHelp!_** |
| | |e-mail: [mailto:edithelp@etsi.org](mailto:edithelp@etsi.org) |
+-------+-----------+---------------------------------------------------------------------------+
|V2.4.0 |Sep 2019 |Integrated approved contributions: |
| | | |
| | |- TDE-2019-0162-TTCN-3\_Test\_cases |
+-------+-----------+---------------------------------------------------------------------------+
|V2.5.0 |May 2020 |Integrated approved contributions: |
| | | |
| | |- TDE-2020-0043-TS-0019\_TTCN-3\_Test\_cases\_R2 |
| | |- TDE-2020-0044R01-TS-0019\_Update\_Test\_components\_variables\_R2 |
+-------+-----------+---------------------------------------------------------------------------+
|V2.6.0 |Jan 2021 |Integrated approved contributions: |
| | | |
| | |- TDE-2020-0105-TS-0019\_TTCN3\_Test\_cases\_R2 |
+-------+-----------+---------------------------------------------------------------------------+
|V2.7.0 |Jan 2022 |Integrated approved contributions: |
| | | |
| | |- TDE-2021-0070-TS-0019\_TTCN3\_Test\_cases\_R2 |
| | |- TDE-2022-0001-TS-0019_Update_Test_components_variables_R2 |
+-------+-----------+---------------------------------------------------------------------------+
|V2.8.0 |Apr 2023 |Integrated approved contributions: |
| | | |
| | |- TDE-2023-0001-TS-0019\_TTCN3\_Test\_cases\_R2 |
+-------+-----------+---------------------------------------------------------------------------+
|V2.9.0 |Jan 2024 |Integrated approved contributions: |
| | | |
| | |- TDE-2023-0050-TS-0019-Adaptation\_from\_converted\_version\_R2 |
+-------+-----------+---------------------------------------------------------------------------+
|V2.9.1 |2024-02-15 |Some editorials |
+-------+-----------+---------------------------------------------------------------------------+
|V2.9.2 |2025-02-13 |Partners pre-processing done by **_editHelp!_** \ |
| | |e-mail: [edithelp@etsi.org](edithelp@etsi.org) |
+-------+-----------+---------------------------------------------------------------------------+
| | | |
+-------+-----------+---------------------------------------------------------------------------+