Miguel Angel Reina Ortega · 4a7a1cb2
--- a/TS-0019-Abstract_Test_Suite_&_implementation_eXtra_Information_for_Test.md

+ 21

− 14
+++ b/TS-0019-Abstract_Test_Suite_&_implementation_eXtra_Information_for_Test.md

+ 21

− 14
 @@ -26,7 +26,7 @@ The present document has not been subject to any approval process by the oneM2M
 The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. 
 More information about oneM2M may be found at:  http//www.oneM2M.org
 Copyright Notification
-© 2019, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).
+� 2019, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).
 All rights reserved.
 The copyright extends to reproduction in all media.

 @@ -137,9 +137,9 @@ History    25


 # <br/>1    Scope
-The present document contains the Abstract Test Suite (ATS) for oneM2M as defined in oneM2M TS-0001 [1] and oneM2M TS-0004 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 96467 [5].
+The present document contains the Abstract Test Suite (ATS) for oneM2M as defined in oneM2M TS-0001 [1] and oneM2M TS-0004 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 96467�[5].
 The objective of the present document is to provide a basis for conformance tests for oneM2M products giving a high probability of interoperability between different manufacturers' equipment.
-The ISO standard for the methodology of conformance testing (ISO/IEC 96461 [3] and ISO/IEC 96462 [4]) as well as oneM2M TS-0015 Testing Framework [i.2] are used as a basis for the test methodology.
+The ISO standard for the methodology of conformance testing (ISO/IEC 96461�[3] and ISO/IEC�96462�[4]) as well as oneM2M TS-0015 Testing Framework�[i.2] are used as a basis for the test methodology.

 # 2    References

 @@ -177,7 +177,7 @@ The following referenced documents are not necessary for the application of the

 ## 3.1    Terms

-For the purposes of the present document, the terms given in ISO/IEC 96461 [3], ISO/IEC 96467 [5] and oneM2M TS-0015 [i.2] apply.
+For the purposes of the present document, the terms given in ISO/IEC�96461�[3], ISO/IEC�96467�[5] and oneM2M TS-0015 [i.2] apply.

 ## 3.2    Symbols
 Void.
 @@ -264,7 +264,7 @@ As figure 5.1-1 illustrates, the corresponding ATS needs to use lower layers to

 ### 5.2.1    AE Test Configuration
 Test configurations are defined to test different entities such as CSE and AE, etc.
-Figure 5.2.1-1 shows a AE test configuration which is mapped to CF03 in clause 6.3.3.3 in oneM2M TS0015 [i.2] and aligns with conformance test system architecture in clause 6.3.3.2 in oneM2M TS-0015 [i.2].
+Figure 5.2.1-1 shows a AE test configuration which is mapped to CF03 in clause 6.3.3.3 in oneM2M TS0015�[i.2] and aligns with conformance test system architecture in clause 6.3.3.2 in oneM2M TS-0015 [i.2].
 The TTCN-3 Test Component in Test System sends triggering actions or behaviour to the Upper Tester Application of SUT through upper tester transport link Ut while the IUT sends/receives oneM2M service primitives through Mca to/from CSE in Test System.

 ![media/image6.png](media/image6.png)
 @@ -285,10 +285,10 @@ 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 [1] and oneM2M TS-0004 [2].
- 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.
+- 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.

 Figure 5.3-2 shows the oneM2M TTCN-3 test architecture design used for the oneM2M ATS. The Test Suite needs to interact with the System Adaptor to implement the collection of TTCN-3 test cases that are intended to be used to test the oneM2M IUTs.
-The oneM2M TTCN-3 test cases implement the test algorithms specified in the TSS&TP document oneM2M TS0018 [7], including verdict logic that allows pass/fail diagnosis.
+The oneM2M TTCN-3 test cases implement the test algorithms specified in the TSS&TP document oneM2M TS0018�[7], including verdict logic that allows pass/fail diagnosis.
 The test algorithms use the interfaces defined in [1] and [2] (mca, mcc) in order to:

 1. control the test event to be sent towards the IUT; and
 @@ -594,7 +594,7 @@ As necessary, further actions may be included in the f_postamble functions.
 This test suite follows the naming convention guidelines provided in oneM2M TS-0015 [i.2].
 The naming convention is based on the following underlying principles:

- in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 7.2.1-1) indicating the type of TTCN3 element it represents;
+- in most cases, identifiers should be prefixed with a short alphabetic string (specified in table�7.2.1-1) indicating the type of TTCN3 element it represents;
 - suffixes should not be used except in those specific cases identified in table 7.2.1-1;
 - prefixes and suffixes should be separated from the body of the identifier with an underscore ("_");

 @@ -605,7 +605,7 @@ The naming convention is based on the following underlying principles:

 `EXAMPLE 2:    f_initialState.`

-Table 7.2.1-1 specifies the naming guidelines for each element of the TTCN3 language indicating the recommended prefix, suffixes (if any) and capitalization.
+Table�7.2.1-1 specifies the naming guidelines for each element of the TTCN3 language indicating the recommended prefix, suffixes (if any) and capitalization.

 **Table 7.2.1-1: TTCN-3 generic naming conventions**

 @@ -640,7 +640,7 @@ Table
 ### 7.2.2    oneM2M specific TTCN-3 naming conventions
 Next to such general naming conventions, table 7.2.2-1 shows specific naming conventions that apply to the oneM2M TTCN-3 ATS.

-**Table 7.2.2-1: oneM2M specific TTCN-3 naming conventions**
+**Table�7.2.2-1: oneM2M specific TTCN-3 naming conventions**

 |Language element |Naming convention |Prefix |Example identifier |
 |-|-|-|-|
 @@ -667,7 +667,7 @@ All TTCN-3 log statements use the following format using the same order:

 Furthermore, the following rules are applied too:

- All TTCN-3 setverdict statements are combined (as defined in TTCN-3 - ETSI ES 201 873-1 [6]) with a log statement following the same above rules (see example 2).
+- All TTCN-3 setverdict statements are combined (as defined in TTCN-3 - ETSI�ES 201 873-1 [6]) with a log statement following the same above rules (see example 2).

 `EXAMPLE 2:    setverdict(pass, "TC_ONEM2M_CSE_DMR_CRE_001: Received correct message");`

 @@ -742,23 +742,30 @@ The following parameters are used by the oneM2M ATS for the correct execution of
 # 8    TTCN-3 Verifications
 The principles for Verifying the TTCN-3 test code are given in oneM2M TS-0015 [i.2].

+Adding a new change
+
 All test cases provided with the present document in annex A which correspond to at least one of the product profiles defined in oneM2M TS-0025 [i.3] have been verified at the time of publication of the present document which corresponds with the TTCN-3 code gitlab tag provided in annex A.

 # <br/>Annex A (normative):<br/>TTCN-3 library modules

 ## A.1    Electronic annex, zip file with TTCN-3 code
-This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 [6].
+This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI�ES 201 873-1 [6].

 This test suite has been compiled error-free using two different commercial TTCN-3 compilers.
-The TTCN-3 library modules, which form parts of the present document, are contained in the following gitLab tag:
+The TTCN-3 library, which form parts of the present document, are contained in the following gitLab tag:
+
+Include something else

-[https://git.onem2m.org/TST/ATS/tags/TS-0019-baseline-v2_7_0](https://git.onem2m.org/TST/ATS/tags/TS-0019-baseline-v2_7_0)  
+[https://git.onem2m.org/TST/ATS/tags/TS-0019-baseline-v2_8_0](https://git.onem2m.org/TST/ATS/tags/TS-0019-baseline-v2_8_0)  
 <br/>

 # Annex B (informative):<br/>Bibliography
 - ISO/IEC 9646-6 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification".
 - oneM2M TS-0017: "Implementation Conformance Statement".
 - oneM2M TS-0031: "Feature catalogue".
+- A new element in the list
+- Another element in the list
+- Change by miguel


 # <br/>History