Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TC-DD-2.1, 2.2, 3.11–3.14] - Updated Manual Scripts and Test Steps to Align with Test Plan and VS Changes #37048

Open
wants to merge 14 commits into
base: master
Choose a base branch
from
Prev Previous commit
Next Next commit
DD Manual script update
Rajashreekalmane committed Jan 13, 2025
commit 3bd829485a1cd9cb23fa1ecf792d408a348cd835
3 changes: 2 additions & 1 deletion src/app/tests/suites/certification/Test_TC_DD_2_1.yaml
Original file line number Diff line number Diff line change
@@ -185,6 +185,8 @@ tests:
2.4GHz band."
PICS: MCORE.COM.WIFI && MCORE.DD.DISCOVERY_PAF
verification: |
WIFI - PAF feature is out of scope for V1.4
[Configuration command to be filled by NXP]
Configure the AP to the PAF working channel and connect TH to AP
@@ -244,7 +246,6 @@ tests:
vendor-unique means or by commissioning the DUT onto the Matter
network and opening a commissioning window. The DUT is sending
mandatory Commissionable Node Discovery service records over DNS-SD."
PICS: MCORE.COM.WIFI && MCORE.DD.DISCOVERY_SOFTAP
verification: |
./chip-all-clusters-app
...
4 changes: 1 addition & 3 deletions src/app/tests/suites/certification/Test_TC_DD_2_2.yaml
Original file line number Diff line number Diff line change
@@ -204,9 +204,7 @@ tests:
disabled: true

- label:
"Step 4b: DUT must find TH and provide onboarding data for
validation.Pass Criteria: DUT is able to report the Onboarding payload
as set on TH"
"Step 4b: DUT starts Wi-Fi scan of all 2.4 GHz Wi-Fi channels allowed per its operational regulatory domain (channels 1, 6, and 11 are preferred)"
PICS: MCORE.DD.DISCOVERY_SOFTAP
verification: |
Out of Scope : SoftAP commissioning currently not supported
20 changes: 12 additions & 8 deletions src/app/tests/suites/certification/Test_TC_DD_3_11.yaml
Original file line number Diff line number Diff line change
@@ -67,10 +67,12 @@ tests:
current Matter spec. documentation."
PICS: MCORE.DD.DISCOVERY_BLE
verification: |
Verifiy on TH(ALL-CLUSTER-APP):
Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports BLE for its Discovery Capability, and
ensures the Version bit string follows the current Matter specification. Pass the QR code into the DUT during the commissioning process.
./chip-all-clusters-app --custom-flow 0 --capabilities 2 --ble-device 1
On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT
./chip-all-clusters-app --capabilities 2 --ble-device 1
...
[1667888323.966941][3151:3151] CHIP:DL: Device Configuration:
[1667888323.967057][3151:3151] CHIP:DL: Serial Number: TEST_SN
[1667888323.967179][3151:3151] CHIP:DL: Vendor Id: 65521 (0xFFF1)
@@ -90,8 +92,8 @@ tests:
- label: "Step 1b: Scan the QR code from the previous step using the DUT."
PICS: MCORE.DD.SCAN_QR_CODE
verification: |
1. Verify the QR code is scanned by DUT.
Note: chip-tool does not support physically scanning QR codes
Scan the QR code generated in the previous step using the DUT. Verify that the QR code is scanned successfully.
The chip-tool does not support physically scanning QR codes.
disabled: true

- label:
@@ -100,17 +102,19 @@ tests:
process using BLE"
PICS: MCORE.DD.DISCOVERY_BLE
verification: |
Verify on the DUT (CHIP-TOOL):
./chip-tool pairing code 1 MT:-24J0YXE00KA0648G00
Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the Commissioner/Commissionee commissioning process via BLE.
On DUT (CHIP-TOOL), run the following command:
./chip-tool pairing code 1 MT:-24J0YXE00KA0648G00
The DUT successfully parses the QR code and commissions the TH onto the Matter network.
[1657232374820] [31379:16804218] CHIP: [CTL] Received CommissioningComplete response, errorCode=0
[1657232374820] [31379:16804218] CHIP: [CTL] Successfully finished commissioning step 'SendComplete'
[1657232374820] [31379:16804218] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup'
[1657232374820] [31379:16804218] CHIP: [CTL] Performing next commissioning step 'Cleanup'
[1657232374820] [31379:16804218] CHIP: [CTL] Successfully finished commissioning step 'Cleanup'
[1657232374820] [31379:16804218] CHIP: [TOO] Device commissioning completed with success
Verifiy on TH(ALL-CLUSTER-APP):
On TH (ALL-CLUSTER-APP), Ensure the following log output:
[1657232374.956508][370357:370357] CHIP:DL: HandlePlatformSpecificBLEEvent 32784
[1657232374.956534][370357:370357] CHIP:SVR: Commissioning completed successfully