Matter Version |
TH Version |
TH image location |
Supporting Documentation |
SDK commit |
Comments |
Matter 1.0 |
v2.6 |
96c9357 |
|||
Matter 1.1 |
v2.8.1 |
5a21d17 |
|||
Matter 1.2 |
TH-Fall2023 |
19771ed |
|||
Matter 1.3 |
v2.10+spring2024 |
N/A |
11f94c3 |
To install, use the tag "v2.10+spring2024" in the instructions of TH Installation on Raspberry Pi |
|
Matter 1.3 |
v2.10.1+spring2024 |
N/A |
fb2c0e5 |
To install, use the tag "v2.10.1+spring2024" in the instructions of TH Installation on Raspberry Pi |
|
Matter 1.4 |
v2.11-beta3.1+fall2024 |
N/A |
17b1a38 |
To install, use the tag "v2.11-beta3.1+fall2024" in the instructions of TH Installation on Raspberry Pi |
Revision |
Date |
Author |
Description |
1 |
11-Jan-2022 |
[GRL]Suraj Seenivasan |
* Initial version of the user manual used for V1.0. |
2 |
22-Aug-2022 |
[GRL]Suraj Seenivasan |
* Updated the steps required to run the Python script inside docker: Input given by Tennessee Carmel-Veilleux. |
3 |
06-Feb-2023 |
[GRL]Suraj Seenivasan |
* Added instructions to update the existing image and personal access token: How to execute simulated test cases. |
4 |
09-Feb-2023 |
[GRL]Suma |
* Structuring the user manual. |
5 |
24-Feb-2023 |
[SiLabs]Yinyi Hu |
* Instruction to Flash SiLabs RCP. |
6 |
01-Mar-2023 |
[GRL]Suraj Seenivasan |
* Instructions to flash nRF52840 Dongle and nRF52840 DK. |
7 |
16-Mar-2023 |
[Apple]Fábio Wladimir Monteiro Maia |
* Added TH layout explanation. |
8 |
12-Jun-2023 |
[Apple]Carolina Lopes |
* Added instructions to install TH without a Raspberry Pi. |
9 |
06-Sep-2023 |
[Apple]Antonio Melo Jr. |
* Moved the table of contents to a further page. |
10 |
25-Oct-2023 |
[Apple]Hilton Lima |
* Added SDK commit column to Test-Harness Links table. |
11 |
26-Oct-2023 |
[Apple]Carolina Lopes |
* Updated some links and images. |
12 |
06-Dec-2023 |
[Apple]Hilton Lima |
* Added Custom Yaml test section. |
13 |
07-Dec-2023 |
[Apple]Carolina Lopes |
* Updated instructions on how to install TH without a Raspberry Pi. |
14 |
14-Dec-2023 |
[Apple]Hilton Lima |
* Updated SDK Python Test section. |
15 |
20-Dec-2023 |
[Apple]Antonio Melo Jr. |
* Updated Test Harness links related to release of Spring 2024. |
16 |
04-Jan-2024 |
[Apple]Antonio Melo Jr. |
* Updated Test Harness Release location link to the new Drive folder. |
17 |
04-Jan-2024 |
[Apple]Romulo Quidute |
* Renamed Custom Yaml test section to Customized Test Scripts and also added Custom Python test information. |
18 |
05-Jan-2024 |
[Apple]Carolina Lopes |
* Added information about the SDK Python Test suites. |
19 |
30-Jan-2024 |
[Apple]Romulo Quidute |
* Updated some referenced links. |
20 |
07-Feb-2024 |
[Apple]Hilton Lima |
* Added 'Common Test Failures' section for SDK tests. |
21 |
07-Feb-2024 |
[Apple]Carolina Lopes |
* Added 'Bringing up the Matter Python REPL' section. |
22 |
15-Feb-2024 |
[Apple]Hilton Lima |
* Updated 'TH Installation on Raspberry Pi' section. |
23 |
26-Feb-2024 |
[Apple]Carolina Lopes |
* Added volume mapping for data model XML files on docker run commands for SDK containter. |
24 |
27-Feb-2024 |
[Apple]Carolina Lopes |
* Updated mapping in docker run command for SDK container. |
25 |
27-Mar-2024 |
[Apple]Hilton Lima |
* Update nRF52840 firmware download link. |
26 |
01-Apr-2024 |
[Apple]Hilton Lima |
* Update download link to Flash SiLabs RCP. |
27 |
01-Apr-2024 |
[Apple]Romulo Quidute |
* Update OTBR scripts location. |
28 |
17-Apr-2024 |
[Apple]Hilton Lima |
* Updated Test Harness links related to final release of Spring 2024. |
29 |
18-Apr-2024 |
[Apple]Hilton Lima |
* Update section 'TH installation without a Raspberry Pi'. |
30 |
30-Apr-2024 |
[Apple]Hilton Lima |
* Update location for update scripts. |
31 |
10-Jun-2024 |
[Apple]Hilton Lima |
* Updated Test Harness links. |
32 |
17-Jun-2024 |
[Google] Tennessee Carmel-Veilleux |
* Added an example of an external operational dataset. |
33 |
01-Aug-2024 |
[Apple] Carolina Lopes |
* Added information about Certification Mode. |
34 |
02-Aug-2024 |
[Apple] Antonio Melo Jr. |
* Update the Ubuntu mentions to the current supported version. |
35 |
06-Aug-2024 |
[Apple] Antonio Melo Jr. |
* Add the TH release version to the front page of the document. |
36 |
09-Aug-2024 |
[Apple] Antonio Melo Jr. |
* Adding the new cleanup procedure to the troubleshooting of TH Installation section. |
37 |
13-Aug-2024 |
[Apple] Hilton Lima |
* Remove old references of TH image (obsolete). |
38 |
30-Aug-2024 |
[Apple] Hilton Lima |
* Replace images by text examples in 'Project Configuration' section. |
39 |
04-Sep-2024 |
[Apple] Hilton Lima |
* Moved PIXIT section. |
- 1. Introduction
- 2. References
- 3. Test-Harness (TH) Design
- 4. Getting Started with Matter Test-Harness (TH)
- 5. Bringing Up of Matter Node (DUT) for Certification Testing
- 6. Bringing up the Matter Python REPL
- 7. OT Border Router (OTBR) Setup
- 7.1. Instructions to Flash the Firmware NRF52840 RCPDongle
- 7.2. Nrfconnect Sample APPs Firmwares to Flash on the NRF52840DK Kit
- 7.3. Instructions to Flash SiLabs RCP
- 7.4. Forming Thread Network and Generating Dataset for Thread Pairing
- 7.5. Troubleshooting: Boarder Router Container failure to initialize
- 8. Test Configuration
- 9. Test Case Execution
The Matter Test-Harness is a comprehensive test tool used for certification testing of Matter devices in accordance with the Matter protocol as defined in the Matter specification.
This user guide serves as the primary user documentation to work with the Test-Harness ( TH ) tool, providing high-level architecture of the tool, how to use the tool to execute certification tests and submit the test results to CSA for certification.
The TH tool runs on the Raspberry Pi platform, providing an intuitive Web user interface to create a test project, configure the project/Device Under Test ( DUT ) settings, load the required test cases using the PICS xml file and execute test cases for various devices (commissioner, controller and controlee) as defined in the Matter specification.
The TH tool provides an option to execute the following test scripts— Automated, Semi Automated, Python, Manual and Simulated. Upon completion of the test execution, detailed logs and test results will be available for user analysis. The user will also be able to submit logs to ATL’s for review to obtain device certification.
The TH tool can be used by any DUT vendor to run the Matter certification tests, or by any hobby developer to get acquainted with the Matter certification testing tools or technologies.
-
Matter Specification: Matter Specification (Causeway) / Matter Specification (Github)
-
Matter SDK Repo github: https://github.com/project-chip/connectedhomeip
-
Matter Test Plans: Matter Test Plans (Causeway) / Matter Test Plans (GitHub)
-
PICS Tool: PICS Tool - Connectivity Standards Alliance (csa-iot.org)
-
XML Files: https://groups.csa-iot.org/wg/members-all/document/31907
-
TEDS Matter tool: https://groups.csa-iot.org/wg/matter-wg/document/28545
Important: Some links contained in this user manual require a CSA membership and authentication as a CSA authorized user in order to be accessed
This section outlines the TH architecture, data model and data flow on how different components of TH communicate with each other.
Each of the main subsystems of the Test Harness (Proxy, Frontend, Backend and Database) runs on its own docker container deployed to a Ubuntu Raspberry Pi platform. The Proxy container hosts an instance of the traefik application proxy (https://traefik.io/traefik/) which is responsible to route user requests coming from an external (to the Raspberry Pi) web browser to either the Frontend or the Backend as appropriate. The Frontend container serves the dynamic web pages that comprise the Web GUI to be rendered on the user browser including the client-side logic. According to that client-side logic and user input, REST API requests are sent again by the external browser to the Application Proxy and get redirected to the Backend container, where a FastAPI (https://fastapi.tiangolo.com/) Python application implements the server-side logic. Any application information that needs to be persisted gets serialized and written by the server-side logic to the Postgres database running in the Database container.
In addition to the four main containers described above, which get created and destroyed when the Raspberry Pi platform respectively boots up and shuts down, two other containers are created and destroyed dynamically on demand according to the test execution lifecycle: the SDK container and the OTBR container. The SDK container has copies of the Matter SDK tools (binary executables) which can be used to play the role of clients and servers of the Matter protocol in test interactions, either as Test Harness actuators or DUT simulators. That container gets automatically created and destroyed by the server-side logic at the start and at the end, respectively, of a Test Suite which needs actuators or simulators. The OTBR container, on the other hand, hosts an instance of the Open Thread Border Router and needs to be explicitly started by the TH user when they want to test a real Matter device that runs over a Thread fabric, as described in Section 7, OT Border Router (OTBR) Setup.
The data model diagram in Figure 2 shows the various data objects that the Test Execution consumes and maintains and the relationship between these data objects.
-
Test Run
-
Test Run Config
-
DUT Config
-
Harness Config
-
Test Case Execution
-
Test Step Execution
-
Test Case
-
Test Step
-
Test Suite
-
Test Case Config
The Matter Node (DUT) that is used for certification testing can either be a commissioner, controller or controlee.
If the DUT is a controlee (e.g., light bulb), the TH spins a reference commissioner/controller using chip-tool binary shipped with the SDK. The TH commissioner provisions the DUT and is used to execute the certification tests on the controlee.
If the DUT is a commissioner/controller, the Test TH spins an example accessory that is shipped with the SDK and uses that for the DUT to provision, control and run certification tests.
Refer to Section 5, Bringing Up of Matter Node (DUT) for Certification Testing to bring up the DUT and then proceed with device testing by referring to Section 8, Test Configuration.
For hobby developers who want to get acquainted with certification tools/process/TC’s, can spin DUT’s using the example apps provided in the SDK. Refer to the instructions to set up one here.
The TH runs on the official Ubuntu Server 24.04 LTS (64-bit) version. If the TH device happens to be using a different Ubuntu release or other OS, we strongly recommend fresh installing version Ubuntu Server 24.04 LTS (64-bit) for reliable results.
The official installation method uses a Raspberry Pi (TH Installation on Raspberry Pi), but there’s an alternative method used in the tool’s development that uses a virtual machine instead (TH installation without a Raspberry Pi). Keep in mind that thread networking is not officially supported in VM installations at the moment.
There are two ways to obtain the latest TH on Raspberry Pi. Follow the instructions in Section 4.1.2, TH Installation on Raspberry Pi to install TH from scratch OR if you already have the TH, follow the instructions in Section 4.4, Update Existing TH to update the TH.
The following equipment will be required to have a complete TH setup:
-
Raspberry Pi Version (4 or 5) with SD card of minimum 64 GB Memory
The TH will be installed on Raspberry PI. The TH contains couple of docker container(s) with all the required dependencies for certification tests execution.
-
Windows or Linux System (Laptop/Desktop/Mac)
The Mac/PC will be used to flash the Ubuntu image on the SD card to be used on Raspberry Pi. Download the Raspberry Pi Imager or Balena Etcher tool. The same can be used to set up the required build environment for the Matter SDK or building Matter reference apps for various platforms.
-
RCP dongle
If the DUT supports thread transport, an RCP dongle provisioned with a recommended RCP firmware for the default OTBR router that comes with the TH will be required to function properly. Currently, the OTBR can work with a Nordic RCP dongle or a SiLabs RCP dongle. Refer to Section 6, OT Border Router (OTBR) Setup on how to install the RCP firmware.
|
ℹ️
|
Starting with version v2.10 we have moved from distributing TH as an SD-Card image to publishing the TH Docker containers at Github Container Registry and pulling them at install time. By doing that the release process has been made much faster and less error-prone, while at the same time installation time has gone shorter. |
-
Place the blank SD card into the user’s system USB slot.
-
Open the Raspberry Pi Imager or Balena Etcher tool on the Mac/PC and select the 'Ubuntu Server 24.04 LTS (64-bit)'.
-
Edit the SO custom settings to:
-
username: ubuntu
⚠️ The username must be 'ubuntu'. Changing the name may cause problems running TH. -
password: raspberrypi
-
hostname: ubuntu
-
-
Make sure you have enabled the SSH service.
-
-
After the SD card has been flashed, remove the SD card and place it in the Raspberry Pi’s memory card slot.
-
Power on the Raspberry Pi and ensure that the local area network, display monitor and keyboard are connected.
-
Enter the username and password.
-
Install the TH system:
-
Clone the TH repository:
-
$git clone -b <Target_Branch/Tag> https://github.com/project-chip/certification-tool.git
-
-
Goto to TH folder:
-
$cd certification-tool
-
-
Install/configure the TH dependencies:
-
$./scripts/pi-setup/auto-install.sh -
At the end of the script, select option 1 to restart the RaspberryPi.
-
-
-
Wait about 10 minutes.
-
Using the ifconfig command, obtain the IP address of the Raspberry Pi. The same IP address will be used to launch the TH user interface on the user’s system using the browser.
-
Proceed with test configuration and execution (refer to Section 8, Test Configuration and Section 9, Test Case Execution respectively).
The official installation method uses a Raspberry Pi (TH Installation on Raspberry Pi). This alternative installation method is targeted for development purpose and it only supports onnetwork pairing mode.
|
ℹ️
|
To install TH without using a Raspberry Pi you’ll need a machine with Ubuntu Server 24.04 LTS (64-bit). You can create a virtual machine for this purpose, but be aware that if the host’s architecture is not arm64 you’ll need to substitute backend, frontend and the SDK’s docker image in order for it to work properly.
|
|
ℹ️
|
Images for linux/amd64 will not always be available in the github registry. So, if necessary, the images need to be built locally using the following script:./certification-tool/scripts/build.sh
|
Here’s an example of how to create a virtual machine for TH using multipass (https://multipass.run/).
Please make sure the docker images are compatible with the host architecture. |
-
Install multipass
|
-
Create new VM with Ubuntu Server 24.04 LTS (64-bit) (2 cpu cores, 8G mem and a 50G disk)
|
-
SSH into VM
|
|
ℹ️
|
About Multipass: Seems like bridged network is not available, so you will not be able to test with DUT outside the docker container, but you can develop using the sample apps on the platform. |
-
Clone git repo
|
-
Go into the repo directory
|
-
Run TH auto install script
|
-
Reboot VM
If using multipass, to find the IP address use the command
|
If the platform of the machine that will run the TH is 'linux/amr64' it will not be necessary to build a new SDK docker image.
To run TH on a machine using the 'linux/amd64' platform, you will need to first build a new SDK docker image.
-
Get the SDK commit SHA
Value for variable |
-
Download the Dockerfile for chip-cert-bins from the commit you need
Substitute <COMMIT_SHA> with the value from |
-
Copy Docker file to TH’s machine
-
Make sure that no other SDK image for that commit SHA is loaded in the machine
Run |
-
Build new SDK image (this could take about 3 hours)
Substitute <COMMIT_SHA> with the value from |
-
Update TH sample apps
To update your sample apps using the new image run this script in the certification-tool repository |
|
|
If the Operating System is not the Ubuntu Server 24.04 LTS (64-bit), please flash and use a SD card with that Ubuntu release to use this version of Test Harness. Beware that the auto update process below will fail in the case of a different release version. |
To update an existing TH environment, follow the instructions below on the terminal.
Wait for 10 mins and open the TH application using the browser |
It is possible to update yaml test script content by directly editing the file content. It is useful when validating small changes or fixing misspelled commands.
Yaml files are located at:
|
To update an existing Yaml test script: (e.g. Test_TC_ACE_1_1.yaml)
-
Open the script file:
|
-
Update/change the desired information.
-
Save and close the file.
-
Restart TH’s backend container:
|
-
Changes will be available on the next execution of the yaml test.
To create a new Yaml test script:
-
Use an existing test script as a starting point.
-
Rename the file to a new one: e.g.
Test_TC_ACE_1_1.yamltoTest_TC_ACE_9_9.yaml -
Update the name entry inside the yaml file:
FROM name: 42.1.1. TO name: 42.1.1. |
-
Proceed as explained on updating an existent yaml file.
To use customized tests, the files must be placed in the specific folder (described below). This way, Test-Harness will load and display the available tests on the interface. These tests will not be affected if the system is restarted or if the SDK Yaml tests are updated.
Custom Yaml files folder are located at:
|
Custom Python files folder are located at:
|
Hint: You can copy the original SDK Yaml/Python test to Custom Yaml/Python folder and do any changes on it. |
-
During the execution of TH installation commands if a read-only file system error or an error showing "Is docker daemon running?" occurs, follow the steps below to fix the issue:
|
-
Upon successful completion, try the following commands:
|
-
In case "sudo fsck" fails, use the following commands:
|
-
In case the "remote: Repository not found" fatal error occurs, try the following steps to fix the issue. Clone the certification-tool with personal access token (Refer to Section 4.2.2, Generate Personal Access Token to generate the personal access token) and follow the steps below.
cd ~ Take the backup of Test Harness binary using below command: Follow the instructions given in the section below on how to update an existing Test-Harness |
The Personal Access Token may be required during the process of updating an existing TH. Below are the instructions to obtain the personal access token.
-
Connect to the Github account (the one recognized and authorized by Matter).
-
On the upper-right corner of the page, click on the profile photo, then click on Settings.
-
On the left sidebar, click on Developer settings.
-
On the left sidebar, click on Personal access tokens [Personal access tokens (classic)].
-
Click on Generate new token .
-
Provide a descriptive name for the token.
-
Enter an expiration date, in days or using the calendar.
-
Select the scopes or permissions to grant this token.
-
Click on Generate new token .
-
The generated token will be printed out on the screen. Make sure to save it as a local copy as it will disappear.
ℹ️Sample token: ghp_hUQExoppLKma***************Urg4P
During the initial reboot of the Raspberry Pi, if the docker is not initiated automatically, try the following command on the Raspberry Pi terminal to bring up the dockers.
Use the command Once the SSH connection is successful, start the docker container using the command The above command might take a while to get executed, wait for 5-10 minutes and then proceed with the Test Execution Steps as outlined in the below sections. |
If the Test-Harness environment is facing issues to install, update or start and no other action is working, you may try the cleanup command followed by a install operation.
|
|
Please, be advised that this cleanup operation will delete all previous data from the TH database, along with all the docker networks, containers, images used by the application and more. |
Follow the bellow procedure to clean and install Test-Harness:
Use the command Once the SSH connection is successful, clean the environment using the command: Finally, execute a new installation with the following command: |
A Matter node can either be a commissioner, controller, controlee, software component or an application. The Matter SDK comes with a few example apps that can be used by Vendors as a reference to build their products. Refer to the examples folder in the SDK github repo for the same.
DUT vendors need to get the device flashed with the production firmware revision that they want to get their device certified and execute all the applicable TC’s for their products using the TH. DUT vendors can skip the below sections as the TH brings up the reference applications automatically during the certification tests execution.
A hobby developer can build Matter reference apps either using a Raspberry Pi or Nordic DK board (if the user wants to use thread transport). Follow the instructions below for the Raspberry Pi and Nordic platforms.
In the case where a device maker/hobby developer needs to bring up a sample/reference DUT, i.e. light bulb, door lock, etc. using the example apps provided in SDK and verify provisioning of the DUT over the Bluetooth LE, Wi-Fi and Ethernet interfaces, follow the below steps to set up the DUT.
Users can either use the example apps (i.e. light bulb, door lock, etc.) that are shipped with the TH OR build the apps from the latest SDK source.
To use the apps that are shipped with the TH, follow the instructions below:
-
Do a fresh install of TH (Installation on Raspberry Pi).
-
Go to the apps folder in /home/ubuntu/apps (as shown below) and launch the app that the user is interested in.
To build the example apps from the latest SDK source, follow the instructions below:
-
User to acquire Raspberry Pi Version (4 or 5) with SD card of minimum 64 GB memory.
-
Do a fresh install of the Ubuntu Server 24.04 LTS (64-bit) image and install all the required dependencies as outlined in https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/BUILDING.md.
-
Clone the connected home SDK repo using the following commands:
$ |
-
Select the sample app that the user wants to build as available in the examples folder of the SDK repo e.g., lighting-app, all-cluster-app. The user needs to build these apps for the Linux platform using the following command:
Build the app using the below command:
|
The sample app (lighting-app or lock-app or all-cluster-app) can be provisioned over the Wi-Fi network when the app is launched with the "--wifi" argument.
|
The sample app (lighting-app or lock-app or all-cluster-app) can be provisioned over the Ethernet (using onnetwork configuration) that it is connected when the app is launched with no arguments.
|
Follow the instructions below to set up the Matter Node on Thread Platform. For additional reference, go to the following link:
The following devices are required for a stable and full Thread Setup:
-
DUT: nRF52840-DK board and one nRF52840-Dongle
|
ℹ️
|
The DUT nRF52840-DK board mentioned in this manual is used for illustration purposes only. If the user has a different DUT, they will need to configure the DUT following the DUT requirements. |
To set up the Thread Board, follow the instructions below.
|
ℹ️
|
The nRF52840-DK setup can be performed in two methods either by flashing the pre-built binary hex of sample apps which is released along with the TH by using the nRF Connect Desktop application tool (refer Section 5.2.2.1) or by building the docker environment to build the sample apps (refer Section 5.2.2.2). |
-
Requirements:
-
nRF Connect for Desktop tool: Installer for Windows, MAC or Linux
ℹ️The J-Link driver needs to be separately installed on macOS and Linux. Download and install it from SEGGER under the section J-Link Software and Documentation Pack. -
Download thread binary files which are released along with the TH.
-
-
From the User Interface:
-
Connect nRF52840-DK to the USB port of the user’s operating system.
-
From the nRF Connect for Desktop tool, install Programmer from the apps tab.
-
Open the Programmer tool to flash the downloaded binary hex file on nRF52840-DK.
-
In the Programmer tool, select the device name from the SELECT DEVICE drop-down list.
-
Select Add file and browse the downloaded file to upload the desired sample app hex file.
-
Select Erase & write to flash the hex file on the device.
-
Check the log for successful flash.
-
Connect the nRF52840-Dongle to the USB port of the Raspberry Pi having the latest TH.
-
For the Thread DUT, enable discoverable over Bluetooth LE (e.g., on nRF52840 DK: select Button 4) and start the Thread Setup Test execution by referring to Section 8, Test Configuration .
-
-
To build the sample apps for nRF-Connect, check out the Matter repository and bootstrap using following commands:
git clone https://github.com/project-chip/connectedhomeip.git
cd ~/connectedhomeip/
source scripts/bootstrap.sh
cd ~/connectedhomeip/
source scripts/activate.sh -
If the nRF-Connect SDK is not installed, create a directory running the following command:
$
mkdir ~/nrfconnect -
Download the latest version of the nRF-Connect SDK Docker image by running the following command:
$
sudo docker pull nordicsemi/nrfconnect-chip -
Start Docker using the downloaded image by running the following command:
sudo docker run --rm -it -e RUNAS=$(id -u) -v ~/nrfconnect:/var/ncs -v ~/connectedhomeip:/var/chip -v /dev/bus/usb:/dev/bus/usb --device-cgroup-rule "c 189:* rmw" nordicsemi/nrfconnect-chip -
The following commands can be executed to change the settings if required:
~/nrfconnect can be replaced with an absolute path to the nRF-Connect SDK source directory.
~/connectedhomeip can be replaced with an absolute path to the CHIP source directory.-v /dev/bus/usb:/dev/bus/usb --device-cgroup-rule "c 189: rmw"*
ℹ️Parameters can be omitted if flashing the example app onto the hardware is not required. This parameter gives the container access to USB devices connected to your computer such as the nRF52840 DK. --rm can be omitted if you do not want the container to be auto-removed when you exit the container shell session.
-e RUNAS=$(id -u) is needed to start the container session as the current user instead of root. -
Update the nRF-Connect SDK to the most recent supported revision, by running the following command:
$
cd /var/chip
$python3 scripts/setup/nrfconnect/update_ncs.py --update
Perform the following procedure, regardless of the method used for setting up the environment:
-
Navigate to the example directory:
$
cd examples/all-clusters-app/nrfconnect -
Before building, remove all build artifacts by running the following command:
$
rm -r build -
Run the following command to build the example, with build-target replaced with the build target name of the Nordic Semiconductor’s kit, for example, nrf52840dk_nrf52840:
$
west build -b <build-target> --pristine always — -DCONFIG_CHIP_LIB_SHELL=yTarget Name
Compatible Kit
nRF52840 DK
nrf52840dk_nrf52840
nRF5340 DK
nrf5340dk_nrf5340_cpuapp
nRF52840 Dongle
nrf52840dongle_nrf52840
nRF7002 DK
nrf7002dk_nrf5340_cpuapp
-
To flash the application to the device, use the west tool and run the following command from the example directory:
$
west flash --erase -
Connect the nRF52840-Dongle to the USB port of the Raspberry Pi having the latest TH.
-
For the Thread DUT, enable discoverable over Bluetooth LE (e.g., On nRF52840 DK: Press Button 4) and start the Thread Setup Test execution by referring to Section 8, Test Configuration.
The Matter Python REPL, also known as chip-repl, is a native IPython shell environment loaded with a Python-wrapped version of the C++ Matter stack to permit interacting as a controller to other Matter-compliant devices.
You can use the chip-cert-bins SDK image to run chip-repl on your Test Harness by follwing these instructions:
-
Start container:
Remember to setPATH_TO_PAA_ROOTSand substitute<SDK SHA RECOMMENDED>
|
-
Activate python environment:
|
-
Run chip-repl:
|
If the DUT supports Thread Transport, DUT vendors need to use the OTBR that is shipped with the TH for certification testing. Here are the instructions to set up OTBR that comes with the TH. Users need to get the RCP programmed with the recommended version and connect it to the Raspberry Pi running the TH. The OTBR will be started when the TH runs the thread transport related TC’s.
Currently the OTBR in the TH works with either the Nordic RCP dongle or SiLabs RCP dongle. Refer to Section 7.1 to flash the NRF52840 firmware or Section 7.2 to flash the SiLabs firmware and get the RCP’s ready. Once the RCP’s are programmed, the user needs to insert the RCP dongle on to the Raspberry Pi running the TH and reboot the Raspberry Pi.
-
Download RCP firmware package from the following link on the user’s system — Thread RCP Firmware Package
-
nRF Util is a unified command line utility for Nordic products. For more details, refer to the following link— https://www.nordicsemi.com/Products/Development-tools/nrf-util
-
Install the nRF Util dependency in the user’s system using the following command:
python3 -m pip install -U nrfutil -
Connect the nRF52840 Dongle to the USB port of the user’s system.
-
Press the Reset button on the dongle to enter the DFU mode (the red LED on the dongle starts blinking).
-
To install the RCP firmware package on to the dongle, run the following command from the path where the firmware package was downloaded:
nrfutil dfu usb-serial -pkg <FILE NAME> -p /dev/ttyACM0
Example:
nrfutil dfu usb-serial -pkg nrf52840dongle_rcp_c084c62.zip -p /dev/ttyACM0 -
Once the flash is successful, the red LED turns off slowly.
-
Remove the Dongle from the user’s system and connect it to the Raspberry Pi running TH.
-
In case any permission issue occurs during flashing, launch the terminal and retry in sudo mode.
The Nrfconnect Sample apps binary Package is available for download and should be flashed in the development kit NRF52840DK to use it as DUT in the Test-Harness tests.
Download the latest version of ot-rcp-binaries from the assets list of the latest release: Silicon Labs Matter GitHub
For detailed RCP firmware usage, refer to: https://www.silabs.com/documents/public/application-notes/an1256-using-sl-rcp-with-openthread-border-router.pdf
Requirements:
-
SiLabs RCP: Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT Kit or EFR32MG Wireless Starter Kit
-
SiLabs RCP Firmware: See Session 6.2
From UI:
-
Connect the RCP dongle to the USB port of the user’s operating system or via Ethernet.
-
From the Simplicity Commander app, select and connect to RCP:
-
For USB connection, select the corresponding Serial Number from the drop-down list.
-
For Ethernet connection, enter the IP address of the RCP and click on Connect .
-
-
To flash an image, go to "Flash", select the RCP binary file, and click on Flash .
From CLI:
-
In case RCP is connected via Ethernet and the Simplicity Commander UI is not an option, the RCP image can be flashed using CLI.
-
From path to Simplicity Commander:
commander flash <rcp-image-path> --ip <rcp-ip-address>
TH spins the OTBR docker image automatically when executing the thread related test cases. Follow the steps below if the user wants to start OTBR with custom parameters. The user needs to generate a dataset for the custom OTBR. To generate hexadecimal code required for manual Thread pairing procedure, use the instructions below.
ssh the Raspberry-Pi in the User System using the command "ssh ubuntu@IP_address"
Example output for the above command to generate the dataset value:
ubuntu@ubuntu:~$ ./certification-tool/backend/test_collections/matter/scripts/OTBR/otbr_start.sh
nrfconnect/otbr 9185bda 083c8472bc52 10 months ago 1.21GB waiting 10 seconds to give the docker container enough time to start up… |
If any issue occurs while using otbr_start.sh, follow the steps below to generate the dataset value manually:
On Terminal 1:
-
Follow the steps below to build the OTBR docker:
-
Create the docker network by executing the following commands:
sudo docker network create --ipv6 --subnet fd11:db8:1::/64 -o com.docker.network.bridge.name=otbr0 otbr
sudo sysctl net.ipv6.conf.otbr0.accept_ra_rt_info_max_plen=128
sudo sysctl net.ipv6.conf.otbr0.accept_ra=2 -
Run the dependency:
sudo modprobe ip6table_filter -
Run the docker:
sudo docker run -it --rm --privileged --network otbr -p 8080:80 --sysctl "net.ipv6.conf.all.disable_ipv6=0 net.ipv6.conf.all.forwarding=1" --name otbr -e NAT64=0 --volume /dev/ttyACM0:/dev/ttyACM0 nrfconnect/otbr:9185bda --radio-url spinel+hdlc+uart:///dev/ttyACM0
-
-
Generate the Thread form for dataset by entering ‘<Raspberry-Pi IP>:8080’ on the user’s system browser. The OTBR form will be generated as shown below.
-
Click on the Form option and follow the sequence to generate the OTBR form.
On Terminal 2:
-
Generation of Hex Code:
Obtain the dataset hex value by running the following command:sudo docker exec -ti otbr ot-ctl dataset active -xExample hex code :
0e080000000000010000000300000f35060004001fffe0020811111111222222220708fdabd97fc1941f29051000112233445566778899aabbccddeeff030e4f70656e54687265616444656d6f010212340410445f2b5ca6f2a93a55ce570a70efeecb0c0402a0f7f8 -
The above generated sample pairing code can be used during the manual Thread pairing procedure with the following command:
./chip-tool pairing ble-thread <node-id> hex:<dataset hex value> <setup-pin> <discriminator>
./chip-tool pairing ble-thread 97 hex:0e080000000000010000000300001035060004001fffe0020811111111222222020708fd882e3d3a7373dc051000112233445566778899aabbccddeeff030f4f70656e54687265616444656d70790102123404101570fcfd6de18b3d78d6d39881a8a5710c0402a0f7f8 20202021 3840
-
Error message: (Example)
Error occurred during setup of test suite.FirstChipToolSuite. 409 Client Error for http+docker://localhost/v1.42/containers/10ad48500522af3d5a23c181a6018053248250b958a353ed88d5a5f538dcbf33/exec: Conflict ("Container 10ad48500522af3d5a23c181a6018053248250b958a353ed88d5a5f538dcbf33 is not running")
Solution:
-
Check for the presence of rogue executions of the otbr-chip container. Using command:
$docker psStop any running otbr-chip containers from the result.
$docker container stop <container_id> -
Check host (raspberry) network configuration interface’s ip address does not conflict with otbr-chip default interface ip address.
Conflicting network configuration could be pointed out by checking container’s initialization log.
$docker logs <container_id>Example Log Output:
…
+ service tayga start
* Starting userspace NAT64 tayga
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
…fail!
+ die 'Failed to start tayga'
+ echo ' * ERROR: Failed to start tayga'
* ERROR: Failed to start tayga
+ exit 1
tail: cannot open '/var/log/syslog' for reading: No such file or directory
tail: no files remainingDefault Tayga interface address:
ipv4-addr 192.168.255.1# This address could be checked on /etc/tayga.conf on otbr-chip containerUse command below on host (raspberrypi) to check interface’s ip addresses
$ifconfig
…
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.2 netmask 255.255.255.0 broadcast 192.168.2.255 inet6 fdcb:377:2b62:f8fd:dea6:32ff:fe94:c54c prefixlen 64 scopeid 0x0<global> inet6 fe80::dea6:32ff:fe94:c54c prefixlen 64 scopeid 0x20<link> ether dc:a6:32:94:c5:4c txqueuelen 1000 (Ethernet) RX packets 250969 bytes 184790487 (184.7 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 125202 bytes 85904550 (85.9 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 520 bytes 48570 (48.5 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 520 bytes 48570 (48.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0If any interface matches tayga ip address, change the conflicting IP on host.
-
When the DUT is a client, refer to Simulated Tests. The TH brings up the example accessory using chip-app1 binary. The user will be prompted to commission the device. Once the commissioning process is completed, proceed with the test execution.
In the case where the DUT is a server, the TH spins up the controller, the DUT bring-up procedure should be completed and has to be paired with the controller.
Depending on the DUT’s network transport, any one of the appropriate pairing modes can be opted:
-
‘ble-wifi ’ to complete the pairing for the DUT using BLE Wi-Fi
-
‘onnetwork’ to complete the pairing for the DUT that is already on the operational network (e.g., the device is already present on the same Ethernet network of the TH) connection
-
‘ble-thread’ to complete the pairing for the Thread Device
Follow the sections below for the project configuration and test execution.
-
Open a Web browser from the user’s system and enter the IP address of the Raspberry Pi as given in Section 4.1.2, TH Installation on Raspberry Pi.
-
In case the TH user interface does not launch, refer to Section 4.2.3, Bringing Up of Docker Containers Manually.
-
A new window will be opened as "Matter Test Harness".
-
Click on the Create New Project button. Enter the project name as "Test Project" and edit the Project Config settings to provide additional details.
{ "test_parameters": null, "network": { "wifi": { "ssid": "testharness", "password": "wifi-password" }, "thread": { "rcp_serial_path": "/dev/ttyACM0", "rcp_baudrate": 115200, "on_mesh_prefix": "fd11:22::/64", "network_interface": "eth0", "dataset": { "channel": "15", "panid": "0x1234", "extpanid": "1111111122222222", "networkkey": "00112233445566778899aabbccddeeff", "networkname": "DEMO" }, "otbr_docker_image": null } }, "dut_config": { "discriminator": "3840", "setup_code": "20202021", "pairing_mode": "onnetwork", "chip_timeout": null, "chip_use_paa_certs": false, "trace_log": true } }
-
Configure the DUT by providing details like discriminator, setup_code and set the pairing_mode as "ble-wifi".
"dut_config": { "discriminator": "3840", "setup_code": "20202021", "pairing_mode": "ble-wifi", "chip_timeout": null, "chip_use_paa_certs": false, "trace_log": true } -
To pair in the BLE Wi-Fi mode, configure the Network settings by providing the ssid and password.
"network": { "wifi": { "ssid": "testharness", "password": "wifi-password" }, ... }
-
If the DUT is already present on the operational network (e.g., connected to the same network as the controller via Ethernet) then the user can select this mode.
-
Configure the DUT by providing details like discriminator, setup_code and set the pairing_mode as "onnetwork".
"dut_config": { "discriminator": "3840", "setup_code": "20202021", "pairing_mode": "onnetwork", "chip_timeout": null, "chip_use_paa_certs": false, "trace_log": true }
-
Input the DUT configuration details like discriminator: "3840", setup_code:"20202021", and pairing_mode as "ble-thread".
"dut_config": { "discriminator": "3840", "setup_code": "20202021", "pairing_mode": "ble-thread", "chip_timeout": null, "chip_use_paa_certs": false, "trace_log": true } -
The TH loads the default thread configuration values that match the OTBR built on the TH. The following configuration can be customized as per the user’s need.
"thread": { "rcp_serial_path": "/dev/ttyACM0", "rcp_baudrate": 115200, "on_mesh_prefix": "fd11:22::/64", "network_interface": "eth0", "dataset": { "channel": "15", "panid": "0x1234", "extpanid": "1111111122222222", "networkkey": "00112233445566778899aabbccddeeff", "networkname": "DEMO" }, "otbr_docker_image": null }ℹ️The OTBR docker is contained in the TH and runs automatically upon the start of the TH tool. -
If using an already configured Thread network with a Thread Border router present on the same network as the TH, it is possible to provide an explicit operational data configuration so that it is used instead of locally configuring a new Thread PAN/
"thread": { "operational_dataset_hex": "0e08000000000001000035060004001fffe00708fd5270f26ee4c02c041064dc641d7195508d7cd17ce22db711420c0402a0f7f8000300000f0102123402081111111122222222030444454d4f051000112233445566778899aabbccddeeff" }⚠️ OTBR needs to be configured and running. TH will not start any OTBR docker containers.
For the case that the DUT requires a PAA certificate to perform a pairing operation, input "true" for the flag "chip_tool_use_paa_certs" to configure the Test-Harness to use them.
"dut_config": {
"discriminator": "3840",
"setup_code": "20202021",
"pairing_mode": "onnetwork",
"chip_timeout": null,
"chip_use_paa_certs": true,
"trace_log": true
}|
ℹ️
|
Make sure to include the desired PAA certificates in the default path "/var/paa-root-certs/", in the Raspberry-Pi. |
-
Input the test parameters like endpoint on the DUT where the cluster to be tested is implemented.
"test_parameters": { "endpoint": 5 } -
"qr-code" and "manual-code" parameters:
Only one of the following parameter is allowed, also when one of them is configured, the TH will not send "passcode" and "discriminator" (from "dut_config") arguments to DUT.-
"qr-code" parameter example:
"test_parameters": { "qr-code": "MT:-24J042C00KA0648G00" } -
"manual-code" parameter example:
"test_parameters": { "manual-code": "34970112332" } -
Invalid configuration: "manual-code" and "qr-code" together:
"test_parameters": { "qr-code": "MT:-24J042C00KA0648G00" "manual-code": "34970112332" }⚠️ This is an invalid configuration. TH will not accept both parameters set at the same time.
-
On completion of the "network" and the "dut_config" configuration, select the Update and then Create button to create the Test Project.
The newly created project will be listed under the Project details column.
Click on the Edit option to configure the project to load the required PICS file for the cluster to be tested and select the Update button. Refer to Section 9, Test Case Execution.
-
Now the Test Project is ready for execution. Click on the Go To Test-Run icon and create a new Test Run batch.
-
A Test Run can be created in Regular Mode or Certification Mode. The test cases are automatically selected based on the PICS files provided in the Project Configuration. For a Test Run in Regular Mode, it is possible to change this selection, but in Certification Mode that selection is unchangable — a test case must be executed if and only if the PICS files indicate that it is applicable.
-
Provide a Test name for this run such as Door Lock First Run. Input any additional description about the run. Enter the Test Engineers Name under Operator. Select only the test cases that are to be executed and deselect other test cases. There is a search option available to search for a particular test case. The number of times the test is to be executed can be given by clicking on the number spin control.
Ensure that DUT is in the discoverable mode before clicking on the Start button.
Example command to be used to launch the sample apps (e.g., all-cluster-app):Ble-wifi: ./chip-all-clusters-app --wifi
Onnetwork: ./chip-all-clusters-app
Thread: Enable discoverable over Bluetooth LE (ex: On nRF52840 DK: Press Button 4 to start BLE advertisements)
-
Click on the Start button for the test execution. Note that the test execution gets started and the log window appears. Click on the Abort button to stop the test execution.
-
Once the test execution is completed, click on
-
The Yellow icon to download the test logs
-
The Blue icon to save the test reports
-
-
Click on the Result button and select the test that was executed and click on Show Report to view the reports. The user can also select previously executed tests and view the reports and logs. There is an option provided to re-run the test cases. Refer to Section 10, Collect Logs and Submit to TEDS to collect the logs and submit the reports to TEDS.
-
To start a new Test Run in Certification Mode, first select the Certification Mode button and then click on + Add Test.
-
Click on Utility Menu to review the previous test report.
-
Click on the Browse button to upload the previous report and select the desired log filter options. The console logger contains a filter drop-down list to select the different categories of logs to display. Use the Print button to print the test report.
Click on the "Select theme" option drop-down to select the different theme for the user interface.
Refer to Section 2, References for PICS tool documentation to generate the PICS XML files.
PICS (Protocol Implementation Conformance Statement) is a list of features supported by a device as defined by a technology protocol , standard or specification. Each feature is known as a PICS Item , and device implementation is either mandatory or optional. PICS is used by the device manufacturer as a statement of conformance to a technology standard and a requirement for all CSA Product Certification programs.
PICS codes are generated from the Test Plans. The Base.xml file lists all the Core feature PICS from the Matter Base Specifications and the application cluster PICS are listed in the respective TestPlan.xml files. Follow the steps below to generate and upload the PICS files.
-
Click on the following link to download the PICS XML files— https://groups.csa-iot.org/wg/members-all/document/31907
-
Click on the following link to use the PICS tool— PICS Tool v1.6.4 matter 1.0 - Connectivity Standards Alliance (csa-iot.org)
-
Load the Base.xml file by clicking on the Browse option. In case the following error is observed:
⚠️ Base.xml: This XML PICS template is unapproved and has not been tested with this tool. To test new or updated PICS documents, please enable author mode and try again. Enable author mode and retry uploading the XML file.
-
Load the XML file that is required for testing, e.g., Doorlock.xml.
-
Check the option for which the testing will be done for the DoorLock cluster. In the case of the Door Lock cluster to be tested in the Server mode, select the checkbox for DRLK.S. In case the cluster has to be tested in the Client mode, select the checkbox for DRLK.C.
-
Review all the attributes/commands that are supported by the DoorLock cluster and ensure the corresponding options are checked in the PICS tool.
-
Click on Validate PICS . Ensure that there are no warnings or errors. In case of any warnings or errors, revisit the options and check/uncheck the options as supported by the DUT.
-
Prior to the test execution, the user will have to load the relevant PICS file to list the required test cases. Depending on the PICS file loaded, the test suites list will be updated accordingly.
Click on the SDK YAML Tests tab. The automated and semi automated test cases will be listed in FirstChipToolSuite. The Automated test cases will be listed as the TC-<Cluster>-XX without any suffix, e.g., TC-DRLK-1.1. Automated test case execution will not require any manual intervention.
The Semi Automated test cases will be listed as TC-<Cluster>-XX(Semi-automated). During the Semi Automated test case execution, some of the steps will be executed automatically and the user will be prompted to perform a few steps as shown below in the screenshots. From the TH user interface, load the required PICS file to select the test cases, e.g., Doorlock Test Plan.xml.
Select the required Semi Automated test case to be executed and ensure other test cases are not selected. Take for example TC-ACE-1.6 as shown below:
Bring up the DUT (All Clusters as Server) by sending the following command ./chip-all-clusters-app on the Raspberry Pi terminal and click on the Start button.
During the Test execution, as the log gets updated, copy the newly generated node ID.
Form the Chip-tool, execute the above command with node ID listed in the TH log. Save the Chip-tool logs in a text file. Verify the result in the Chip-tool log and select the applicable choice from the user prompt in the TH tool and select the Submit button.
Example:
|
Check for the response of the command in the Chip-tool log and compare with the expected response from the TH user prompt as shown below. In case both the responses match, click on PASS followed by the Submit button.
At the end of the test execution, the user will be prompted to upload the Chip-tool logs that were saved in the previous step.
The Onboarding Payload Device Discovery test cases are listed under this option. Before executing the Python tests, bring up the DUT in the Chip-tool and save the discovery log. During the Python test execution, the user is prompted to input data such as QR code. Copy the data from the previously saved logs and provide the input. Follow the sequence below to execute the python_tests.
During the DUT bring-up, note down the QR code and save it for future use.
Select the python_tests tab for the test execution.
During the test execution the user is prompted for the QR code. Use the code that was saved earlier and proceed with the testing.
During the manual test case execution, the user is prompted for an action for each test step as shown below.
After the Manual pairing of the DUT, execute the command displayed on the prompt as shown below.
Example: |
Save the Chip-tool logs in a text file. Validate the chip tool log and select the applicable choice from the user prompt in the TH tool and select the Submit button. At the end of the test execution, the user is prompted to upload the Chip-tool logs that were saved in the previous step.
Simulated tests must be executed when the DUT is considered as a Client. The simulated test cases will be listed in FirstAppSuite under the SDK YAML Tests tab.
During the execution of these tests, the user is prompted for an action to be performed on the device as shown in the following screenshot.
Follow the instructions provided in the user prompt to complete the test execution.
IMPORTANT: Currently the selection will be done automatically by TH based on the test execution result. In the future the User Prompt will be updated to proper represent this behavior. |
Some automated Python scripts are available inside the docker of the TH.
E.g.: TC_ACE_1_3.py, TC_ACE_1_4.py , TC_CGEN_2_4.py , TC_DA_1_7.py , TC_RR_1_1.py TC_SC_3_6.py
Follow the instructions below to execute the test cases.
-
A directory containing the PAA (Product) roots that will be mounted as /paa_roots.
-
Run the following commands from the Raspberry Pi terminal.
cd certification-tool
./backend/test_collections/matter/scripts/update-paa-certs.sh -
After execution of the above commands ensure that the PAA’s are available locally at /var/paa-root-certs .
Device-specific configuration is shown as shell variables. PLEASE REPLACE THOSE WITH THE CORRECT VALUE in the steps below.
-
$PATH_TO_PAA_ROOTS: Path on host where PAA roots are located. Failure to provide a correct path will cause early failure during commissioning (e.g., /var/paa-root-certs/)
-
$DISCRIMINATOR: Long discriminator for DUT (e.g., 3840 for Linux examples)
-
$SETUP_PASSCODE: Setup passcode for DUT (e.g., 20202021 for Linux examples)
-
$WIFI_SSID: SSID of Wi-Fi AP to which to attempt connection
-
$WIFI_PASSPHRASE: Passphrase of Wi-Fi AP to which to attempt connection
-
$BLE_INTERFACE_ID: Interface ID for BLE interface (e.g., 0 for default, which usually works)
-
$THREAD_DATASET_HEX: Thread operational dataset as a hex string (e.g., output of dataset active -x in OpenThread CLI on an existing end-device
Factory-reset the DUT
|
This downloads a Docker image with the test environment, and runs the environment including mounting the PAA trust store in /paa_roots and mounts the local Avahi socket so that Avahi in the VM can run against its host.
-
You will be shown a # root prompt
|
ℹ️
|
The first time running docker will be SLOW (around 5 minutes) due to the need to download data. Every other run after that will be instant. |
Execute the following command:
|
To test this against a Linux target running on the same network as the host:
|
|
ℹ️
|
|
Execute the following command in the docker for the BLE+Wi-Fi pairing:
|
Execute the below command in the docker for the BLE+Thread pairing:
|
Factory reset the DUT again → The test fills tons of stuff and the device will be in an odd state of ACL’s. This will be fixed once there is ample time to clean up after the test is completed by sending commands to, for example, remove the fabrics joined.
-
Failing at Step 9 during execution of TC_RR_1_1:
-
Some DUT’s have an incorrectly-configured UserLabel cluster where the backend is not implemented due to SDK example issues where some examples have the backend and others do not. This will fail at the last step ("Step 9: Fill UserLabel clusters on each endpoint"), with FAILURE writes. To override the test not to run this step, you can add "--bool-arg skip_user_label_cluster_steps:true" to the command line of TC_RR_1_1.py, at the end.
-
Not having the $PATH_TO_PAA_ROOTS set properly when starting the docker or not having PAA roots certificates at that path.
-
Follow the instructions for item 2 in Section 9.5.1.1, Prerequisite.
-
The documents in this link are intended to be used to help root-cause common test failures, especially in cases where the underlying cause of the failure may not be immediately obvious from the test step or expected outcomes.
Some automated Python scripts are available in TH User Interface.
To execute the tests, the parameters discriminator, setup_code and pairing_mode need to be filled in the device configuration parameters (dut_config).
To configure specific/custom parameters, please edit the project configuration to include the parameters in the session (test_parameters).
Project configuration example:
{
...
"dut_config": {
"discriminator": "3840",
"setup_code": "20202021",
"pairing_mode": "onnetwork",
"chip_tool_timeout": null,
"chip_tool_use_paa_certs": false
},
"test_parameters": {
"paa-trust-store-path": "/credentials/development/paa_roots",
"storage-path": "admin_storage.json"
}
...
}PIXIT type parameters must be filled in the test_parameters section. The following example will be used to define the following parameters:
PIXIT.ACE.APPENDPOINT:1 PIXIT.ACE.APPDEVTYPEID:256 PIXIT.ACE.APPCLUSTER:OnOff PIXIT.ACE.APPATTRIBUTE:OnOff
Project configuration example:
{
...
"test_parameters": {
"paa-trust-store-path": "/credentials/development/paa_roots",
"storage-path": "admin_storage.json",
"int-arg": "PIXIT.ACE.APPENDPOINT:1 PIXIT.ACE.APPDEVTYPEID:256",
"string-arg": "PIXIT.ACE.APPCLUSTER:OnOff PIXIT.ACE.APPATTRIBUTE:OnOff"
}
...
}The above example will be used to define the following arguments when running the test:
--int-arg PIXIT.ACE.APPENDPOINT:1 PIXIT.ACE.APPDEVTYPEID:256 --string-arg PIXIT.ACE.APPCLUSTER:OnOff PIXIT.ACE.APPATTRIBUTE:OnOffAccess the spreadsheet via the Verification Steps Document and review the information provided. Based on this data, create the parameters set as requested.
Below are some specific examples assembled from data obtained from the spreadsheet.
-
TC-ACE-1.4
Sample command to run manually inside docker
python3 TC_ACE_1_4.py --discriminator 3840 --passcode 20202021 --commissioning-method on-network --storage-path admin_storage.json --int-arg PIXIT.ACE.APPENDPOINT:1 PIXIT.ACE.APPDEVTYPEID:256 --string-arg PIXIT.ACE.APPCLUSTER:OnOff PIXIT.ACE.APPATTRIBUTE:OnOff --paa-trust-store-path /credentials/development/paa-root-certs/
Arguments to be used while executing using UI (use product specific values)
"test_parameters": { "int-arg" : "PIXIT.ACE.APPENDPOINT:1 PIXIT.ACE.APPDEVTYPEID:256", "string-arg": "PIXIT.ACE.APPCLUSTER:OnOff PIXIT.ACE.APPATTRIBUTE:OnOff" } -
TC-SC-7.1
Sample command to run manually inside docker
python3 TC_SC_7_1.py --bool-arg post_cert_test:true --qr-code MT:-<24J0CEK01KA0648G00> --storage-path admin_storage.json --paa-trust-store-path ../../credentials/development/paa-root-certs/
Arguments to be used while executing using UI (use product specific values)
"test_parameters": { "bool-arg": "post_cert_test:true", "qr-code": " MT-24J042C00KA0648G00" }
TH expects the SDK Python Tests to follow a certain template. New tests are being written with this template and the old tests are being updated to conform to it. The tests are divided in 3 test suites:
-
Python Testing Suite
-
For test cases that follow the expected template and have a commissioning first step.
-
The user will be asked to make sure that the DUT is in Commissioning Mode at the start of the test suite setup and then the DUT will be commissioned.
-
The commissioning will be kept throughout the execution of all its tests.
-
-
Python Testing Suite - No commissioning
-
For test cases that follow the expected template but don’t have a commissioning first step.
-
The selected tests will be executed without commissioning the DUT.
-
The user will be asked to make sure that the DUT is in Commissioning Mode at the start of each test.
-
-
Python Testing Suite - Legacy
-
For test cases that don’t follow the expected template yet.
-
The user will be asked to make sure that the DUT is in Commissioning Mode at the start of each test.
-
The user will also be asked if the DUT should be commissioned at the start of each test. The DUT will be commissioned depending on the user’s answer.
-
