This document contains instructions on how to build, run, and interact with a simulated device. All virtual accessories live in examples/placeholder/linux/apps.
Each accessory needs to be hosted into a subfolder. It will be the name of the application. For example app1 will create a binary named chip-app1.
If some parameters need to be overridden, a CHIPProjectConfig.h file can be placed under an ‘include’ folder into the app folder. For example examples/placeholder/linux/apps/app1/include/CHIPProjectConfig.h
In order to generate specific tests for a given accessory, a examples/placeholder/linux/apps/app1/tests.js file can be added into the application directory. The tests listed there are the one that will be executed once the application has been commissioned.
Simulated Device: simulation of an application in which tests can be added. It is defined by a ZAP config file and tests can be added with a YAML file.
In order to utilize the app against a commissioner or controller, the app will need to be specifically built.
To build the chip-app1 binary completing the following steps:
./scripts/examples/gn_build_example.sh examples/placeholder/linux out/debug/simulated/ chip_tests_zap_config=\"app1\"
In order to utilize the app against a commissioner or controller, the app will need to be specifically built.
To only build the chip-app1 binary completing the following steps:
source scripts/activate.sh gn gen --check --root=examples/placeholder/linux out/simulated --args="chip_tests_zap_config=\"app1\"" ninja -C out/simulated
Now that the building is completed there is a chip-app1 binary created. This binary can be executed on a linux os.
./out/debug/simulated/chip-app1
Now that the building is completed there is a chip-app1 binary created. This binary can be executed on a linux os with test commands.
./out/debug/simulated/chip-app1 --command [TEST NAME]
Now that the building the app and starting it is complete, you will be able to interact with it using chip-tool
Follow the instruction to build chip-tool in the chip-tool readme.
Run this command to commission with whatever is listed on the “SetupQRCode:” line in the log output:
./out/debug/standalone/chip-tool pairing code 0x654321 MT:-24J0AFN00KA0648G00
Most tests will start at this point and now an send cluster commands with chip-tool as follow.
./out/debug/standalone/chip-tool onoff on 0x654321 1 ./out/debug/standalone/chip-tool onoff read on-off 0x654321 1 ./out/debug/standalone/chip-tool onoff write on-time 1 0x654321 1
See chip-tool readme for additional commands.
In order to validate commissioner/controller behavior, tests need to be added to the simulated device test framework. To achieve this, YAML files are created and new code is generated.
YAML test file are located in YAML folder
Test names must follow a strict format dues to CI of test recognition. The format is as follows:
CATEGORY ABBREVIATION]_[SECTION NUMBER]_[SUBSECTION NUMBER]_Simulated.yamlIMPORTANT: The test name must end in Simulated with the capital.Available properties can be found in YAML Test Name
An Additional property is as follows:
| Name | Description |
|---|---|
| wait | The command that is expected to be received on the app from the controller. |
Test_TC_DM_1_3_Simulated is an example of a written test that runs on the simulated device.
Next, it will need to be added to examples/placeholder/linux/apps/app1/tests.js in the following array:
const tests = ["Test_TC_DM_1_3_Simulated"];
Then, the code will be generated using ZAP.
./scripts/tools/zap/generate.py examples/placeholder/linux/apps/app1/config.zap -t examples/placeholder/templates/templates.json -o zzz_generated/placeholder/app1/zap-generated
The following command can be used to generate and compile:
./scripts/examples/gn_build_test_example.sh app1