AliOS Things Porting Test Guide

EN| 中文

Content

• 1. Overview
• 2. Ways of using and customizing test suite
• 3. List of supported tests
• 4. Q&A

---

1.Overview

AliOS Things provides a set of basic test cases for system transplanting quality verification. Users can customize and adjust test suite based on their transplanted components.

This article will talk about the way of using and customizing AliOS test suite, list of test cases that have been supported, and how to add new test case.

2. Ways of using and customizing test suite

AliOS Things has preset a test application named "YTS" in the "example" directory.

2.1 How to use the test suite :

• Generate test application through $ aos make yts@board_name If specified test component is needed, you can set the "test" parameter: $ aos make yts@board_name test=component_name。
• Burn the compiled binary file into the target board.
• When reset of target board is started, you can input "yts_run" command in the CLI environment to execute the specific test case:

2.2 How to customize the test suite :

• Mark the test components list in "board_name.mk" file corresponding to the target board by variable "TEST_COMPONENTS" . (board_name.mk is generally located in the board directory)

  Take STM32's b_l475e (b_l475e.mk) as an example:

  

• The test component is specified by compiling the parameter "test" of the command:$ aos make yts@board_name test=component_name

3. list of supported tests

Name	Function	Description
basic	test_basic	basic list structure test case(slist, dlist)
cjson	test_cjson	cjson component test case
digest_algorithm	test_digest_algorithm	digest algorithm component test case
hashtable	test_hashtable	hashtable component test case
api	test_api	aos api test case
rhino	test_rhino	rhino kernel test case
vcall	test_vcall	vcall component test case (only for mico/b_l475e board)
vfs	test_vfs	vfs component test case
yloop	test_yloop	yloop component test case
kv	test_kv	key-value store component test case
fatfs	test_fatfs	fatfs file system component test case
deviceIO	test_deviceIO	device IO component test case (only for linuxhost)
wifi_hal	test_hal	wifi HAL & timer HAL interface test case
netmgr	test_netmgr	netmgr component test case
alink	test_alink	alink component test case
mqtt	test_mqtt	mqtt component test case
coap	test_coap	coap component test case
fota	test_fota	fota component test case
alicrypto	test_alicrypto	alicrypto component test case
tfs	test_tfs	tfs component test case
tls	test_tls	mbedtls component test case

4. Q&A

• Q: I can't input command through CLI after target board burns the yts program .

  A: This is because CLI module hasn't been compiled into the application. Please make sure the mk file of your board has declared the dependency on cli, or you should add the dependency in yts.mk. COMPONENTS += cli。

• Q: How can I just test Rhino kernel?
  A: There are mainly two measures: 1. compile a test application that only tests Rhino throughaos make yts@board_name test=rhino；2. set the variable “TEST_COMPONENTS” in board_name.mk TEST_COMPONENTS := rhino.