1. Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., yinjiaxin@huawei.com Meeting Date: 2015-1-7 Agenda Item: TBD

2. Asking for input from WGs What need to be tested? – Primitive procedures? - PRO – DM procedures? - MAS – HTTP, CoAP, MQTT bindings? – PRO – OMA DM 1.3&2.0, OMA LWM2M, BBF TR069 interworking? – MAS – Security procedures? - SEC How to test? – Conformance test – Interoperability test Call for test requirements from WGs Need to test all covered requirements from R1 of TS0001? © 2013 oneM2M Partners 2

3. The hierarchy of calls Test Group Stage 1 Stage 2 Stage 3 Test Requirement1Test Requirement2Test Requirement3 REQ+SEC+MAS ARC+SEC+MAS PRO+SEC+MAS Test Case Testing WG Test Step Test Sequence Test Step Test Sequence Test Step Test Sequence Test Step Test Sequence

4. Call for test requirements Originated from covered requirements from TS0001 Release 1 Indicates requirements that needs to have corresponding test specifications in WG6. The test requirements will be contributed to deliverables in WG6. The test requirements are also important inputs to ARC WG when writing Test Groups.

5. Call for test groups A test group is a collection of test cases that can be categorized into the fulfillment of the same function. Example of test group can be: – Registration – Update firmware – …

6. Call for test cases A test case has one clear purpose for example the test of notification results from a change to one of the resource. It’s composed of several steps. – Steps may form sequences by their order. – Some of the steps are preambles which could be commonly used to establish necessary resource structure. – Some of them are postamble to change the resource result from the step.

7. In WG6 we will Design architecture or deployment of the test Design detailed test steps to test all feedbacks from REQ, ARC, PRO, SEC and ARC. Fill in what was left from a test case: – Preambles – Test sequence (diagram of the procedure) – Expected output – etc…

8. Questions?