@@ -11,11 +11,6 @@ If some parameters need to be overridden, a `CHIPProjectConfig.h` file can be
11
11
placed under an ‘include’ folder into the app folder. For example
12
12
` examples/placeholder/linux/apps/app1/include/CHIPProjectConfig.h `
13
13
14
- In order to generate specific tests for a given accessory, a
15
- [ examples/placeholder/linux/apps/app1/tests.js] ( ../../examples/placeholder/linux/apps/app1/tests.js )
16
- file can be added into the application directory. The tests listed there are the
17
- one that will be executed once the application has been commissioned.
18
-
19
14
Simulated Device: simulation of an application in which tests can be added. It
20
15
is defined by a ZAP config file and tests can be added with a
21
16
[ YAML file] ( ../../src/app/tests/suites/certification/Test_TC_DM_1_3_Simulated.yaml ) .
@@ -66,7 +61,7 @@ Now that the building is completed there is a `chip-app1` binary created. This
66
61
binary can be executed on a linux os with test commands.
67
62
68
63
```
69
- ./out/debug/simulated/chip-app1 --command [ TEST NAME]
64
+ ./scripts/tests/yaml/runner.py [ TEST NAME] app1
70
65
```
71
66
72
67
## Interacting with the simulated app
@@ -99,8 +94,7 @@ interact with it using chip-tool
99
94
## Adding simulated Tests via YAML
100
95
101
96
In order to validate commissioner/controller behavior, tests need to be added to
102
- the simulated device test framework. To achieve this, YAML files are created and
103
- new code is generated.
97
+ the simulated device test framework. To achieve this, YAML files are created.
104
98
105
99
1. YAML test file are located in
106
100
[YAML folder](../../src/app/tests/suites/certification/)
@@ -124,26 +118,3 @@ new code is generated.
124
118
125
119
5. [Test_TC_DM_1_3_Simulated](../../src/app/tests/suites/certification/Test_TC_DM_1_3_Simulated.yaml)
126
120
is an example of a written test that runs on the simulated device.
127
-
128
- 6. Next, it will need to be added to
129
- [examples/placeholder/linux/apps/app1/tests.js](../../examples/placeholder/linux/apps/app1/tests.js)
130
- in the following array:
131
-
132
- ```javascript
133
- const tests = ["Test_TC_DM_1_3_Simulated"];
134
- ```
135
-
136
- 7. Then, the code will be generated using ZAP.
137
-
138
- ```
139
- ./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
140
- ```
141
-
142
- The following command can be used to generate and compile:
143
-
144
- ```
145
- ./scripts/examples/gn_build_test_example.sh app1
146
- ```
147
-
148
- 8) When submitting code for review, create 2 commits. One for YAML changes and
149
- second for generated code.
0 commit comments