gecko-sdk-v4.2.2-第1包

# CHIP Test Suites - [CHIP Test Suites](#chip-test-suites) - [Controllers](#controllers) - [Automatic conversion process](#automatic-conversion-process) - [List](#list) - [chip_tests](#list-chiptests) - [Property: test](#property-test) - [Property: config](#property-config) - [Property: {variable_name}](#property-variable_name) - [chip_tests_items](#list-chip_tests_items) - [Property: tests](#property-tests) - [Property: arguments](#property-arguments) - [Property: values](#property-values) - [Property: response](#property-response) - [Property: constraints](#property-constraints) - [chip_tests_item_parameters](#list-chip_tests_item_parameters) - [chip_tests_item_response_parameters](#list-chip_tests_item_response_parameters) - [chip_tests_pics](#list-chip_tests_pics) - [YAML Test Definition](#yaml-test-definition) - [PICS Usage](#pics-usage) - [Examples](#examples) - [YAML Examples](#yaml-examples) - [ZAP Example](#zap-example) - [Index](#index) This directory contains a set of tests describing interactions between nodes, and more specifically between a controller and a controllee. This test set is written in a high level language before being automatically converted into a language understandable by the different controllers. # Controllers There are currently 4 implementations of the CHIP device controller. These different implementations share a common configuration file describing the supported functionalities in terms of clusters, commands and attributes: [controllers-clusters.zap](../../../controller/data_model/controller-clusters.zap) | Controllers | Testing | | ----------- | ------- | | POSIX CLI | y | | Darwin CLI | y | | iOS | y | | Python | n | | Android | n | For more information on the different implementations of the CHIP device controller, see [README.md](../../../controller/README.md) # Automatic conversion process The process of automatic conversion of test files depends on the [ZAP](https://github.com/project-chip/zap) tool. Each of the CHIP device controller implementations uses a dedicated template translating the tests into an appropriate format. | Controllers | Template | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | POSIX CLI | [examples/chip-tool/templates/partials/test_cluster.zapt](../../../../examples/chip-tool/templates/partials/test_cluster.zapt) | | Darwin CLI | [examples/darwin-framework-tool/templates/partials/test_cluster.zapt](../../../../examples/darwin-framework-tool/templates/partials/test_cluster.zapt) | | iOS | [src/darwin/Framework/CHIP/templates/partials/test_cluster.zapt](../../../../src/darwin/Framework/CHIP/templates/partials/test_cluster.zapt) | | Python | | | Android | | These dedicated templates share a common [script](../../zap-templates/common/ClusterTestGeneration.js) which augments the test file with the content of the ZAP database built from the [definition files](../../zap-templates/zcl) of the specification. # Lists This common script exposes the result of the analysis in the form of multiple lists accessible from the dedicated template files. These lists contain elements of which certain properties are directly configurable through the source test file, but also additional properties added during the analysis. ## List: _chip_tests_ **{{chip\_tests}}** takes as parameter a list of test files and returns an iterable list of objects. Each element of the list is an object with the following properties: #### Property: [_test_](./examples/Test_Example.yaml) | Name | Description | Required | | ------ | ----------------------------------------------------------------------------------- | -------- | | name | Name of the test set in human readable format | Yes | | config | Default configuration that is inherited by each of the tests in this set | Yes | | tests | The set of tests. It is possible to iterate over it using **{{chip\_test\_items}}** | Yes | #### Property: [_config_](#basic-yaml-config-example) | Name | Description | Required | | --------------- | ------------------------------------------------------------------------------------------------ | -------- | | cluster | Name of the cluster listed in [Cluster Names](#index) | No | | endpoint | Endpoint Identifier that will be targeted by default by each of the tests in this set | No | | identity | Name of the controller to perform tests with. alpha, beta, and gamma are the only ones supported | No | | {variable_name} | Name of test variable to use within test. | No | ##### Property: [_{variable_name}_](./examples/Config_Variables_Example.yaml) | Name | Description | | --------------- | ------------------------------------------------ | | {variable_name} | Name of test variable to use within test. | | type | Macro type from [ZAP atomics](#zap-atomic-types) | Additionally, the object exhibits the following autogenerated properties: | Name | Description | | ---------- | --------------------------------------------------------- | | filename | Name of the source file from which the test set was built | | totalTests | Total number of tests contained in this set | ## List: _chip_tests_items_ **{{chip\_tests\_items}}** can be used inside a **{{chip\_tests}}** block and iterates over the test set. Each element of the list is an object with the following configurable properties: #### Property: [_tests_](./examples/Test_Example.yaml) | Name | Description | Required | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | | label | Test name | Yes | | disabled | Allows to deactivate a test | No | | command | Name of the command to execute. The command can be any of the commands available for the cluster, or a special command.