TDE-2025-0002-TS-0019-ATS_v3_5_2_baseline
Compare changes
@@ -7,14 +7,29 @@
|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 /> |
@@ -27,7 +42,7 @@
@@ -43,7 +58,7 @@ More information about oneM2M may be found at: http//www.oneM2M.org
@@ -59,69 +74,14 @@ NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURA
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>.
@@ -134,13 +94,10 @@ The following referenced documents are necessary for the application of the pres
@@ -153,13 +110,17 @@ The following referenced documents are not necessary for the application of the
@@ -172,6 +133,7 @@ For the purposes of the present document, the following abbreviations apply:
@@ -181,12 +143,13 @@ For the purposes of the present document, the following abbreviations apply:
@@ -206,7 +169,7 @@ The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in
@@ -243,14 +206,14 @@ Following this recommendation the oneM2M tester architecture comprises a non-pla
- **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.
@@ -310,11 +273,11 @@ Two primitives are currently defined for these ports indicated as table 5.4.1-1:
@@ -327,13 +290,17 @@ Both primitives contain another parameters that permits to dynamically configure
@@ -407,10 +374,10 @@ The upper tester triggering message type maps to particular message formats for
@@ -428,18 +395,84 @@ Table 5.4.4.2.2-1 defines UtTrigger and UtTriggerAck primitives including oneM2M
|_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 <_** **_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 <_** **_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 />} |**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": 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 <_** **_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 <_** **_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.4.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. |NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. |NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. |NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. |NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. |NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.<br />NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. |
@@ -452,6 +485,7 @@ Table 5.4.4.2.2-1 defines UtTrigger and UtTriggerAck primitives including oneM2M
@@ -470,17 +504,24 @@ The rules for defining UtTrigger and UtTriggerAck primitives are:
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.
@@ -503,27 +544,75 @@ The Tester test component includes a set of ports, timers and variables that are
@@ -760,30 +849,33 @@ Furthermore, the following rules are applied too:
@@ -818,7 +910,7 @@ The following parameters are used by the oneM2M ATS for the correct execution of
|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 |
|TesterParameters |PX\_TS\_CSE2 |CSE2 component settings |cseName = "CSE2\_NAME"<br />cseId = "/CSE2\_ID"<br />cseResourceId = "CSE2\_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 |
@@ -849,7 +941,7 @@ This test suite has been compiled error-free using two different commercial TTCN
@@ -862,13 +954,34 @@ oneM2M TS-0031: "Feature catalogue".