Skip to content

Commit bf9c86a

Browse files
authoredFeb 12, 2024
[placeholder] Remove tests generated with zap (#32038)
* [placeholder] Remove examples/placeholder tests codegen * Remove src/app/tests/suites/pics * Remove src/app/tests/suites/include * Remove src/app/tests/suites/templates * Remove src/app/tests/suites/commands/[delay|discovery|log|system] * Remove examples/darwin-framework-tool/commands/tests/TestCommandBridge.h
1 parent 9a7a77c commit bf9c86a

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

49 files changed

+2
-8955
lines changed
 

‎docs/guides/simulated_device_linux.md

+2-31
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,6 @@ If some parameters need to be overridden, a `CHIPProjectConfig.h` file can be
1111
placed under an ‘include’ folder into the app folder. For example
1212
`examples/placeholder/linux/apps/app1/include/CHIPProjectConfig.h`
1313

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-
1914
Simulated Device: simulation of an application in which tests can be added. It
2015
is defined by a ZAP config file and tests can be added with a
2116
[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
6661
binary can be executed on a linux os with test commands.
6762
6863
```
69-
./out/debug/simulated/chip-app1 --command [TEST NAME]
64+
./scripts/tests/yaml/runner.py [TEST NAME] app1
7065
```
7166
7267
## Interacting with the simulated app
@@ -99,8 +94,7 @@ interact with it using chip-tool
9994
## Adding simulated Tests via YAML
10095
10196
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.
10498
10599
1. YAML test file are located in
106100
[YAML folder](../../src/app/tests/suites/certification/)
@@ -124,26 +118,3 @@ new code is generated.
124118
125119
5. [Test_TC_DM_1_3_Simulated](../../src/app/tests/suites/certification/Test_TC_DM_1_3_Simulated.yaml)
126120
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

Comments
 (0)