1. Issues pertaining to IOP test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: 2015-7-19 Agenda Item: TBD

2. Issue One - Duplication The test description is highly coupled. – Between no hop, single hop and multi hop – Between normal case, non-blocking sync case and non-blocking async case – Between similar procedure among different resource types. The same content is copy pasted for several times Problem: – Hard to maintain under changes – Easy to make mistakes © 2014 oneM2M Partners 2

3. Issue One - Duplication Proposal: – Focus on Test Description of no hop, single hop and multi hop is composed of no hop eventually – Focus on common Test Description that applies to most of the resource operations, and figure out the differentiations with regard to specific resource types. – Need to think up a way to reference which is helpful to understanding

4. Issue Two – unclearness of the condition The success perform of the Test Description relies on some pre-conditions. – Security association establishment – Service subscription – Registration of CSE or AE – Existence of resource to be manipulated – Allocation of identity The pre-condition is highly reused by multiple resource but still exists some difference.

5. Issue Two – unclearness of the condition Proposals: – Figure out and define several pre-conditions that can be referenced by each Test Description – Some pre-conditions may rely on some test descriptions. As a pre-condition the existence of a resource relies on the create procedure.

6. Issue Three – inconsistency and mistaken The procedure of primitive is not defined The procedure of binding is defined but sometimes with inconsistencies between different bindings. – For example: request identifier is included in some MQTT binding, but not included in some other HTTP and CoAP binding. – Short name and long name are both used but not in a consistent way.

7. Issue Three – inconsistency and mistaken Proposals: – Focus on the common procedure of primitives, spend some time to guarantee its correctness. – Work on each binding of the primitive – For the test description of each resource type, we figure out the margin part

8. Issue Four: missing test descriptions We still miss some test descriptions – Remote for no hop case – The test description for fanOutPoint, node, mgmtObj… – The AE and CSE registration test description is not correct

9. Way forward We focus on the no hop test description with primitive and the bindings. We divide the all the no hop test description to volunteers to define the test description following container. Another clause for retargeting which will cover single hop and multihop. Another clause for nonblocking syc and async Add a table of test description numbers for single hop. The test description for container can be repeated.