1# XTS<a name="EN-US_TOPIC_0000001126156429"></a> 2 3- [Introduction](#section465982318513) 4- [System Types](#section125090457443) 5- [Directory Structure](#section161941989596) 6- [Constraints](#section119744591305) 7- [Usage Guidelines](#section137768191623) 8- [Test Case Development Guidelines](#section3695134065513) 9 - [C-based Test Case Development and Compilation \(for the Mini System\)](#section198193336544) 10 - [C-based Test Case Execution \(for the Mini System\)](#section13820233175418) 11 - [C++-based Test Case Development and Compilation \(for Standard and Small Systems\)](#section3822123311540) 12 - [C++-based Test Case Execution \(for Standard and Small Systems\)](#section128222336544) 13 14 15## Introduction<a name="section465982318513"></a> 16 17The X test suite \(XTS\) subsystem contains a set of OpenHarmony certification test suites, including the currently supported distributed compatibility test suite \(DCTS\). 18 19This subsystem contains the DCTS and **tools** software package. 20 21- The **dcts** directory stores the source code and configuration files of DCTS test cases. The DCTS helps device vendors detect the distributed scenario incompatibility as early as possible and ensures that the software is compatible to OpenHarmony during the entire development process. 22- The **tools** software package stores the test case development framework related to **dcts**. 23 24## System Types<a name="section125090457443"></a> 25 26OpenHarmony supports the following system types: 27 28- Mini system 29 30 A mini system runs on the devices whose memory is greater than or equal to 128 KiB and that are equipped with MCU processors such as ARM Cortex-M and 32-bit RISC-V. This system provides multiple lightweight network protocols and graphics frameworks, and a wide range of read/write components for the IoT bus. Typical products include connection modules, sensors, and wearables for smart home. 31 32- Small system 33 34 A small system runs on the devices whose memory is greater than or equal to 1 MiB and that are equipped with application processors such as ARM Cortex-A. This system provides higher security capabilities, standard graphics frameworks, and video encoding and decoding capabilities. Typical products include smart home IP cameras, electronic cat eyes, and routers, and event data recorders \(EDRs\) for smart travel. 35 36- Standard system 37 38 A standard system runs on the devices whose memory is greater than or equal to 128 MiB and that are equipped with application processors such as ARM Cortex-A. This system provides a complete application framework supporting the enhanced interaction, 3D GPU, hardware composer, diverse components, and rich animations. This system applies to high-end refrigerator displays. 39 40 41## Directory Structure<a name="section161941989596"></a> 42 43``` 44/test/xts 45├── dcts # Test code 46│ └── subsystem # Source code of subsystem test cases for the standard system 47│ └── subsystem_lite # Source code of subsystems test cases for mini and small systems 48│ └── common # Source code of Test cases rely on shared memory for mini and small systems 49│ └── BUILD.gn # Build configuration of test cases for the standard system 50│ └── build_lite 51│ └── BUILD.gn # Build configuration of test cases for mini and small systems 52└── tools # Test tool code 53``` 54 55## Constraints<a name="section119744591305"></a> 56 57Test cases for the mini system must be developed based on C, and those for the small system must be developed based on C++. 58 59## Usage Guidelines<a name="section137768191623"></a> 60 61**Table 1** Test case levels 62 63<a name="table12856113719456"></a> 64<table><thead align="left"><tr id="row88561737114517"><th class="cellrowborder" valign="top" width="33.333333333333336%" id="mcps1.2.4.1.1"><p id="p54711456452"><a name="p54711456452"></a><a name="p54711456452"></a>Level</p> 65</th> 66<th class="cellrowborder" valign="top" width="33.283328332833285%" id="mcps1.2.4.1.2"><p id="p114834544518"><a name="p114834544518"></a><a name="p114834544518"></a>Definition</p> 67</th> 68<th class="cellrowborder" valign="top" width="33.383338333833386%" id="mcps1.2.4.1.3"><p id="p348154574518"><a name="p348154574518"></a><a name="p348154574518"></a>Scope</p> 69</th> 70</tr> 71</thead> 72<tbody><tr id="row78561137134514"><td class="cellrowborder" valign="top" width="33.333333333333336%" headers="mcps1.2.4.1.1 "><p id="p17481345124512"><a name="p17481345124512"></a><a name="p17481345124512"></a>Level0</p> 73</td> 74<td class="cellrowborder" valign="top" width="33.283328332833285%" headers="mcps1.2.4.1.2 "><p id="p1548945204514"><a name="p1548945204514"></a><a name="p1548945204514"></a>Smoke</p> 75</td> 76<td class="cellrowborder" valign="top" width="33.383338333833386%" headers="mcps1.2.4.1.3 "><p id="p174824517456"><a name="p174824517456"></a><a name="p174824517456"></a>Verifies basic functionalities of key features and basic DFX attributes with the most common input. The pass result indicates that the features are runnable.</p> 77</td> 78</tr> 79<tr id="row28563372451"><td class="cellrowborder" valign="top" width="33.333333333333336%" headers="mcps1.2.4.1.1 "><p id="p448445144512"><a name="p448445144512"></a><a name="p448445144512"></a>Level1</p> 80</td> 81<td class="cellrowborder" valign="top" width="33.283328332833285%" headers="mcps1.2.4.1.2 "><p id="p44813452452"><a name="p44813452452"></a><a name="p44813452452"></a>Basic</p> 82</td> 83<td class="cellrowborder" valign="top" width="33.383338333833386%" headers="mcps1.2.4.1.3 "><p id="p648184584514"><a name="p648184584514"></a><a name="p648184584514"></a>Verifies basic functionalities of key features and basic DFX attributes with common input. The pass result indicates that the features are testable.</p> 84</td> 85</tr> 86<tr id="row12856137204514"><td class="cellrowborder" valign="top" width="33.333333333333336%" headers="mcps1.2.4.1.1 "><p id="p164834520453"><a name="p164834520453"></a><a name="p164834520453"></a>Level2</p> 87</td> 88<td class="cellrowborder" valign="top" width="33.283328332833285%" headers="mcps1.2.4.1.2 "><p id="p148245184511"><a name="p148245184511"></a><a name="p148245184511"></a>Major</p> 89</td> 90<td class="cellrowborder" valign="top" width="33.383338333833386%" headers="mcps1.2.4.1.3 "><p id="p348945124510"><a name="p348945124510"></a><a name="p348945124510"></a>Verifies basic functionalities of key features and basic DFX attributes with common input and errors. The pass result indicates that the features are functional and ready for beta testing.</p> 91</td> 92</tr> 93<tr id="row48571137204514"><td class="cellrowborder" valign="top" width="33.333333333333336%" headers="mcps1.2.4.1.1 "><p id="p7481545184513"><a name="p7481545184513"></a><a name="p7481545184513"></a>Level3</p> 94</td> 95<td class="cellrowborder" valign="top" width="33.283328332833285%" headers="mcps1.2.4.1.2 "><p id="p1748184514455"><a name="p1748184514455"></a><a name="p1748184514455"></a>Regular</p> 96</td> 97<td class="cellrowborder" valign="top" width="33.383338333833386%" headers="mcps1.2.4.1.3 "><p id="p8481245104519"><a name="p8481245104519"></a><a name="p8481245104519"></a>Verifies functionalities of all key features, and all DFX attributes with common and uncommon input combinations or normal and abnormal preset conditions.</p> 98</td> 99</tr> 100<tr id="row14857133712451"><td class="cellrowborder" valign="top" width="33.333333333333336%" headers="mcps1.2.4.1.1 "><p id="p1248144515456"><a name="p1248144515456"></a><a name="p1248144515456"></a>Level4</p> 101</td> 102<td class="cellrowborder" valign="top" width="33.283328332833285%" headers="mcps1.2.4.1.2 "><p id="p94804514519"><a name="p94804514519"></a><a name="p94804514519"></a>Rare</p> 103</td> 104<td class="cellrowborder" valign="top" width="33.383338333833386%" headers="mcps1.2.4.1.3 "><p id="p1248445164516"><a name="p1248445164516"></a><a name="p1248445164516"></a>Verifies functionalities of key features under extremely abnormal presets and uncommon input combinations.</p> 105</td> 106</tr> 107</tbody> 108</table> 109 110**Table 2** Test case granularities 111 112<a name="table1690733521014"></a> 113<table><thead align="left"><tr id="row9907143516105"><th class="cellrowborder" valign="top" width="19.591959195919593%" id="mcps1.2.4.1.1"><p id="p1141312416102"><a name="p1141312416102"></a><a name="p1141312416102"></a>Test Scale</p> 114</th> 115<th class="cellrowborder" valign="top" width="35.17351735173517%" id="mcps1.2.4.1.2"><p id="p34131416109"><a name="p34131416109"></a><a name="p34131416109"></a>Test Objects</p> 116</th> 117<th class="cellrowborder" valign="top" width="45.23452345234523%" id="mcps1.2.4.1.3"><p id="p12413141171010"><a name="p12413141171010"></a><a name="p12413141171010"></a>Test Environment</p> 118</th> 119</tr> 120</thead> 121<tbody><tr id="row2907335181017"><td class="cellrowborder" valign="top" width="19.591959195919593%" headers="mcps1.2.4.1.1 "><p id="p6414134117109"><a name="p6414134117109"></a><a name="p6414134117109"></a>LargeTest</p> 122</td> 123<td class="cellrowborder" valign="top" width="35.17351735173517%" headers="mcps1.2.4.1.2 "><p id="p20414104113101"><a name="p20414104113101"></a><a name="p20414104113101"></a>Service functionalities, all-scenario features, and mechanical power environment (MPE) and scenario-level DFX</p> 124</td> 125<td class="cellrowborder" valign="top" width="45.23452345234523%" headers="mcps1.2.4.1.3 "><p id="p5414841121013"><a name="p5414841121013"></a><a name="p5414841121013"></a>Devices close to real devices</p> 126</td> 127</tr> 128<tr id="row10907635131015"><td class="cellrowborder" valign="top" width="19.591959195919593%" headers="mcps1.2.4.1.1 "><p id="p19414134117104"><a name="p19414134117104"></a><a name="p19414134117104"></a>MediumTest</p> 129</td> 130<td class="cellrowborder" valign="top" width="35.17351735173517%" headers="mcps1.2.4.1.2 "><p id="p114141241141018"><a name="p114141241141018"></a><a name="p114141241141018"></a>Modules, subsystem functionalities after module integration, and DFX</p> 131</td> 132<td class="cellrowborder" valign="top" width="45.23452345234523%" headers="mcps1.2.4.1.3 "><p id="p14414941111015"><a name="p14414941111015"></a><a name="p14414941111015"></a>Single device that is actually used. You can perform message simulation, but do not mock functions.</p> 133</td> 134</tr> 135<tr id="row1990713353100"><td class="cellrowborder" valign="top" width="19.591959195919593%" headers="mcps1.2.4.1.1 "><p id="p641414110109"><a name="p641414110109"></a><a name="p641414110109"></a>SmallTest</p> 136</td> 137<td class="cellrowborder" valign="top" width="35.17351735173517%" headers="mcps1.2.4.1.2 "><p id="p54141541181018"><a name="p54141541181018"></a><a name="p54141541181018"></a>Modules, classes, and functions</p> 138</td> 139<td class="cellrowborder" valign="top" width="45.23452345234523%" headers="mcps1.2.4.1.3 "><p id="p1841494131013"><a name="p1841494131013"></a><a name="p1841494131013"></a>Local PC. Use a large number of mocks to replace dependencies with other modules.</p> 140</td> 141</tr> 142</tbody> 143</table> 144 145**Table 3** Test types 146 147<a name="table18811230124619"></a> 148<table><thead align="left"><tr id="row48163019466"><th class="cellrowborder" valign="top" width="19.040000000000003%" id="mcps1.2.3.1.1"><p id="p1791784418465"><a name="p1791784418465"></a><a name="p1791784418465"></a>Type</p> 149</th> 150<th class="cellrowborder" valign="top" width="80.96%" id="mcps1.2.3.1.2"><p id="p2917164444614"><a name="p2917164444614"></a><a name="p2917164444614"></a>Definition</p> 151</th> 152</tr> 153</thead> 154<tbody><tr id="row682630104615"><td class="cellrowborder" valign="top" width="19.040000000000003%" headers="mcps1.2.3.1.1 "><p id="p1091784414469"><a name="p1091784414469"></a><a name="p1091784414469"></a>Function</p> 155</td> 156<td class="cellrowborder" valign="top" width="80.96%" headers="mcps1.2.3.1.2 "><p id="p16917344104618"><a name="p16917344104618"></a><a name="p16917344104618"></a>Tests the correctness of both service and platform functionalities provided by the tested object for end users or developers.</p> 157</td> 158</tr> 159<tr id="row1821930154611"><td class="cellrowborder" valign="top" width="19.040000000000003%" headers="mcps1.2.3.1.1 "><p id="p591714474612"><a name="p591714474612"></a><a name="p591714474612"></a>Performance</p> 160</td> 161<td class="cellrowborder" valign="top" width="80.96%" headers="mcps1.2.3.1.2 "><p id="p15917154410463"><a name="p15917154410463"></a><a name="p15917154410463"></a>Tests the processing capability of the tested object under specific preset conditions and load models. The processing capability is measured by the service volume that can be processed in a unit time, for example, call per second, frame per second, or event processing volume per second.</p> 162</td> 163</tr> 164<tr id="row13821030104616"><td class="cellrowborder" valign="top" width="19.040000000000003%" headers="mcps1.2.3.1.1 "><p id="p691711440467"><a name="p691711440467"></a><a name="p691711440467"></a>Power</p> 165</td> 166<td class="cellrowborder" valign="top" width="80.96%" headers="mcps1.2.3.1.2 "><p id="p159171544104616"><a name="p159171544104616"></a><a name="p159171544104616"></a>Tests the power consumption of the tested object in a certain period of time under specific preset conditions and load models.</p> 167</td> 168</tr> 169<tr id="row6821330114618"><td class="cellrowborder" valign="top" width="19.040000000000003%" headers="mcps1.2.3.1.1 "><p id="p13917164454612"><a name="p13917164454612"></a><a name="p13917164454612"></a>Reliability</p> 170</td> 171<td class="cellrowborder" valign="top" width="80.96%" headers="mcps1.2.3.1.2 "><p id="p11917194416465"><a name="p11917194416465"></a><a name="p11917194416465"></a>Tests the service performance of the tested object under common and uncommon input conditions, or specified service volume pressure and long-term continuous running pressure. The test covers stability, pressure handling, fault injection, and Monkey test times.</p> 172</td> 173</tr> 174<tr id="row11821930184612"><td class="cellrowborder" valign="top" width="19.040000000000003%" headers="mcps1.2.3.1.1 "><p id="p1691774474618"><a name="p1691774474618"></a><a name="p1691774474618"></a>Security</p> 175</td> 176<td class="cellrowborder" valign="top" width="80.96%" headers="mcps1.2.3.1.2 "><a name="ul112421652121513"></a><a name="ul112421652121513"></a><ul id="ul112421652121513"><li>Tests the capability of defending against security threats, including but not limited to unauthorized access, use, disclosure, damage, modification, and destruction, to ensure information confidentiality, integrity, and availability.</li><li>Tests the privacy protection capability to ensure that the collection, use, retention, disclosure, and disposal of users' private data comply with laws and regulations.</li><li>Tests the compliance with various security specifications, such as security design, security requirements, and security certification of the Ministry of Industry and Information Technology (MIIT).</li></ul> 177</td> 178</tr> 179<tr id="row16825307467"><td class="cellrowborder" valign="top" width="19.040000000000003%" headers="mcps1.2.3.1.1 "><p id="p129188444462"><a name="p129188444462"></a><a name="p129188444462"></a>Global</p> 180</td> 181<td class="cellrowborder" valign="top" width="80.96%" headers="mcps1.2.3.1.2 "><p id="p179186444465"><a name="p179186444465"></a><a name="p179186444465"></a>Tests the internationalized data and localization capabilities of the tested object, including multi-language display, various input/output habits, time formats, and regional features, such as currency, time, and culture taboos.</p> 182</td> 183</tr> 184<tr id="row08211308464"><td class="cellrowborder" valign="top" width="19.040000000000003%" headers="mcps1.2.3.1.1 "><p id="p191814447465"><a name="p191814447465"></a><a name="p191814447465"></a>Compatibility</p> 185</td> 186<td class="cellrowborder" valign="top" width="80.96%" headers="mcps1.2.3.1.2 "><a name="ul186961827111612"></a><a name="ul186961827111612"></a><ul id="ul186961827111612"><li>Tests backward compatibility of an application with its own data, the forward and backward compatibility with the system, and the compatibility with different user data, such as audio file content of the player and smart SMS messages.</li><li>Tests system backward compatibility with its own data and the compatibility of common applications in the ecosystem.</li><li>Tests software compatibility with related hardware.</li></ul> 187</td> 188</tr> 189<tr id="row1782730124618"><td class="cellrowborder" valign="top" width="19.040000000000003%" headers="mcps1.2.3.1.1 "><p id="p13918144134614"><a name="p13918144134614"></a><a name="p13918144134614"></a>User</p> 190</td> 191<td class="cellrowborder" valign="top" width="80.96%" headers="mcps1.2.3.1.2 "><p id="p1291844494611"><a name="p1291844494611"></a><a name="p1291844494611"></a>Tests user experience of the object in real user scenarios. All conclusions and comments should come from the users, which are all subjective evaluation in this case.</p> 192</td> 193</tr> 194<tr id="row58243024617"><td class="cellrowborder" valign="top" width="19.040000000000003%" headers="mcps1.2.3.1.1 "><p id="p1291884474614"><a name="p1291884474614"></a><a name="p1291884474614"></a>Standard</p> 195</td> 196<td class="cellrowborder" valign="top" width="80.96%" headers="mcps1.2.3.1.2 "><p id="p0918124424614"><a name="p0918124424614"></a><a name="p0918124424614"></a>Tests the compliance with industry and company-specific standards, protocols, and specifications. The standards here do not include any security standards that should be classified into the security test.</p> 197</td> 198</tr> 199<tr id="row382830124619"><td class="cellrowborder" valign="top" width="19.040000000000003%" headers="mcps1.2.3.1.1 "><p id="p119181044164619"><a name="p119181044164619"></a><a name="p119181044164619"></a>Safety</p> 200</td> 201<td class="cellrowborder" valign="top" width="80.96%" headers="mcps1.2.3.1.2 "><p id="p1291818443468"><a name="p1291818443468"></a><a name="p1291818443468"></a>Tests the safety property of the tested object to avoid possible hazards to personal safety, health, and the object itself.</p> 202</td> 203</tr> 204<tr id="row1083153014465"><td class="cellrowborder" valign="top" width="19.040000000000003%" headers="mcps1.2.3.1.1 "><p id="p39187441469"><a name="p39187441469"></a><a name="p39187441469"></a>Resilience</p> 205</td> 206<td class="cellrowborder" valign="top" width="80.96%" headers="mcps1.2.3.1.2 "><p id="p891815444462"><a name="p891815444462"></a><a name="p891815444462"></a>Tests the resilience property of the tested object to ensure that it can withstand and maintain the defined running status (including downgrading) when being attacked, and recover from and adapt defense to the attacks to approach mission assurance.</p> 207</td> 208</tr> 209</tbody> 210</table> 211 212## Test Case Development Guidelines<a name="section3695134065513"></a> 213 214You should select the appropriate programming language and your target test framework to develop test cases. 215 216**Table 4** Test frameworks and test case languages for different systems 217 218<a name="table4418343171415"></a> 219<table><thead align="left"><tr id="row34183435145"><th class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.2.4.1.1"><p id="p941874311148"><a name="p941874311148"></a><a name="p941874311148"></a>System</p> 220</th> 221<th class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.2.4.1.2"><p id="p1841804341413"><a name="p1841804341413"></a><a name="p1841804341413"></a>Test Framework</p> 222</th> 223<th class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.2.4.1.3"><p id="p2418104311148"><a name="p2418104311148"></a><a name="p2418104311148"></a>Language</p> 224</th> 225</tr> 226</thead> 227<tbody><tr id="row8419164319148"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.2.4.1.1 "><p id="p7419194312143"><a name="p7419194312143"></a><a name="p7419194312143"></a>Mini</p> 228</td> 229<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.2.4.1.2 "><p id="p10419124312145"><a name="p10419124312145"></a><a name="p10419124312145"></a>HCTest</p> 230</td> 231<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.2.4.1.3 "><p id="p11419643191410"><a name="p11419643191410"></a><a name="p11419643191410"></a>C</p> 232</td> 233</tr> 234<tr id="row141915438147"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.2.4.1.1 "><p id="p441911436141"><a name="p441911436141"></a><a name="p441911436141"></a>Small</p> 235</td> 236<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.2.4.1.2 "><p id="p541916432142"><a name="p541916432142"></a><a name="p541916432142"></a>HCPPTest</p> 237</td> 238<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.2.4.1.3 "><p id="p54191643131416"><a name="p54191643131416"></a><a name="p54191643131416"></a>C++</p> 239</td> 240</tr> 241<tr id="row4419134341417"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.2.4.1.1 "><p id="p341964313143"><a name="p341964313143"></a><a name="p341964313143"></a>Standard</p> 242</td> 243<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.2.4.1.2 "><p id="p10419443171416"><a name="p10419443171416"></a><a name="p10419443171416"></a>HJSUnit and HCPPTest</p> 244</td> 245<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.2.4.1.3 "><p id="p9419143181414"><a name="p9419143181414"></a><a name="p9419143181414"></a>JavaScript and C++</p> 246</td> 247</tr> 248</tbody> 249</table> 250 251### C-based Test Case Development and Compilation \(for the Mini System\)<a name="section198193336544"></a> 252 253**Developing test cases for the mini system** 254 255The HCTest framework is used to support test cases developed with the C language. HCTest is enhanced and adapted based on the open-source test framework Unity. 256 2571. Access the **test/xts/dcts** repository where the test cases will be stored. 258 259 ``` 260 ├── dcts 261 │ └──subsystem_lite 262 │ │ └── module_hal 263 │ │ │ └── BUILD.gn 264 │ │ │ └── src 265 │ └──build_lite 266 │ │ └── BUILD.gn 267 ``` 268 2692. Write the test case in the **src** directory. 270 271 1 Import the test framework header file. 272 273 ``` 274 #include "hctest.h" 275 ``` 276 277 2. Use the **LITE\_TEST\_SUIT** macro to define names of the subsystem, module, and test suite. 278 279 ``` 280 /** 281 * @brief Registers a test suite named IntTestSuite. 282 * @param test Subsystem name 283 * @param example Module name 284 * @param IntTestSuite Test suite name 285 */ 286 LITE_TEST_SUIT(test, example, IntTestSuite); 287 ``` 288 289 3. Define Setup and TearDown. 290 291 Format: Test suite name+Setup, Test suite name+TearDown. 292 293 The Setup and TearDown functions must exist, but function bodies can be empty. 294 295 4. Use the **LITE\_TEST\_CASE** macro to write the test case. 296 297 Three parameters are involved: test suite name, test case name, and test case properties \(including type, granularity, and level\). 298 299 ``` 300 LITE_TEST_CASE(IntTestSuite, TestCase001, Function | MediumTest | Level1) 301 { 302 // Do something 303 }; 304 ``` 305 306 5. Use the **RUN\_TEST\_SUITE** macro to register the test suite. 307 308 ``` 309 RUN_TEST_SUITE(IntTestSuite); 310 ``` 311 3123. Create the configuration file \(**BUILD.gn**\) of the test module. 313 314 Create a **BUILD.gn** \(example\) build file in each test module directory. Specify the name of the built static library and its dependent header file and library in the build file. The format is as follows: 315 316 ``` 317 import("//test/xts/tools/lite/build/suite_lite.gni") 318 hctest_suite("DctsDemoTest") { 319 suite_name = "dcts" 320 sources = [ 321 "src/test_demo.c", 322 ] 323 include_dirs = [ ] 324 cflags = [ "-Wno-error" ] 325 } 326 ``` 327 3284. Add build options to the **BUILD.gn** file in the **dcts** directory. 329 330 You need to add the test module to the **test/xts/dcts/build\_lite/BUILD.gn** script in the **dcts** directory. 331 332 ``` 333 lite_component("dcts") { 334 ... 335 if(board_name == "liteos_m") { 336 features += [ 337 ... 338 "//xts/dcts/subsystem_lite/module_hal:DctsDemoTest" 339 ] 340 } 341 } 342 ``` 343 3445. Run build commands. 345 346 Test suites are built along with version build. The DCTS is built together with the debug version. 347 348 > **NOTE:** 349 >The DCTS build middleware is a static library, which will be linked to the image. 350 351 352### C-based Test Case Execution \(for the Mini System\)<a name="section13820233175418"></a> 353 354**Executing test cases for the mini system** 355 356Burn the image into the development board. 357 358**Executing the test** 359 3601. Use a serial port tool to log in to the development board and save information about the serial port. 3612. Restart the device and view serial port logs. 362 363**Analyzing the test result** 364 365View the serial port logs, whose format is as follows: 366 367The log for each test suite starts with **Start to run test suite:** and ends with **xx Tests xx Failures xx Ignored**. 368 369### C++-based Test Case Development and Compilation \(for Standard and Small Systems\)<a name="section3822123311540"></a> 370 371**Developing test cases for small-system devices** \(For examples of the standard system, go to the **global/i18n\_standard directory**.\) 372 373The HCPPTest framework is enhanced and adapted based on the open-source framework Googletest. 374 3751. Access the **test/xts/dcts** repository where the test cases will be stored. 376 377 ``` 378 ├── dcts 379 │ └──subsystem_lite 380 │ │ └── module_posix 381 │ │ │ └── BUILD.gn 382 │ │ │ └── src 383 │ └──build_lite 384 │ │ └── BUILD.gn 385 ``` 386 3872. Write the test case in the **src** directory. 388 389 1. Import the test framework header file. 390 391 The following statement includes **gtest.h**. 392 393 ``` 394 #include "gtest/gtest.h" 395 ``` 396 397 2. Define Setup and TearDown. 398 399 ``` 400 using namespace std; 401 using namespace testing::ext; 402 class TestSuite: public testing::Test { 403 protected: 404 // Preset action of the test suite, which is executed before the first test case 405 static void SetUpTestCase(void){ 406 } 407 // Test suite cleanup action, which is executed after the last test case 408 static void TearDownTestCase(void){ 409 } 410 // Preset action of the test case 411 virtual void SetUp() 412 { 413 } 414 // Cleanup action of the test case 415 virtual void TearDown() 416 { 417 } 418 }; 419 ``` 420 421 3. Use the **HWTEST** or **HWTEST\_F** macro to write the test case. 422 423 **HWTEST**: definition of common test cases, including the test suite name, test case name, and case annotation. 424 425 **HWTEST\_F**: definition of SetUp and TearDown test cases, including the test suite name, test case name, and case annotation. 426 427 Three parameters are involved: test suite name, test case name, and test case properties \(including type, granularity, and level\). 428 429 ``` 430 HWTEST_F(TestSuite, TestCase_0001, Function | MediumTest | Level1) { 431 // Do something 432 } 433 ``` 434 4353. Create a configuration file \(**BUILD.gn**\) of the test module. 436 437 Create a **BUILD.gn** build file in each test module directory. Specify the name of the built static library and its dependent header file and library in the build file. Each test module is independently built into a **.bin** executable file, which can be directly pushed to the development board for testing. 438 439 Example: 440 441 ``` 442 import("//test/xts/tools/lite/build/suite_lite.gni") 443 hcpptest_suite("DctsDemoTest") { 444 suite_name = "dcts" 445 sources = [ 446 "src/TestDemo.cpp" 447 ] 448 449 include_dirs = [ 450 "src", 451 ... 452 ] 453 deps = [ 454 ... 455 ] 456 cflags = [ "-Wno-error" ] 457 } 458 ``` 459 4604. Add build options to the **BUILD.gn** file in the **dcts** directory. 461 462 Add the test module to the **test/xts/dcts/build\_lite/BUILD.gn** script in the **dcts** directory. 463 464 ``` 465 lite_component("dcts") { 466 ... 467 else if(board_name == "liteos_a") { 468 features += [ 469 ... 470 "//xts/dcts/subsystem_lite/module_posix:DctsDemoTest" 471 ] 472 } 473 } 474 ``` 475 4765. Run build commands. 477 478 Test suites are built along with the version build. The DCTS is built together with the debug version. 479 480 > **NOTE:** 481 >The DCTS for the small system is independently built to an executable file \(.bin\) and archived in the **suites\\dcts** directory of the build result. 482 483 484### C++-based Test Case Execution \(for Standard and Small Systems\)<a name="section128222336544"></a> 485 486**Executing test cases for the small system** 487 488Currently, test cases are shared by the NFS and mounted to the development board for execution. 489 490**Setting up the environment** 491 4921. Use a network cable or wireless network to connect the development board to your PC. 4932. Configure the IP address, subnet mask, and gateway for the development board. Ensure that the development board and the PC are in the same network segment. 4943. Install and register the NFS server on the PC and start the NFS service. 4954. Run the **mount** command for the development board to ensure that the development board can access NFS shared files on the PC. 496 497 Format: **mount** _NFS server IP address_**:/**_NFS shared directory_ **/**_development board directory_ **nfs** 498 499 Example: 500 501 ``` 502 mount 192.168.1.10:/nfs /nfs nfs 503 ``` 504 505 506**Executing test cases** 507 508Execute **DctsDemoTest.bin** to trigger test case execution, and analyze serial port logs generated after the execution is complete. 509
