1. Testing Framework TST 15 Source: Laurent Velez, ETSI, laurent.velez@etsi.orglaurent.velez@etsi.org Meeting Date: 2015-01-15 TST-2015-0017-Testing_framework.PPT

2. Current status in WG TST A set of oneM2M test specifications: – TST-spec: Interoperability Test Descriptions of oneM2M Primitives WG TST had many contributions proposing definitions, test architectures, conventions. Problem: many contributions or discussions refer to “testing” without indicating if it is about Interoperability and conformance. – we may define all the testing terminology in a Testing Framework, describing the oneM2M Test methodology. – This document may then be usedin all the future contributions and Test specifications produced by WG TST.

3. Testing framework needs For the testing activities, everybody will talk the same languages using commonly agreed terminology and proccess. All the test specifications produced by oneM2M will be homogenous whatever the scope of they address (unless it is specifically required to use other methodology). It is important for going to third-party Certification body to be able to present the test methodology ( for ex, required by GCF). Otherwise, certification body will require to use his methodology.

4. Proposed testing framework Common set of definitions and conventions Interoperability Testing: Conformance Testing Development of test specifications and test suites  Similar proposed framework has been used in 3GPP and many other Technical Bodies, like ETSI TC ITS (Intelligent Transport System : see ETSI EG 202 798)

5. Conformance testing Tests a specific (part of a) product for compliance to requirements in a Base Standard

6. Interoperability testing Tests (end-to-end) functionality between two or more products

7. Conformance testing methodology Identification of candidate "Implementations Under Test" (IUT); Identification of reference points; Identification of the Abstract Test Method: – abstract protocol tester. It is a process providing the test behaviour for testing an IUT. Thus it will emulate a peer IUT of the same layer/the same entity. – functional test architecture describing how to implement the abstract test architecture

8. Interop testing methodology Identification of candidate EUTs. Identification of test scenarios. Definition of test bed architecture. Identification of test bed interfaces.

9. Development of test specifications Guidance to write test specifications and to develop test suites: Developing "Implementation Conformance Statements" (ICS) or "Interoperable Functions Statement" (IFS) – Developing "Test Suite Structure and Test Purposes" (TSS&TP) from ICS and base standards. – Developing "Test Descriptions" (TDs) from base standards. – Developing test suite, e.g. naming conventions, code documentation, test case structure.

10. Next Steps ? Need a New WI for Test methodology WI to be created at TP#15 Start of work at TP#16