1. Planning for the test event Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., yinjiaxin@huawei.com Meeting Date: 2015-2-25 Agenda Item: TBD

2. Outline Pre-requisites Time & Location Procedure How to minute & Output Support needed Future planning © 2015 oneM2M Partners 2

3. Pre-requisites Rename – “Interoperability Test Event” to “Interoperability Test Activity” – To avoid the confusion with Certification procedure. Purpose: – Improve the understanding of the specification among companies that has oneM2M compliant systems. – Improve the specification based on the output minute during the activity. – Get ready for certification. Have some early stage first hand material and experience. Things needed: – Test specifications are ready for most of the parts. – oneM2M compliant devices and platforms are ready. – Logistic documents ready to define how are we going to proceed the test activity. – Excel sheets ready to record all the tests. – Documents ready to minute the output of the event – Plans on how to leverage the outputs to the TSes. – Host of the test activities include the testing equipments

4. Time & Location Three meeting cycles to develop the details of the HTTP TST binding. CoAP Interoperability test may be accomplished before TP#19. Option 1 USA Option 2 EU

5. Procedure Candidate Phase – Company who are going to participate the test activity submit their application form, in which the following information should be included: Entity to be tested (AE, MN-CSE, IN-CSE, ASN-CSE…). Test cases to go through People attend the activity – TST WG confirm the host and facilities to support the test activity. Pairing Phase – According to the submitted Entities to be tested. Arrange the pairing of the Entities. – IN-CSE to AE, IN-CSE to MN-CSE, AE to MN-CSE etc. – Arrange the schedule of the testing. Candidate PhasePairing PhaseTesting PhaseSummary Phase

6. Procedure Testing Phase – Test the Entities following the schedule. – Minute the mismatches, inconsistencies, different understandings occurred during the test. – The minutes will be input to the summary phase Summary Phase – Participate companies analyze the minutes, try to solve the mismatches recorded. See if they are: unclearness of the spec system not correctly implemented mistake of the spec – Bring contributions, CRs to improve the spec, or correct the system implementation. Several documents need to be generated to record the procedures – new WI? – Put them in the Testing Framework document? Candidate PhasePairing PhaseTesting PhaseSummary Phase

7. How to minute and Output Minutes will be organized by cases. For each test case, the following things need to be recorded: – Time – Test Case ID – Test Parties – Tested Entities – Phenomenon record – Action item to be tracked – Other comments Output: – A description of the overall situation of the test activity – A description for each company of the submitted system to be tested and the test result. How many test cases? How many other companies system interworked with? What’s the result of each test? – A list of problems stated in the test activity and the description of each problem. – A collection of CRs to be submitted afterwards pertaining to the problems spotted.

8. Support needed An extension of the time – Friday afternoon? – Saturday? An extension of the facility support of the TP meeting – Needs additional budget – Negotiate with the organizer Other equipments

9. Future planning consideration Land on the ground before thinking the next step. A few high standard compliant systems after a few rounds of test activity. More and more companies to join are expected. Cross testing may become an tedious job after some time. Start to consider automatic test machine. Start to investigate how to build the test platform or test tools. Volunteer companies to build an automatic conformance test machine to run the test cases. Or may be try to run an community to write the test tools? Route to self-testing with the help of oneM2M?

10. Thanks!