From a8a505a45dfea35ae299f53c13ffe8bb97fd7640 Mon Sep 17 00:00:00 2001 From: Rajashreekalmane Date: Mon, 13 Jan 2025 15:13:34 +0530 Subject: [PATCH 01/13] DD YAML Update --- .../suites/certification/Test_TC_DD_2_1.yaml | 18 +- .../suites/certification/Test_TC_DD_2_2.yaml | 167 +++++++------- .../suites/certification/Test_TC_DD_3_11.yaml | 132 ++++++----- .../suites/certification/Test_TC_DD_3_12.yaml | 168 +++++++------- .../suites/certification/Test_TC_DD_3_13.yaml | 170 +++++++------- .../suites/certification/Test_TC_DD_3_14.yaml | 209 +++++++++--------- 6 files changed, 455 insertions(+), 409 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml b/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml index e0f8386d742b97..20f9926cbf4628 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml @@ -196,6 +196,8 @@ tests: in 5GHz band if it is in ETSI regulatory domains." PICS: MCORE.COM.WIFI && !MCORE.COM.BLE && 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 @@ -204,6 +206,8 @@ tests: - label: "Step 9: DUT begins sending Wi-Fi PAF Publish messages." PICS: MCORE.COM.WIFI && MCORE.DD.DISCOVERY_PAF verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] * 2.4g: @@ -217,18 +221,22 @@ tests: - label: "Step 10: TH scans and finds the DUT SSID" PICS: MCORE.COM.WIFI && MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported on TH=chip-tool + Out of Scope : SoftAP commissioning is currently not supported. disabled: true - label: - "Step 11: TTH scans and finds the DUT SSID TH sends to DUT a 1st power + "Step 11: TH scans and finds the DUT SSID TH sends to DUT a 1st power cycle command (or reset manually) TH sends to DUT a 2nd power cycle command (or reset manually)" PICS: MCORE.COM.WIFI && MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported on TH=chip-tool + Out of Scope : SoftAP commissioning is currently not supported. + disabled: true + + - label: "Step 12: TH scans and finds the DUT SSID" + PICS: MCORE.COM.WIFI && MCORE.DD.IE + verification: | + Out of Scope : SoftAP commissioning is currently not supported. disabled: true - label: diff --git a/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml b/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml index 925ac72f7012ad..90f9ff659a5d5b 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml @@ -46,8 +46,10 @@ tests: "Step 1a: TH starts matter announcement procedure using BLE transport" PICS: MCORE.DD.DISCOVERY_BLE verification: | + Initiate the Matter announcement procedure on the TH using BLE transport, and the TH must start sending BLE advertisements successfully. ./chip-all-clusters-app --wifi --discriminator 3841 - Verify in TH as commissionee side: + + Verify in TH on the commissionee side: [1657221603.350406][368108:368108] CHIP:DL: Device Configuration: [1657221603.350445][368108:368108] CHIP:DL: Serial Number: TEST_SN @@ -70,6 +72,10 @@ tests: with a sufficient dwell time, interval, and overall duration of scan" PICS: MCORE.DD.DISCOVERY_BLE verification: | + Initiate BLE scan on the DUT across all three advertising channels, ensuring sufficient dwell time, interval, + and overall scan duration; the DUT must successfully detect the TH and retrieve the onboarding data for validation, + reporting the onboarding payload as set on the TH to meet the pass criteria. + 1. Discover commissionables over BLE using DUT=chip-tool pairing Verify in TH as commissionee side: @@ -90,7 +96,8 @@ tests: - label: "Step 2b: TH starts matter announcement using BLE transport" PICS: MCORE.DD.DISCOVERY_BLE verification: | - $ ./out/all-clusters-app/chip-all-clusters-app --wifi --discriminator 3841 + TH starts the Matter announcement using BLE transport, and the TH must begin sending BLE advertisements + ./chip-all-clusters-app --wifi --discriminator 3841 Verify in TH as commissionee side [1653087913.247229][8083:8083] CHIP:SVR: Server Listening... @@ -116,73 +123,56 @@ tests: as set on TH" PICS: MCORE.DD.DISCOVERY_BLE verification: | - 1. Discover commissionables over BLE using DUT=chip-tool pairing command - - Verify in TH as commissionee side: - [1651743346.152716][5072:5075] CHIP:DL: Device E4:5F:01:0F:3B:B1 (Path: /org/bluez/hci0/dev_E4_5F_01_0F_3B_B1) Connected - [1651743347.908807][5072:5075] CHIP:DL: BluezCharacteristicAcquireWrite is called, conn: 0xffffa0043700 - [1651743347.911151][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 - [1651743347.911349][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 - [1651743347.911754][5072:5072] CHIP:BLE: local and remote recv window sizes = 6 - [1651743347.911829][5072:5072] CHIP:BLE: selected BTP version 4 - [1651743347.911877][5072:5072] CHIP:BLE: using BTP fragment sizes rx 244 / tx 244. - [1651743348.006770][5072:5075] CHIP:DL: CHIPoBLE subscribe received - [1651743348.007026][5072:5072] CHIP:IN: BLE EndPoint 0xaaaab7bb3c20 Connection Complete - [1651743348.007132][5072:5072] CHIP:DL: HandlePlatformSpecificBLEEvent 32778 - [1651743348.007196][5072:5072] CHIP:DL: Receive kCHIPoBLEConnectionEstablished - [1651743348.150980][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 - [1651743348.199997][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 - [1651743348.200614][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 - [1651743348.201013][5072:5072] CHIP:EM: Received message of type 0x20 with protocolId (0, 0) and MessageCounter:3306320356 on exchange 29381r - [1651743348.201117][5072:5072] CHIP:EM: Handling via exchange: 29381r, Delegate: 0xaaaab7bb2a90 - [1651743348.201191][5072:5072] CHIP:SC: Received PBKDF param request - [1651743348.201280][5072:5072] CHIP:SC: Peer assigned session ID 14881 - [1651743348.201349][5072:5072] CHIP:SC: Found MRP parameters in the message - [1651743348.201520][5072:5072] CHIP:SC: Including MRP parameters in PBKDF param response - [1651743348.201884][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2ef78 to 0x0000000000000000 (0) of type 0x21 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159088. - [1651743348.201989][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2ef78 with MessageCounter:2627159088 to 0x0000000000000000 at monotonic time: 0000000000FF6731 msec - [1651743348.202196][5072:5072] CHIP:SC: Sent PBKDF param response - [1651743348.298384][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 - [1651743348.299274][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 - [1651743348.300132][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 - [1651743348.300571][5072:5072] CHIP:EM: Received message of type 0x22 with protocolId (0, 0) and MessageCounter:3306320357 on exchange 29381r - [1651743348.300655][5072:5072] CHIP:EM: Found matching exchange: 29381r, Delegate: 0xaaaab7bb2a90 - [1651743348.300741][5072:5072] CHIP:SC: Received spake2p msg1 - [1651743348.304696][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2ee58 to 0x0000000000000000 (0) of type 0x23 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159089. - [1651743348.304817][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2ee58 with MessageCounter:2627159089 to 0x0000000000000000 at monotonic time: 0000000000FF6798 msec - [1651743348.305007][5072:5072] CHIP:SC: Sent spake2p msg2 - [1651743348.444144][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 - [1651743348.444992][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 - [1651743348.445608][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 - [1651743348.445888][5072:5072] CHIP:EM: Received message of type 0x24 with protocolId (0, 0) and MessageCounter:3306320358 on exchange 29381r - [1651743348.445943][5072:5072] CHIP:EM: Found matching exchange: 29381r, Delegate: 0xaaaab7bb2a90 - [1651743348.446001][5072:5072] CHIP:SC: Received spake2p msg3 - [1651743348.446130][5072:5072] CHIP:SC: Sending status report. Protocol code 0, exchange 29381 - [1651743348.446202][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2eea8 to 0x0000000000000000 (0) of type 0x40 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159090. - [1651743348.446262][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2eea8 with MessageCounter:2627159090 to 0x0000000000000000 at monotonic time: 0000000000FF6825 msec - [1651743348.446452][5072:5072] CHIP:IN: New secure session created for device , LSID:2138 PSID:14881! - [1651743348.446962][5072:5072] CHIP:SVR: Commissioning completed session establishment step + DUT must detect the TH and retrieve the onboarding data for validation + 1. Discover commissionables over BLE using DUT=chip-tool pairing command + Verify in TH as commissionee side: + [1651743346.152716][5072:5075] CHIP:DL: Device E4:5F:01:0F:3B:B1 (Path: /org/bluez/hci0/dev_E4_5F_01_0F_3B_B1) Connected + [1651743347.908807][5072:5075] CHIP:DL: BluezCharacteristicAcquireWrite is called, conn: 0xffffa0043700 + [1651743347.911151][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 + [1651743347.911349][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 + [1651743347.911754][5072:5072] CHIP:BLE: local and remote recv window sizes = 6 + [1651743347.911829][5072:5072] CHIP:BLE: selected BTP version 4 + [1651743347.911877][5072:5072] CHIP:BLE: using BTP fragment sizes rx 244 / tx 244. + [1651743348.006770][5072:5075] CHIP:DL: CHIPoBLE subscribe received + [1651743348.007026][5072:5072] CHIP:IN: BLE EndPoint 0xaaaab7bb3c20 Connection Complete + [1651743348.007132][5072:5072] CHIP:DL: HandlePlatformSpecificBLEEvent 32778 + [1651743348.007196][5072:5072] CHIP:DL: Receive kCHIPoBLEConnectionEstablished + [1651743348.150980][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 + [1651743348.199997][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 + [1651743348.200614][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 + [1651743348.201013][5072:5072] CHIP:EM: Received message of type 0x20 with protocolId (0, 0) and MessageCounter:3306320356 on exchange 29381r + [1651743348.201117][5072:5072] CHIP:EM: Handling via exchange: 29381r, Delegate: 0xaaaab7bb2a90 + [1651743348.201191][5072:5072] CHIP:SC: Received PBKDF param request + [1651743348.201280][5072:5072] CHIP:SC: Peer assigned session ID 14881 + [1651743348.201349][5072:5072] CHIP:SC: Found MRP parameters in the message + [1651743348.201520][5072:5072] CHIP:SC: Including MRP parameters in PBKDF param response + [1651743348.201884][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2ef78 to 0x0000000000000000 (0) of type 0x21 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159088. + [1651743348.201989][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2ef78 with MessageCounter:2627159088 to 0x0000000000000000 at monotonic time: 0000000000FF6731 msec + [1651743348.202196][5072:5072] CHIP:SC: Sent PBKDF param response + [1651743348.298384][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 + [1651743348.299274][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 + [1651743348.300132][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 + [1651743348.300571][5072:5072] CHIP:EM: Received message of type 0x22 with protocolId (0, 0) and MessageCounter:3306320357 on exchange 29381r + [1651743348.300655][5072:5072] CHIP:EM: Found matching exchange: 29381r, Delegate: 0xaaaab7bb2a90 + [1651743348.300741][5072:5072] CHIP:SC: Received spake2p msg1 + [1651743348.304696][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2ee58 to 0x0000000000000000 (0) of type 0x23 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159089. + [1651743348.304817][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2ee58 with MessageCounter:2627159089 to 0x0000000000000000 at monotonic time: 0000000000FF6798 msec + [1651743348.305007][5072:5072] CHIP:SC: Sent spake2p msg2 + [1651743348.444144][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 + [1651743348.444992][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 + [1651743348.445608][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 + [1651743348.445888][5072:5072] CHIP:EM: Received message of type 0x24 with protocolId (0, 0) and MessageCounter:3306320358 on exchange 29381r + [1651743348.445943][5072:5072] CHIP:EM: Found matching exchange: 29381r, Delegate: 0xaaaab7bb2a90 + [1651743348.446001][5072:5072] CHIP:SC: Received spake2p msg3 + [1651743348.446130][5072:5072] CHIP:SC: Sending status report. Protocol code 0, exchange 29381 + [1651743348.446202][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2eea8 to 0x0000000000000000 (0) of type 0x40 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159090. + [1651743348.446262][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2eea8 with MessageCounter:2627159090 to 0x0000000000000000 at monotonic time: 0000000000FF6825 msec + [1651743348.446452][5072:5072] CHIP:IN: New secure session created for device , LSID:2138 PSID:14881! + [1651743348.446962][5072:5072] CHIP:SVR: Commissioning completed session establishment step disabled: true - - - label: "Step 3a: TH starts SoftAP and begin matter announcement procedure" - PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope - SoftAP commissioning not currently supported on TH=all-clusters-app - disabled: true - + - label: - "Step 3b: 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 not currently supported on TH=all-clusters-app - disabled: true - - - label: - "Step 3c: TH is configured with the default channel to be Channel 6 in + "Step 3a: TH is configured with the default channel to be Channel 6 in 2.4GHz. If TH has a 5GHz Wi-Fi radio, TH is configured with an additional channel list that includes Channel 44 and the operating channel Wi-Fi network the DUT is on if it is operating in non-ETSI @@ -190,49 +180,64 @@ tests: regulatory domains." PICS: MCORE.DD.DISCOVERY_PAF verification: | + WIFI - PAF feature is out of scope for V1.4 TH must start sending Wi-Fi PAF Publish Frames on the default channel and the channel list. 2.4g - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 5g - FCC - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=5220 5g ETSI - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=5745 disabled: true - - label: "Step 3d: DUT starts Wi-Fi PAF scan in its commissioning channel" + - label: "Step 3b: DUT starts Wi-Fi PAF scan in its commissioning channel" PICS: MCORE.DD.DISCOVERY_PAF verification: | + WIFI - PAF feature is out of scope for V1.4 + DUT must find TH and provide onboarding data to for validation. Pass Criteria: DUT is able to report the Onboarding payload as set on TH $ sudo ./chip-tool pairing wifipaf-wifi 1 n_m_2g nxp12345 20202021 3840 disabled: true - - label: "Step 4a: DUT scans using Wi-Fi in background" + - label: "Step 4a: TH starts SoftAP and begin matter announcement procedure" PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported on TH=all-clusters-app + Out of Scope : SoftAP commissioning currently not supported disabled: true - - label: "Step 4b: TH starts SoftAP and begin matter announcement procedure" + - 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" + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning currently not supported + disabled: true + + - label: "Step 5a: DUT scans using Wi-Fi in background" PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported on TH=all-clusters-app + Out of Scope : SoftAP commissioning currently not supported disabled: true - - label: - "Step 4c: DUT must find TH and provide onboarding data for + - label: "Step 5b: TH starts SoftAP and begin matter announcement procedure" + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning currently not supported + disabled: true + - label: + "Step 5c: DUT must find TH and provide onboarding data for validation.Pass Criteria: DUT is able to report the Onboarding payload as set on TH" PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported on TH=all-clusters-app - disabled: true + Out of Scope : SoftAP commissioning currently not supported + disabled: true - label: - "Step 5: With DUT and TH connected to the same network over IP, DUT + "Step 6: With DUT and TH connected to the same network over IP, DUT performs service discovery using DNS-SD" verification: | - 1. TH is in commissioning mode and discoverable by DUT over IP through DNS-SD advertisements. This can also be verified using through the DUT's pairing command over IP. + TH is in commissioning mode and discoverable by DUT over IP through DNS-SD advertisements. + This can also be verified using through the DUT's pairing command over IP. Verify in TH as commissionee side: $ ./out/all-clusters-app/chip-all-clusters-app diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index 0d4a13790f4f62..bedc7fe9473d67 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -118,16 +118,65 @@ tests: disabled: true - label: - "Step 2a: Standard Commissioning Flow: Use a Commissionee with a QR + "Step 2a: Standard Commissioning Flow: Use a Commissionee with a QR code that has + the Custom Flow field set to 0 and supports Wi-Fi PAF for its Discovery Capability. + Ensure the Version bit string follows the current Matter spec. documentation." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 0 --capabilities 8 + [1719392550.248867][1563:1563] CHIP:SVR: SetupQRCode: [MT:-24J0M3810KA0648G00] + [1719392550.248883][1563:1563] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1719392550.248892][1563:1563] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0M3810KA0648G00 + [1719392550.248911][1563:1563] CHIP:SVR: Manual pairing code: [34970112332] + disabled: true + - label: + "Step 2b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + + $ sudo ./chip-tool payload parse-setup-payload MT:-24J0M3810KA0648G00 + + [1719392883.120482][28468:28468] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs + [1719392883.120687][28468:28468] CHIP:SPL: Parsing base38Representation: MT:-24J0M3810KA0648G00 + [1719392883.120839][28468:28468] CHIP:SPL: Version: 0 + [1719392883.120859][28468:28468] CHIP:SPL: VendorID: 65521 + [1719392883.120874][28468:28468] CHIP:SPL: ProductID: 32769 + [1719392883.120890][28468:28468] CHIP:SPL: Custom flow: 0 (STANDARD) + [1719392883.120910][28468:28468] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) + [1719392883.120928][28468:28468] CHIP:SPL: Long discriminator: 3840 (0xf00) + [1719392883.120944][28468:28468] CHIP:SPL: Passcode: 20202021 disabled: true + + - label: + "Step 2c: Using the DUT, parse the TH’s QR code and follow any steps needed for the + Commissioner/Commissionee to complete the commissioning process using Wi-Fi PAF" + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + + [Verification command to be filled by NXP] + + $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 + MT:-24J0M3810KA0648G00 + - label: + "Step 3a: Standard Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports IP Network for its Discovery Capability and is already on the same IP network as the DUT commissioner. Ensure the Version bit string follows the current Matter spec. documentation." PICS: MCORE.DD.DISCOVERY_IP verification: | + Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports IP Network for its Discovery Capability, + and is already on the same IP network as the DUT commissioner. Ensure the Version bit string follows the current Matter + specification documentation. + ./chip-all-clusters-app --custom-flow 0 --capabilities 4 - Verifiy on TH(ALL-CLUSTER-APP): + On the TH (All-Clusters App), verify that the user + has a QR code available to pass into the DUT [1651105420.610637][27312:27312] CHIP:DL: Device Configuration: [1651105420.610695][27312:27312] CHIP:DL: Serial Number: TEST_SN [1651105420.610727][27312:27312] CHIP:DL: Vendor Id: 65521 (0xFFF1) @@ -141,22 +190,26 @@ tests: [1651105420.610962][27312:27312] CHIP:SVR: SetupQRCode: [MT:-24J0AFN00KA0648G00] disabled: true - - label: "Step 2b: Scan the QR code from the previous step using the DUT." + - label: "Step 3b: 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: - "Step 2c: Using the DUT, parse the THs QR code and follow any steps + "Step 3c: Using the DUT, parse the THs QR code and follow any steps needed for the Commissioner/Commissionee to complete the commissioning process using IP Network" PICS: MCORE.DD.DISCOVERY_IP verification: | - Verify on the DUT (CHIP-TOOL): - ./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00 + Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the + Commissioner/Commissionee commissioning process via IP Network. + + On DUT (CHIP-TOOL), run the following command: + + ./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00 + The DUT successfully parses the QR code and commissions the TH onto the Matter network. [1651105530854] [95067:65607294] CHIP: [CTL] Received CommissioningComplete response [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' @@ -165,77 +218,36 @@ tests: [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' [1651105530854] [95067:65607294] CHIP: [TOO] Device commissioning completed with success - Verifiy on TH(ALL-CLUSTER-APP): + On TH (ALL-CLUSTERS-APP), Ensure the following log output [1651105530.973166][27371:27371] CHIP:SVR: Commissioning completed successfully [1651105530.973215][27371:27371] CHIP:DIS: Updating services using commissioning mode 0 disabled: true - - label: "Step 2d: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - 1. User has a QR code to pass into DUT - - # ./chip-all-clusters-app --wifi --wifipaf --custom-flow 0 --capabilities 8 - [1719392550.248867][1563:1563] CHIP:SVR: SetupQRCode: [MT:-24J0M3810KA0648G00] - [1719392550.248883][1563:1563] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1719392550.248892][1563:1563] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0M3810KA0648G00 - [1719392550.248911][1563:1563] CHIP:SVR: Manual pairing code: [34970112332] - disabled: true - - - label: "Step 2e: Verify the QR code has been scanned successfully." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - 1. Verify the QR code has been scanned successfully. - - $ sudo ./chip-tool payload parse-setup-payload MT:-24J0M3810KA0648G00 - [1719392883.120482][28468:28468] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs - [1719392883.120687][28468:28468] CHIP:SPL: Parsing base38Representation: MT:-24J0M3810KA0648G00 - [1719392883.120839][28468:28468] CHIP:SPL: Version: 0 - [1719392883.120859][28468:28468] CHIP:SPL: VendorID: 65521 - [1719392883.120874][28468:28468] CHIP:SPL: ProductID: 32769 - [1719392883.120890][28468:28468] CHIP:SPL: Custom flow: 0 (STANDARD) - [1719392883.120910][28468:28468] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) - [1719392883.120928][28468:28468] CHIP:SPL: Long discriminator: 3840 (0xf00) - [1719392883.120944][28468:28468] CHIP:SPL: Passcode: 20202021 - disabled: true - - - label: - "Step 2f: Using the DUT, parse the TH’s QR code and follow any steps - needed for the Commissioner/Commissionee to complete the commissioning - process using Wi-Fi PAF" - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - 1. DUT parses QR code and DUT commissions TH to the Matter network - - $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0M3810KA0648G00 - disabled: true - - label: - "Step 3a: Standard Commissioning Flow: Use a Commissionee with a QR + "Step 4a: Standard Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 0 and supports SoftAP for its Discovery Capability. Ensure the Version bit string follows the current Matter spec. documentation." PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported + Out of Scope : SoftAP commissioning not currently supported disabled: true - - label: "Step 3b: Scan the QR code from the previous step using the DUT." + - label: "Step 4b: Scan the QR code from the previous step using the DUT." PICS: MCORE.DD.SCAN_QR_CODE verification: | - Out of Scope + Out of Scope : SoftAP commissioning not currently supported SoftAP commissioning not currently supported - 1. Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes + Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes disabled: true - label: - "Step 3c: Using the DUT, parse the THs QR code and follow any steps + "Step 4c: Using the DUT, parse the THs QR code and follow any steps needed for the Commissioner/Commissionee to complete the commissioning process using SoftAP" PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope - SoftAP commissioning not currently supported + verification: | + Out of Scope : SoftAP commissioning not currently supported + disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml index 6dd289efd377aa..44afbf24e785e8 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml @@ -68,10 +68,12 @@ tests: 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 1, 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 --capabilities 2 --custom-flow 1 --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 --custom-flow 1 --ble-device 1 - ... [1657234110.765249][370717:370717] CHIP:SVR: SetupQRCode: [MT:-24J0YXE00KA0648G00] [1657234110.765314][370717:370717] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: [1657234110.765364][370717:370717] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0YXE00KA0648G00 @@ -80,9 +82,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: "Step 1c: DUT parses QR code." @@ -102,11 +103,14 @@ tests: commissioning process using BLE." PICS: MCORE.DD.DISCOVERY_BLE verification: | - Verifiy on TH(ALL-CLUSTER-APP): + 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: [1651101988.943015][23212:23212] CHIP:SVR: Commissioning completed successfully [1651101988.943058][23212:23212] CHIP:DIS: Updating services using commissioning mode 0 - Verify on the DUT (CHIP-TOOL): + On TH (ALL-CLUSTER-APP), Ensure the following log output: ./chip-tool pairing code 1 MT:-24J0YXE00KA0648G00 [1657234147237] [31454:16822562] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' [1657234147237] [31454:16822562] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' @@ -114,32 +118,86 @@ tests: [1657234147237] [31454:16822562] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' [1657234147237] [31454:16822562] CHIP: [TOO] Device commissioning completed with success disabled: true + - label: + "Step 2a: User-Intent Commissioning Flow: Use a Commissionee with a QR code that has the + Custom Flow field set to 1 and supports Wi-Fi PAF for its Discovery Capability. Commissionee is NOT in commissioning mode. Ensure the Version bit string follows the current Matter spec. documentation. " + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + + # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 1 --capabilities 8 + [1719393010.693198][1592:1592] CHIP:SVR: SetupQRCode: [MT:-24J0IJ910KA0648G00] + [1719393010.693213][1592:1592] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1719393010.693222][1592:1592] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0IJ910KA0648G00 + [1719393010.693246][1592:1592] CHIP:SVR: Manual pairing code: [749701123365521327694] + disabled: true + + - label: "Step 2b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + disabled: true + + - label: "Step 2c: DUT parses QR code." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + + $ sudo ./chip-tool payload parse-setup-payload MT:-24J0IJ910KA0648G00 + [1719393067.811966][28514:28514] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs + [1719393067.812195][28514:28514] CHIP:DL: writing settings to file (/tmp/chip_tool_kvs-PRUpuW) + [1719393067.812351][28514:28514] CHIP:DL: renamed tmp file to file (/tmp/chip_tool_kvs) + [1719393067.812455][28514:28514] CHIP:SPL: Parsing base38Representation: MT:-24J0IJ910KA0648G00 + [1719393067.812626][28514:28514] CHIP:SPL: Version: 0 + [1719393067.812647][28514:28514] CHIP:SPL: VendorID: 65521 + [1719393067.812664][28514:28514] CHIP:SPL: ProductID: 32769 + [1719393067.812679][28514:28514] CHIP:SPL: Custom flow: 1 (USER ACTION REQUIRED) + [1719393067.812698][28514:28514] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) + [1719393067.812714][28514:28514] CHIP:SPL: Long discriminator: 3840 (0xf00) + [1719393067.812729][28514:28514] CHIP:SPL: Passcode: 20202021 + disabled: true - label: - "Step 2a: User-Intent Commissioning Flow: Use a Commissionee with a QR + "Step 2d: User should follow any TH-specific steps for putting the TH Commissionee device into commissioning + mode and to complete the commissioning process using Wi-Fi PAF." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0IJ910KA0648G00 + disabled: true + + - label: + "Step 3a: User-Intent Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 1 and supports IP Network for its Discovery Capability. Commissionee is NOT in commissioning mode. Ensure the Version bit string follows the current Matter spec. documentation." PICS: MCORE.DD.DISCOVERY_IP verification: | - Verifiy on TH(ALL-CLUSTER-APP): - ./chip-all-clusters-app --custom-flow 1 --capabilities 4 + Use a Commissionee with a QR code that has the Custom Flow field set to 1, supports + IP Network for its Discovery Capability, and is already on the same IP network as the DUT + commissioner. Ensure the Version bit string follows the current Matter specification documentation. + ./chip-all-clusters-app --custom-flow 1 --capabilities 4 + On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT [1660353382.200125][249074:249074] CHIP:SVR: SetupQRCode: [MT:-24J029Q00KA0648G00] [1660353382.200152][249074:249074] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: [1660353382.200173][249074:249074] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J029Q00KA0648G00 disabled: true - - label: "Step 2b: Scan the QR code from the previous step using the DUT." + - label: "Step 3b: 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: "Step 2c: DUT parses QR code." + - label: "Step 3c: DUT parses QR code." PICS: MCORE.DD.DISCOVERY_IP verification: | 1. Parse the payload of the TH commissionee @@ -151,16 +209,18 @@ tests: disabled: true - label: - "Step 2d: User should follow any TH-specific steps for putting the TH + "Step 3d: User should follow any TH-specific steps for putting the TH Commissionee device into commissioning mode and to complete the commissioning process using IP Network." PICS: MCORE.DD.DISCOVERY_IP verification: | - Verifiy on TH(ALL-CLUSTER-APP): + Using the DUT, parse the QR code generated by the TH and follow the necessary steps to + complete the Commissioner/Commissionee commissioning process via IP Network. + On TH (ALL-CLUSTERS-APP), Ensure the following log output [1657234324.992098][370755:370755] CHIP:SVR: Commissioning completed successfully [1657234324.992146][370755:370755] CHIP:DIS: Updating services using commissioning mode 0 - Verify on the DUT (CHIP-TOOL): + On DUT (CHIP-TOOL), run the following command: ./chip-tool pairing code 1 MT:-24J029Q00KA0648G00 [1657234324847] [31475:16824564] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' [1657234324847] [31475:16824564] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' @@ -170,85 +230,35 @@ tests: disabled: true - label: - "Step 2e: User-Intent Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 1 and supports Wi-Fi PAF - for its Discovery Capability. " - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - User has a QR code to pass into DUT. - # ./chip-all-clusters-app --wifi --wifipaf --custom-flow 1 --capabilities 8 - [1719393010.693198][1592:1592] CHIP:SVR: SetupQRCode: [MT:-24J0IJ910KA0648G00] - [1719393010.693213][1592:1592] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1719393010.693222][1592:1592] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0IJ910KA0648G00 - [1719393010.693246][1592:1592] CHIP:SVR: Manual pairing code: [749701123365521327694] - disabled: true - - - label: "Step 2f: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - Verify the QR code has been scanned successfully. - disabled: true - - - label: "Step 2g: DUT parses QR code." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - Verify DUT has parsed the QR code. Verify TH has not been commissioned to the Matter network. - $ sudo ./chip-tool payload parse-setup-payload MT:-24J0IJ910KA0648G00 - [1719393067.811966][28514:28514] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs - [1719393067.812195][28514:28514] CHIP:DL: writing settings to file (/tmp/chip_tool_kvs-PRUpuW) - [1719393067.812351][28514:28514] CHIP:DL: renamed tmp file to file (/tmp/chip_tool_kvs) - [1719393067.812455][28514:28514] CHIP:SPL: Parsing base38Representation: MT:-24J0IJ910KA0648G00 - [1719393067.812626][28514:28514] CHIP:SPL: Version: 0 - [1719393067.812647][28514:28514] CHIP:SPL: VendorID: 65521 - [1719393067.812664][28514:28514] CHIP:SPL: ProductID: 32769 - [1719393067.812679][28514:28514] CHIP:SPL: Custom flow: 1 (USER ACTION REQUIRED) - [1719393067.812698][28514:28514] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) - [1719393067.812714][28514:28514] CHIP:SPL: Long discriminator: 3840 (0xf00) - [1719393067.812729][28514:28514] CHIP:SPL: Passcode: 20202021 - disabled: true - - - label: - "Step 2h: User should follow any TH-specific steps for putting the TH - Commissionee device into commissioning mode and to complete the - commissioning process using Wi-Fi PAF." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - DUT commissions TH to the Matter network. - $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0IJ910KA0648G00 - disabled: true - - - label: - "Step 3a: User-Intent Commissioning Flow: Use a Commissionee with a QR + "Step 4a: User-Intent Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 1 and supports SoftAP for its Discovery Capability. Commissionee is NOT in commissioning mode. Ensure the Version bit string follows the current Matter spec. documentation." PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported + Out of Scope : SoftAP commissioning currently not supported disabled: true - - label: "Step 3b: Scan the QR code from the previous step using the DUT." + - label: "Step 4b: Scan the QR code from the previous step using the DUT." PICS: MCORE.DD.SCAN_QR_CODE verification: | - Out of Scope - SoftAP commissioning not currently supported + Out of Scope : SoftAP commissionin currently not supported + Verify the QR code is scanned by DUT, chip-tool does not support + physically scanning QR codes disabled: true - - label: "Step 3c: DUT parses QR code." + - label: "Step 4c: DUT parses QR code." PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported + Out of Scope : SoftAP commissioning currently not supported disabled: true - label: - "Step 3d: User should follow any TH-specific steps for putting the TH + "Step 4d: User should follow any TH-specific steps for putting the TH Commissionee device into commissioning mode and to complete the commissioning process using SoftAP." PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported + Out of Scope : SoftAP commissioning currently not supported disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml index b55f04244aa6be..6f12e7d72d7564 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml @@ -68,9 +68,11 @@ tests: documentation." PICS: MCORE.DD.DISCOVERY_BLE verification: | - Verify on the TH (All-cluster-app) - ./chip-all-clusters-app --custom-flow 2 --capabilities 2 - + Use a Commissionee with a QR code that has the Custom Flow field set to 2, + 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 2 --capabilities 2 + On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT [1657235055.253604][370941:370941] CHIP:-: ==== Onboarding payload for Custom Commissioning Flows ==== [1657235055.253688][370941:370941] CHIP:SVR: SetupQRCode: [MT:-24J0YXE00KA0648G00] [1657235055.253736][370941:370941] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: @@ -80,8 +82,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: "Step 1c: DUT parses QR code." @@ -111,26 +113,87 @@ tests: commissioning process using BLE." PICS: MCORE.DD.DISCOVERY_BLE verification: | - Verify on the TH (All-cluster-app) + 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 TH (ALL-CLUSTER-APP), Ensure the following log output + [1657235088.040328][370941:370941] CHIP:SVR: Commissioning completed successfully [1657235088.040371][370941:370941] CHIP:DIS: Updating services using commissioning mode 0 - Verify on the DUT (Chip-tool): + On DUT (CHIP-TOOL), run the following command: ./chip-tool pairing code 1 MT:-24J0YXE00KA0648G00 [1657235087918] [31502:16832693] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' [1657235087918] [31502:16832693] CHIP: [TOO] Device commissioning completed with success disabled: true +- label: + "Step 2a: Custom Commissioning Flow: Use a Commissionee with a QR code + that has the Custom Flow field set to 2 and supports Wi-Fi PAF for its + Discovery Capability. Commissionee is NOT in commissioning mode. + Ensure the Version bit string follows the current Matter spec. + documentation." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 2 --capabilities 8 + [1719393349.405047][1623:1623] CHIP:SVR: SetupQRCode: [MT:-24J0EZA10KA0648G00] + [1719393349.405062][1623:1623] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1719393349.405071][1623:1623] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0EZA10KA0648G00 + [1719393349.405095][1623:1623] CHIP:SVR: Manual pairing code: [749701123365521327694] + disabled: true + + - label: "Step 2b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + WIFI - PAF feature is out of scope for V1.4 + + [Verification command to be filled by NXP] + disabled: true + + - label: "Step 2c: DUT parses QR code." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + $ sudo ./chip-tool payload parse-setup-payload MT:-24J0EZA10KA0648G00 + CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs + CHIP:DL: writing settings to file (/tmp/chip_tool_kvs-UQIGvf) + CHIP:DL: renamed tmp file to file (/tmp/chip_tool_kvs) + CHIP:SPL: Parsing base38Representation: MT:-24J0EZA10KA0648G00 + CHIP:SPL: Version: 0 + CHIP:SPL: VendorID: 65521 + CHIP:SPL: ProductID: 32769 + CHIP:SPL: Custom flow: 2 (CUSTOM) + CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) + CHIP:SPL: Long discriminator: 3840 (0xf00) + CHIP:SPL: Passcode: 20202021 + + disabled: true - label: - "Step 2a: Custom Commissioning Flow: Use a Commissionee with a QR code + "Step 2d: User should follow any TH-specific steps, unless the DUT has + alternative means to guide the user to successful commissioning, for + putting the TH Commissionee into commissioning mode, for triggering + the DUT Commissioner for commissioning, and for completing the + commissioning process using BLE." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0EZA10KA0648G00 + disabled: true + + - label: + "Step 3a: Custom Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 2 and supports IP Network for its Discovery Capability. Commissionee is NOT in commissioning mode. Ensure the Version bit string follows the current Matter spec. documentation." PICS: MCORE.DD.DISCOVERY_IP verification: | - Verify on the TH (All-cluster-app) + Use a Commissionee with a QR code that has the Custom Flow field set to 2, supports IP Network for its Discovery Capability, and is already on the same IP network as the DUT commissioner. Ensure the Version bit string follows the current Matter specification documentation. ./chip-all-clusters-app --custom-flow 2 --capabilities 4 + On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT [1657235141.663008][370963:370963] CHIP:-: ==== Onboarding payload for Custom Commissioning Flows ==== [1657235141.663082][370963:370963] CHIP:SVR: SetupQRCode: [MT:-24J029Q00KA0648G00] @@ -138,14 +201,14 @@ tests: [1657235141.663189][370963:370963] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J029Q00KA0648G00 disabled: true - - label: "Step 2b: Scan the QR code from the previous step using the DUT." + - label: "Step 3b: 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: "Step 2c: DUT parses QR code." + - label: "Step 3c: DUT parses QR code." PICS: MCORE.DD.DISCOVERY_IP verification: | 1. Parse the payload of the TH commissionee @@ -165,14 +228,17 @@ tests: disabled: true - label: - "Step 2d: User should follow any TH-specific steps, unless the DUT has + "Step 3d: User should follow any TH-specific steps, unless the DUT has alternative means to guide the user to successful commissioning, for putting the TH Commissionee into commissioning mode, for triggering the DUT Commissioner for commissioning, and for completing the commissioning process using IP Network." PICS: MCORE.DD.DISCOVERY_IP verification: | - Verify on the TH (All-cluster-app) + Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the + Commissioner/Commissionee commissioning process via IP Network. + + On TH (ALL-CLUSTERS-APP), Ensure the following log output [1657235198.977848][370963:370963] CHIP:SVR: Commissioning completed successfully [1657235198.977943][370963:370963] CHIP:DIS: Updating services using commissioning mode 0 @@ -183,92 +249,36 @@ tests: disabled: true - label: - "Step 2e: Custom Commissioning Flow: Use a Commissionee with a QR code - that has the Custom Flow field set to 2 and supports Wi-Fi PAF for its - Discovery Capability. Commissionee is NOT in commissioning mode. - Ensure the Version bit string follows the current Matter spec. - documentation." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - 1. User has a QR code to pass into DUT. - # ./chip-all-clusters-app --wifi --wifipaf --custom-flow 2 --capabilities 8 - [1719393349.405047][1623:1623] CHIP:SVR: SetupQRCode: [MT:-24J0EZA10KA0648G00] - [1719393349.405062][1623:1623] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1719393349.405071][1623:1623] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0EZA10KA0648G00 - [1719393349.405095][1623:1623] CHIP:SVR: Manual pairing code: [749701123365521327694] - disabled: true - - - label: "Step 2f: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - 1. Verify the QR code has been scanned successfully. - disabled: true - - - label: "Step 2g: DUT parses QR code." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - 1. Verify DUT has parsed the QR code. Verify TH has not been commissioned to the Matter network. - $ sudo ./chip-tool payload parse-setup-payload MT:-24J0EZA10KA0648G00 - CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs - CHIP:DL: writing settings to file (/tmp/chip_tool_kvs-UQIGvf) - CHIP:DL: renamed tmp file to file (/tmp/chip_tool_kvs) - CHIP:SPL: Parsing base38Representation: MT:-24J0EZA10KA0648G00 - CHIP:SPL: Version: 0 - CHIP:SPL: VendorID: 65521 - CHIP:SPL: ProductID: 32769 - CHIP:SPL: Custom flow: 2 (CUSTOM) - CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) - CHIP:SPL: Long discriminator: 3840 (0xf00) - CHIP:SPL: Passcode: 20202021 - - disabled: true - - - label: - "Step 2h: User should follow any TH-specific steps, unless the DUT has - alternative means to guide the user to successful commissioning, for - putting the TH Commissionee into commissioning mode, for triggering - the DUT Commissioner for commissioning, and for completing the - commissioning process using BLE." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - 1. DUT commissions TH to the Matter network. - $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0EZA10KA0648G00 - disabled: true - - - label: - "Step 3a: Custom Commissioning Flow: Use a Commissionee with a QR code + "Step 4a: Custom Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 2 and supports SoftAP for its Discovery Capability. Commissionee is NOT in commissioning mode. Ensure the Version bit string follows the current Matter spec. documentation." PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported + Out of Scope : SoftAP commissioning currently not supported disabled: true - - label: "Step 3b: Scan the QR code from the previous step using the DUT." + - label: "Step 4b: Scan the QR code from the previous step using the DUT." PICS: MCORE.DD.SCAN_QR_CODE verification: | - Out of Scope - SoftAP commissioning not currently supported + Out of Scope : SoftAP commissioning currently not supported + Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes disabled: true - - label: "Step 3c: DUT parses QR code." + - label: "Step 4c: DUT parses QR code." PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported + Out of Scope : SoftAP commissioning currently not supported disabled: true - label: - "Step 3d: User should follow any TH-specific steps, unless the DUT has + "Step 4d: User should follow any TH-specific steps, unless the DUT has alternative means to guide the user to successful commissioning, for putting the TH Commissionee into commissioning mode, for triggering the DUT Commissioner for commissioning, and for completing the commissioning process using SoftAP." PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope - SoftAP commissioning not currently supported + Out of Scope : SoftAP commissioning currently not supported disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml index c269e0c66d4485..15df10e38027d1 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml @@ -61,9 +61,11 @@ tests: - label: "Step 1: Locate and scan/read the Commissionees QR code using DUT" verification: | - Verify on the TH (All-cluster-app) - ./chip-all-clusters-app --version 0 --vendor-id 0xFFF1 --product-id 0x8001 --custom-flow 2 --capabilities 4 --discriminator 3840 --passcode 20202021 - + Locate the Commissionee’s QR code and scan/read it using the DUT. Ensure the DUT successfully scans/reads the QR code. + Execute the following command on the TH: + + ./chip-all-clusters-app --version 0 --vendor-id 0xFFF1 --product-id 0x8001 --custom-flow 2 --capabilities 4 --discriminator 3840 --passcode 20202021 + Expected logs on the TH: [1657235470.970680][371041:371041] CHIP:DL: Device Configuration: [1657235470.970772][371041:371041] CHIP:DL: Serial Number: (not set) [1657235470.970811][371041:371041] CHIP:DL: Vendor Id: 65521 (0xFFF1) @@ -77,6 +79,7 @@ tests: [1657235470.971199][371041:371041] CHIP:SVR: SetupQRCode: [MT:-24J029Q00KA0648G00] [1657235470.971258][371041:371041] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: [1657235470.971293][371041:371041] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J029Q00KA0648G00 + Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes disabled: true - label: @@ -84,9 +87,11 @@ tests: new QR code but substituting out the current Version String with an invalid Version String (i.e. '010' or any non-zero 3-bit value)" verification: | - 1. Use chip-tool's "payload generate-qrcode" command to help generate the new, invalid QR code - Verify on the TH (All-cluster-app) - ./chip-tool payload generate-qrcode --existing-payload MT:-24J029Q00KA0648G00 --allow-invalid-payload 1 --version 2 + Using the chip-tool, execute the following command to create a new QR code with an invalid version string ('010' or any non-zero 3-bit value): + + Use chip-tool's "payload generate-qrcode" command to help generate the new, invalid QR code + ./chip-tool payload generate-qrcode --existing-payload MT:-24J029Q00KA0648G00 --allow-invalid-payload 1 --version 2 + Expected Logs on the TH: [1657235626568] [31698:16839018] CHIP: [TOO] QR Code: MT:034J029Q00KA0648G00 disabled: true @@ -94,13 +99,14 @@ tests: "Step 2b: Scan/read the QR code, generated in the previous step, using the DUT" verification: | - Verify on the DUT (Chip-tool): + Execute the following command on the DUT(chip-tool) to parse the QR code generated in the previous step: ./chip-tool pairing code 1 MT:-034J029Q00KA0648G00 - + The commissioning process should terminate as per the DUT-specific instructions due to the invalid version string. + Observe the following error in the DUT logs: Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - No applicable TH Logs + No applicable logs will be generated on the TH (All-cluster-app), as the commissioning process does not proceed. disabled: true - label: @@ -109,23 +115,66 @@ tests: OnNetwork discovery capability)" PICS: MCORE.DD.DISCOVERY_BLE verification: | - 1. Use chip-tool's "payload generate-qrcode" command to help generate the new, invalid QR code - Verify on the TH (All-cluster-app) - ./chip-tool payload generate-qrcode --existing-payload MT:-24J029Q00KA0648G00 --allow-invalid-payload 1 --rendezvous 4 + Modify the QR code from Step 1 by ensuring the Discovery Capability bit string excludes BLE and is set to OnNetwork discovery capability. + Use the following command to generate the QR code: + + Use chip-tool's "payload generate-qrcode" command to help generate the new, invalid QR code + + ./chip-tool payload generate-qrcode --existing-payload MT:-24J029Q00KA0648G00 --allow-invalid-payload 1 --rendezvous 4 + Expected Logs on the TH: + [1657235754393] [31702:16840391] CHIP: [TOO] QR Code: MT:-24J029Q00KA0648G00 - Verify on the DUT (Chip-tool): - No applicable logs on the DUT side + Ensure the TH logs reflect the QR code during the commissioning process and Use the new QR code payload MT:-24J029Q00KA0648G00 + and pass it into the DUT for further processing. disabled: true - label: "Step 3b: Scan/read the QR code of the TH device using the DUT" PICS: MCORE.DD.DISCOVERY_BLE verification: | - Verify on the DUT (Chip-tool): + On the DUT (Chip-tool), execute the pairing command using the provided QR code to initiate the commissioning process: + ./chip-tool pairing code 1 MT:-24J029Q00KA0648G00 + + Confirm that the DUT discovers the TH device over the OnNetwork capability (and not BLE). + + Check the logs on the DUT to verify that the commissioning process is proceeding over OnNetwork. The expected log should reflect discovery via DNS-SD (Domain Name System Service Discovery) rather than BLE and After successful discovery, the commissioning process should proceed, and you should see a success message confirming that the device was successfully commissioned over OnNetwork. + [1657235905214] [31706:16841970] CHIP: [CTL] Discovered device to be commissioned over DNS-SD - ... - [1657235906071] [31706:16841969] CHIP: [TOO] Device commissioning completed with success + [1657235906071] [31706:16841969] CHIP: [TOO] Device commissioning completed with success + disabled: true + - label: + "Step 4a: Using the QR code from Step 1, ensure the TH’s Discovery + Capability bit string is NOT set to Wi-Fi PAF for discovery (i.e. set + to OnNetwork discovery capability)" + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + + [Verification command to be filled by NXP] + + User has a QR code generated to pass into DUT. Using the example provided above, the payload would be "MT:-24J029Q00KA0648G00". + $ ./out/all-clusters-app/chip-all-clusters-app --version 0 --vendor-id 0xFFF1 --product-id 0x8001 --custom-flow 2 --capabilities 4 --discriminator 3840 --passcode 20202021 + [1657235470.970680][371041:371041] CHIP:DL: Device Configuration: + [1657235470.970772][371041:371041] CHIP:DL: Serial Number: (not set) + [1657235470.970811][371041:371041] CHIP:DL: Vendor Id: 65521 (0xFFF1) + [1657235470.970845][371041:371041] CHIP:DL: Product Id: 32769 (0x8001) + [1657235470.970892][371041:371041] CHIP:DL: Hardware Version: 0 + [1657235470.970929][371041:371041] CHIP:DL: Setup Pin Code (0 for UNKNOWN/ERROR): 20202021 + [1657235470.970984][371041:371041] CHIP:DL: Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00) + [1657235470.971031][371041:371041] CHIP:DL: Manufacturing Date: (not set) + [1657235470.971095][371041:371041] CHIP:DL: Device Type: 65535 (0xFFFF) + [1657235470.971147][371041:371041] CHIP:-: ==== Onboarding payload for Standard Commissioning Flow ==== + [1657235470.971199][371041:371041] CHIP:SVR: SetupQRCode: [MT:-24J029Q00KA0648G00] + [1657235470.971258][371041:371041] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1657235470.971293][371041:371041] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J029Q00KA0648G00" + disabled: true + + - label: "Step 4b: Scan/read the QR code of the TH device using the DUT" + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] disabled: true - label: @@ -137,7 +186,11 @@ tests: the list: 00000000, 11111111, 22222222, 33333333, 44444444, 55555555, 66666666, 77777777, 88888888, 99999999, 12345678, 87654321" verification: | - No applicable TH or DUT Logs + Using the QR code from Step 1, replace the Passcode component with each of the following invalid passcodes: 00000000, 11111111, 22222222, 33333333, 44444444, 55555555, 66666666, 77777777, 88888888, 99999999, 12345678, and 87654321. + For each invalid passcode, generate a unique QR code, resulting in the following payloads: + Execute the following command on the TH: + + ./chip-tool payload generate-qrcode --existing-payload --allow-invalid-payload 1 --rendezvous 4 "MT:-24J029Q00OC0000000" (00000000), "MT:-24J029Q00KMSP0Z800" (11111111), "MT:-24J029Q00GWID1WH00" (22222222), @@ -150,95 +203,41 @@ tests: "MT:-24J029Q00QPQ36B420" (99999999), "MT:-24J029Q004QG46Y900" (12345678), "MT:-24J029Q00YX018EW10" (87654321) + After generating the QR codes, confirm that they are ready for use by the DUT for further testing. There is no applicable logs from the TH disabled: true - label: "Step 4b: Scan each of the generated QR codes from the previous step using DUT" verification: | - Verify on the DUT (Chip-tool): - No applicable TH Logs - - ./chip-tool pairing code 1 MT:-24J029Q00OC0000000 - - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q00OC0000000 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q00KMSP0Z800 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q00GWID1WH00 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q00C4912TQ00 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q008E.Q2QZ00 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q004ORE3N610 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q000YH24KF10 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q00Y58S4HO10 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q00UF-F5EX10 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q00QPQ36B420 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q004QG46Y900 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - - ./chip-tool pairing code 1 MT:-24J029Q00YX018EW10 - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - disabled: true - - - label: - "Step 4c: Using the QR code from Step 1, ensure the TH’s Discovery - Capability bit string is NOT set to Wi-Fi PAF for discovery (i.e. set - to OnNetwork discovery capability)" - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - User has a QR code generated to pass into DUT. Using the example provided above, the payload would be "MT:-24J029Q00KA0648G00". - $ ./out/all-clusters-app/chip-all-clusters-app --version 0 --vendor-id 0xFFF1 --product-id 0x8001 --custom-flow 2 --capabilities 4 --discriminator 3840 --passcode 20202021 - [1657235470.970680][371041:371041] CHIP:DL: Device Configuration: - [1657235470.970772][371041:371041] CHIP:DL: Serial Number: (not set) - [1657235470.970811][371041:371041] CHIP:DL: Vendor Id: 65521 (0xFFF1) - [1657235470.970845][371041:371041] CHIP:DL: Product Id: 32769 (0x8001) - [1657235470.970892][371041:371041] CHIP:DL: Hardware Version: 0 - [1657235470.970929][371041:371041] CHIP:DL: Setup Pin Code (0 for UNKNOWN/ERROR): 20202021 - [1657235470.970984][371041:371041] CHIP:DL: Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00) - [1657235470.971031][371041:371041] CHIP:DL: Manufacturing Date: (not set) - [1657235470.971095][371041:371041] CHIP:DL: Device Type: 65535 (0xFFFF) - [1657235470.971147][371041:371041] CHIP:-: ==== Onboarding payload for Standard Commissioning Flow ==== - [1657235470.971199][371041:371041] CHIP:SVR: SetupQRCode: [MT:-24J029Q00KA0648G00] - [1657235470.971258][371041:371041] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1657235470.971293][371041:371041] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J029Q00KA0648G00" - disabled: true - - - label: "Step 4d: Scan/read the QR code of the TH device using the DUT" - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - If TH Commissionee’s Discovery Capabilities do not support Wi-Fi PAF, ensure that the DUT commissions the TH onto the Matter network over a capability that is NOT BLE. In this example, over OnNetwork. + Scan each of the 12 QR codes generated in the previous step using the DUT. The DUT should parse the QR code and identify the invalid passcode. + As expected, the DUT will terminate the commissioning process based on the invalid passcode. The DUT should reject the commission and not complete the pairing process. This termination will follow the DUT manufacturer’s specific instructions. + + The following command should be run for each QR code: + Expected failure due to the invalid passcode for each of the generated QR codes: + Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument + + Example for the first QR code: + + ./chip-tool pairing code 1 MT:-24J029Q00OC0000000 + + Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument + + Similarly, repeat the command for the rest of the QR codes: + + MT:-24J029Q00OC0000000 + MT:-24J029Q00KMSP0Z800 + MT:-24J029Q00GWID1WH00 + MT:-24J029Q00C4912TQ00 + MT:-24J029Q008E.Q2QZ00 + MT:-24J029Q004ORE3N610 + MT:-24J029Q000YH24KF10 + MT:-24J029Q00Y58S4HO10 + MT:-24J029Q00UF-F5EX10 + MT:-24J029Q00QPQ36B420 + MT:-24J029Q004QG46Y900 + MT:-24J029Q00YX018EW10 + Ensure that the error message CHIP Error 0x0000002F: Invalid argument appears for each attempt, confirming the DUT has rejected the commissioning. disabled: true - label: @@ -246,15 +245,17 @@ tests: code but substituting out the current Prefix with an invalid Prefix that is not 'MT:' (i.e. Prefix='AB:')" verification: | - AB:-24J029Q00KA0648G00 - - No applicable TH or DUT Logs + Generate a new QR code by replacing the current prefix (MT:) with an invalid prefix (AB:) from step 1, resulting in the + payload AB:-24J029Q00KA0648G00, and ensure the QR code is correctly generated and ready to be passed into the DUT with no applicable TH or DUT logs. + AB:-24J029Q00KA0648G00 disabled: true - label: "Step 5b: Scan/read the QR code, generated in the previous step, using the DUT" verification: | + Scan the QR code generated in the previous step using the DUT, ensuring that the DUT commissioner does not + react successfully to scanning the QR code, and the DUT terminates the commissioning process in a manner specific to the DUT manufacturer's instructions. Verify on the DUT (Chip-tool): ./chip-tool pairing code 1 AB:-24J029Q00KA0648G00 From 3bd829485a1cd9cb23fa1ecf792d408a348cd835 Mon Sep 17 00:00:00 2001 From: Rajashreekalmane Date: Mon, 13 Jan 2025 17:40:59 +0530 Subject: [PATCH 02/13] DD Manual script update --- .../suites/certification/Test_TC_DD_2_1.yaml | 3 ++- .../suites/certification/Test_TC_DD_2_2.yaml | 4 +--- .../suites/certification/Test_TC_DD_3_11.yaml | 20 +++++++++++-------- 3 files changed, 15 insertions(+), 12 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml b/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml index 20f9926cbf4628..152394ee37c210 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml @@ -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 ... diff --git a/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml b/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml index 90f9ff659a5d5b..57dedadebbf69a 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml @@ -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 diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index bedc7fe9473d67..16a37714fb264d 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -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,9 +102,11 @@ 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' @@ -110,7 +114,7 @@ tests: [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 From b3a0f1eb3f6b53a37b165d535153a02dfe0de064 Mon Sep 17 00:00:00 2001 From: Rajashreekalmane Date: Mon, 13 Jan 2025 18:32:39 +0530 Subject: [PATCH 03/13] Resolved indentation errors --- .../suites/certification/Test_TC_DD_2_2.yaml | 2 +- .../suites/certification/Test_TC_DD_3_11.yaml | 53 +++++++++---------- .../suites/certification/Test_TC_DD_3_12.yaml | 1 + .../suites/certification/Test_TC_DD_3_13.yaml | 4 +- .../suites/certification/Test_TC_DD_3_14.yaml | 8 +-- 5 files changed, 34 insertions(+), 34 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml b/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml index 57dedadebbf69a..16275cdfbc1fcc 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml @@ -221,7 +221,7 @@ tests: verification: | Out of Scope : SoftAP commissioning currently not supported disabled: true - - label: + - label: "Step 5c: DUT must find TH and provide onboarding data for validation.Pass Criteria: DUT is able to report the Onboarding payload as set on TH" diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index 16a37714fb264d..9fa0e9294667f3 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -104,8 +104,7 @@ tests: verification: | 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 + ./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' @@ -123,36 +122,36 @@ tests: - label: "Step 2a: Standard Commissioning Flow: Use a Commissionee with a QR code that has - the Custom Flow field set to 0 and supports Wi-Fi PAF for its Discovery Capability. - Ensure the Version bit string follows the current Matter spec. documentation." + the Custom Flow field set to 0 and supports Wi-Fi PAF for its Discovery Capability. + Ensure the Version bit string follows the current Matter spec. documentation." PICS: MCORE.DD.DISCOVERY_PAF verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 0 --capabilities 8 - [1719392550.248867][1563:1563] CHIP:SVR: SetupQRCode: [MT:-24J0M3810KA0648G00] - [1719392550.248883][1563:1563] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1719392550.248892][1563:1563] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0M3810KA0648G00 - [1719392550.248911][1563:1563] CHIP:SVR: Manual pairing code: [34970112332] + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 0 --capabilities 8 + [1719392550.248867][1563:1563] CHIP:SVR: SetupQRCode: [MT:-24J0M3810KA0648G00] + [1719392550.248883][1563:1563] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1719392550.248892][1563:1563] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0M3810KA0648G00 + [1719392550.248911][1563:1563] CHIP:SVR: Manual pairing code: [34970112332] disabled: true + - label: "Step 2b: Scan the QR code from the previous step using the DUT." PICS: MCORE.DD.SCAN_QR_CODE verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - - $ sudo ./chip-tool payload parse-setup-payload MT:-24J0M3810KA0648G00 + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] - [1719392883.120482][28468:28468] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs - [1719392883.120687][28468:28468] CHIP:SPL: Parsing base38Representation: MT:-24J0M3810KA0648G00 - [1719392883.120839][28468:28468] CHIP:SPL: Version: 0 - [1719392883.120859][28468:28468] CHIP:SPL: VendorID: 65521 - [1719392883.120874][28468:28468] CHIP:SPL: ProductID: 32769 - [1719392883.120890][28468:28468] CHIP:SPL: Custom flow: 0 (STANDARD) - [1719392883.120910][28468:28468] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) - [1719392883.120928][28468:28468] CHIP:SPL: Long discriminator: 3840 (0xf00) - [1719392883.120944][28468:28468] CHIP:SPL: Passcode: 20202021 disabled: true + $ sudo ./chip-tool payload parse-setup-payload MT:-24J0M3810KA0648G00 + [1719392883.120482][28468:28468] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs + [1719392883.120687][28468:28468] CHIP:SPL: Parsing base38Representation: MT:-24J0M3810KA0648G00 + [1719392883.120839][28468:28468] CHIP:SPL: Version: 0 + [1719392883.120859][28468:28468] CHIP:SPL: VendorID: 65521 + [1719392883.120874][28468:28468] CHIP:SPL: ProductID: 32769 + [1719392883.120890][28468:28468] CHIP:SPL: Custom flow: 0 (STANDARD) + [1719392883.120910][28468:28468] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) + [1719392883.120928][28468:28468] CHIP:SPL: Long discriminator: 3840 (0xf00) + [1719392883.120944][28468:28468] CHIP:SPL: Passcode: 20202021 disabled: true - label: "Step 2c: Using the DUT, parse the TH’s QR code and follow any steps needed for the @@ -162,9 +161,9 @@ tests: WIFI - PAF feature is out of scope for V1.4 [Verification command to be filled by NXP] - - $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 - MT:-24J0M3810KA0648G00 + + $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 + MT:-24J0M3810KA0648G00 - label: "Step 3a: Standard Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports IP Network for diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml index 44afbf24e785e8..f173a96c8aa2a7 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml @@ -137,6 +137,7 @@ tests: PICS: MCORE.DD.SCAN_QR_CODE verification: | WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml index 6f12e7d72d7564..cb3e0dcc79c49a 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml @@ -125,7 +125,8 @@ tests: [1657235087918] [31502:16832693] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' [1657235087918] [31502:16832693] CHIP: [TOO] Device commissioning completed with success disabled: true -- label: + + - label: "Step 2a: Custom Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 2 and supports Wi-Fi PAF for its Discovery Capability. Commissionee is NOT in commissioning mode. @@ -167,7 +168,6 @@ tests: CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) CHIP:SPL: Long discriminator: 3840 (0xf00) CHIP:SPL: Passcode: 20202021 - disabled: true - label: diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml index 15df10e38027d1..74a52a355c6f19 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml @@ -61,7 +61,7 @@ tests: - label: "Step 1: Locate and scan/read the Commissionees QR code using DUT" verification: | - Locate the Commissionee’s QR code and scan/read it using the DUT. Ensure the DUT successfully scans/reads the QR code. + Locate the Commissionee’s QR code and scan/read it using the DUT. Ensure the DUT successfully scans/reads the QR code. Execute the following command on the TH: ./chip-all-clusters-app --version 0 --vendor-id 0xFFF1 --product-id 0x8001 --custom-flow 2 --capabilities 4 --discriminator 3840 --passcode 20202021 @@ -143,7 +143,8 @@ tests: [1657235905214] [31706:16841970] CHIP: [CTL] Discovered device to be commissioned over DNS-SD [1657235906071] [31706:16841969] CHIP: [TOO] Device commissioning completed with success disabled: true - - label: + + - label: "Step 4a: Using the QR code from Step 1, ensure the TH’s Discovery Capability bit string is NOT set to Wi-Fi PAF for discovery (i.e. set to OnNetwork discovery capability)" @@ -257,8 +258,7 @@ tests: Scan the QR code generated in the previous step using the DUT, ensuring that the DUT commissioner does not react successfully to scanning the QR code, and the DUT terminates the commissioning process in a manner specific to the DUT manufacturer's instructions. Verify on the DUT (Chip-tool): - - ./chip-tool pairing code 1 AB:-24J029Q00KA0648G00 + ./chip-tool pairing code 1 AB:-24J029Q00KA0648G00 [1657236169984] [31732:16844455] CHIP: [TOO] Run command failure: ../../examples/chip-tool/third_party/connectedhomeip/src/setup_payload/ManualSetupPayloadParser.cpp:50: CHIP Error 0x00000013: Integrity check failed No applicable TH Logs From 170d3ad8b128f0a55cf90e646042eca8330f5244 Mon Sep 17 00:00:00 2001 From: Rajashreekalmane Date: Mon, 13 Jan 2025 18:42:37 +0530 Subject: [PATCH 04/13] Resolved indentation --- src/app/tests/suites/certification/Test_TC_DD_3_11.yaml | 2 +- src/app/tests/suites/certification/Test_TC_DD_3_12.yaml | 2 +- src/app/tests/suites/certification/Test_TC_DD_3_13.yaml | 2 +- src/app/tests/suites/certification/Test_TC_DD_3_14.yaml | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index 9fa0e9294667f3..8c7b53cdd6457f 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -104,7 +104,7 @@ tests: verification: | 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 + ./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' diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml index f173a96c8aa2a7..664593793af524 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml @@ -138,7 +138,7 @@ tests: verification: | WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] + [Verification command to be filled by NXP] disabled: true - label: "Step 2c: DUT parses QR code." diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml index cb3e0dcc79c49a..6994c6cb1a76b4 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml @@ -148,7 +148,7 @@ tests: verification: | WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] + [Verification command to be filled by NXP] disabled: true - label: "Step 2c: DUT parses QR code." diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml index 74a52a355c6f19..49b55354e21004 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml @@ -106,7 +106,7 @@ tests: Observe the following error in the DUT logs: Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - No applicable logs will be generated on the TH (All-cluster-app), as the commissioning process does not proceed. + No applicable logs will be generated on the TH (All-cluster-app), as the commissioning process does not proceed. disabled: true - label: From 178d2523c119cba2961e2885681f2fc7b1b27c40 Mon Sep 17 00:00:00 2001 From: Rajashreekalmane Date: Mon, 13 Jan 2025 18:47:26 +0530 Subject: [PATCH 05/13] resolved errors --- src/app/tests/suites/certification/Test_TC_DD_3_11.yaml | 2 +- src/app/tests/suites/certification/Test_TC_DD_3_12.yaml | 2 +- src/app/tests/suites/certification/Test_TC_DD_3_13.yaml | 2 +- src/app/tests/suites/certification/Test_TC_DD_3_14.yaml | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index 8c7b53cdd6457f..ca8ec7782a7801 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -105,7 +105,7 @@ tests: 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. + 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' diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml index 664593793af524..37adf7b3c17ec0 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml @@ -167,7 +167,7 @@ tests: PICS: MCORE.DD.DISCOVERY_PAF verification: | WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] + [Verification command to be filled by NXP] $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0IJ910KA0648G00 disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml index 6994c6cb1a76b4..89c8179451563c 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml @@ -155,7 +155,7 @@ tests: PICS: MCORE.DD.DISCOVERY_PAF verification: | WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] + [Verification command to be filled by NXP] $ sudo ./chip-tool payload parse-setup-payload MT:-24J0EZA10KA0648G00 CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs CHIP:DL: writing settings to file (/tmp/chip_tool_kvs-UQIGvf) diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml index 49b55354e21004..eb0563c33015e5 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml @@ -138,7 +138,7 @@ tests: Confirm that the DUT discovers the TH device over the OnNetwork capability (and not BLE). - Check the logs on the DUT to verify that the commissioning process is proceeding over OnNetwork. The expected log should reflect discovery via DNS-SD (Domain Name System Service Discovery) rather than BLE and After successful discovery, the commissioning process should proceed, and you should see a success message confirming that the device was successfully commissioned over OnNetwork. + Check the logs on the DUT to verify that the commissioning process is proceeding over OnNetwork. The expected log should reflect discovery via DNS-SD (Domain Name System Service Discovery) rather than BLE and After successful discovery, the commissioning process should proceed, and you should see a success message confirming that the device was successfully commissioned over OnNetwork. [1657235905214] [31706:16841970] CHIP: [CTL] Discovered device to be commissioned over DNS-SD [1657235906071] [31706:16841969] CHIP: [TOO] Device commissioning completed with success From 8ab0d7eef6e4c9999adcbc604a11b6c91ab63578 Mon Sep 17 00:00:00 2001 From: Rajashreekalmane Date: Mon, 13 Jan 2025 18:52:33 +0530 Subject: [PATCH 06/13] resolved errors --- .../suites/certification/Test_TC_DD_3_11.yaml | 40 +++++++++---------- .../suites/certification/Test_TC_DD_3_12.yaml | 8 ++-- .../suites/certification/Test_TC_DD_3_13.yaml | 10 ++--- 3 files changed, 29 insertions(+), 29 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index ca8ec7782a7801..cf03f1dd831872 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -127,12 +127,12 @@ tests: PICS: MCORE.DD.DISCOVERY_PAF verification: | WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 0 --capabilities 8 - [1719392550.248867][1563:1563] CHIP:SVR: SetupQRCode: [MT:-24J0M3810KA0648G00] - [1719392550.248883][1563:1563] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1719392550.248892][1563:1563] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0M3810KA0648G00 - [1719392550.248911][1563:1563] CHIP:SVR: Manual pairing code: [34970112332] + [Verification command to be filled by NXP] + # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 0 --capabilities 8 + [1719392550.248867][1563:1563] CHIP:SVR: SetupQRCode: [MT:-24J0M3810KA0648G00] + [1719392550.248883][1563:1563] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1719392550.248892][1563:1563] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0M3810KA0648G00 + [1719392550.248911][1563:1563] CHIP:SVR: Manual pairing code: [34970112332] disabled: true - label: @@ -140,18 +140,18 @@ tests: PICS: MCORE.DD.SCAN_QR_CODE verification: | WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] + [Verification command to be filled by NXP] $ sudo ./chip-tool payload parse-setup-payload MT:-24J0M3810KA0648G00 - [1719392883.120482][28468:28468] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs - [1719392883.120687][28468:28468] CHIP:SPL: Parsing base38Representation: MT:-24J0M3810KA0648G00 - [1719392883.120839][28468:28468] CHIP:SPL: Version: 0 - [1719392883.120859][28468:28468] CHIP:SPL: VendorID: 65521 - [1719392883.120874][28468:28468] CHIP:SPL: ProductID: 32769 - [1719392883.120890][28468:28468] CHIP:SPL: Custom flow: 0 (STANDARD) - [1719392883.120910][28468:28468] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) - [1719392883.120928][28468:28468] CHIP:SPL: Long discriminator: 3840 (0xf00) - [1719392883.120944][28468:28468] CHIP:SPL: Passcode: 20202021 disabled: true + [1719392883.120482][28468:28468] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs + [1719392883.120687][28468:28468] CHIP:SPL: Parsing base38Representation: MT:-24J0M3810KA0648G00 + [1719392883.120839][28468:28468] CHIP:SPL: Version: 0 + [1719392883.120859][28468:28468] CHIP:SPL: VendorID: 65521 + [1719392883.120874][28468:28468] CHIP:SPL: ProductID: 32769 + [1719392883.120890][28468:28468] CHIP:SPL: Custom flow: 0 (STANDARD) + [1719392883.120910][28468:28468] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) + [1719392883.120928][28468:28468] CHIP:SPL: Long discriminator: 3840 (0xf00) + [1719392883.120944][28468:28468] CHIP:SPL: Passcode: 20202021 disabled: true - label: "Step 2c: Using the DUT, parse the TH’s QR code and follow any steps needed for the @@ -160,10 +160,10 @@ tests: verification: | WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] + [Verification command to be filled by NXP] - $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 - MT:-24J0M3810KA0648G00 + $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 + MT:-24J0M3810KA0648G00 - label: "Step 3a: Standard Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports IP Network for @@ -179,7 +179,7 @@ tests: ./chip-all-clusters-app --custom-flow 0 --capabilities 4 On the TH (All-Clusters App), verify that the user - has a QR code available to pass into the DUT + has a QR code available to pass into the DUT [1651105420.610637][27312:27312] CHIP:DL: Device Configuration: [1651105420.610695][27312:27312] CHIP:DL: Serial Number: TEST_SN [1651105420.610727][27312:27312] CHIP:DL: Vendor Id: 65521 (0xFFF1) diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml index 37adf7b3c17ec0..443ad5a2367449 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml @@ -179,9 +179,9 @@ tests: documentation." PICS: MCORE.DD.DISCOVERY_IP verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 1, supports + Use a Commissionee with a QR code that has the Custom Flow field set to 1, supports IP Network for its Discovery Capability, and is already on the same IP network as the DUT - commissioner. Ensure the Version bit string follows the current Matter specification documentation. + commissioner. Ensure the Version bit string follows the current Matter specification documentation. ./chip-all-clusters-app --custom-flow 1 --capabilities 4 On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT @@ -195,7 +195,7 @@ tests: verification: | 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. + The chip-tool does not support physically scanning QR codes. disabled: true - label: "Step 3c: DUT parses QR code." @@ -204,7 +204,7 @@ tests: 1. Parse the payload of the TH commissionee Verify on the DUT (CHIP-TOOL): - ./chip-tool payload parse-setup-payload MT:-24J029Q00KA0648G00 + ./chip-tool payload parse-setup-payload MT:-24J029Q00KA0648G00 2. Verify that TH logs do not show the commissionee being commissioned by the DUT. disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml index 89c8179451563c..178bb2d0db1eb3 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml @@ -144,8 +144,8 @@ tests: disabled: true - label: "Step 2b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | + PICS: MCORE.DD.SCAN_QR_CODE + verification: | WIFI - PAF feature is out of scope for V1.4 [Verification command to be filled by NXP] @@ -179,7 +179,7 @@ tests: PICS: MCORE.DD.DISCOVERY_PAF verification: | WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] + [Verification command to be filled by NXP] $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0EZA10KA0648G00 disabled: true @@ -214,7 +214,7 @@ tests: 1. Parse the payload of the TH commissionee Verify on the DUT (Chip-tool): - ./chip-tool payload parse-setup-payload MT:-24J029Q00KA0648G00 + ./chip-tool payload parse-setup-payload MT:-24J029Q00KA0648G00 [1660352541112] [20246:11812333] CHIP: [SPL] Parsing base38Representation: MT:-24J029Q00KA0648G00 [1660352541113] [20246:11812333] CHIP: [SPL] Version: 0 [1660352541113] [20246:11812333] CHIP: [SPL] VendorID: 65521 @@ -243,7 +243,7 @@ tests: [1657235198.977943][370963:370963] CHIP:DIS: Updating services using commissioning mode 0 Verify on the DUT (Chip-tool): - ./chip-tool pairing code 1 MT:-24J029Q00KA0648G00 + ./chip-tool pairing code 1 MT:-24J029Q00KA0648G00 [1657235198856] [31506:16834043] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' [1657235198856] [31506:16834043] CHIP: [TOO] Device commissioning completed with success disabled: true From e12a9ee6d326965abaa4346c2abab3934baaaf1b Mon Sep 17 00:00:00 2001 From: Rajashreekalmane Date: Mon, 13 Jan 2025 19:01:16 +0530 Subject: [PATCH 07/13] resolving format error --- src/app/tests/suites/certification/Test_TC_DD_3_11.yaml | 6 +++--- src/app/tests/suites/certification/Test_TC_DD_3_13.yaml | 5 ++--- 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index cf03f1dd831872..504f716b0b7d9b 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -133,7 +133,7 @@ tests: [1719392550.248883][1563:1563] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: [1719392550.248892][1563:1563] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0M3810KA0648G00 [1719392550.248911][1563:1563] CHIP:SVR: Manual pairing code: [34970112332] - disabled: true + disabled: true - label: "Step 2b: Scan the QR code from the previous step using the DUT." @@ -164,6 +164,7 @@ tests: $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0M3810KA0648G00 + - label: "Step 3a: Standard Commissioning Flow: Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports IP Network for @@ -251,6 +252,5 @@ tests: process using SoftAP" PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning not currently supported - + Out of Scope : SoftAP commissioning not currently supported disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml index 178bb2d0db1eb3..a08c3780a2af1d 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml @@ -144,10 +144,9 @@ tests: disabled: true - label: "Step 2b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | + PICS: MCORE.DD.SCAN_QR_CODE + verification: | WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] disabled: true From c2deac4f1b1a2b098e192be2c5e4d8be7040c7f2 Mon Sep 17 00:00:00 2001 From: Rajashreekalmane Date: Mon, 13 Jan 2025 19:10:25 +0530 Subject: [PATCH 08/13] error resolved --- .../suites/certification/Test_TC_DD_3_11.yaml | 14 +++++++------- .../suites/certification/Test_TC_DD_3_12.yaml | 8 ++++---- .../suites/certification/Test_TC_DD_3_13.yaml | 4 ++-- 3 files changed, 13 insertions(+), 13 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index 504f716b0b7d9b..4670595f720eb4 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -198,7 +198,7 @@ tests: PICS: MCORE.DD.SCAN_QR_CODE verification: | 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. + The chip-tool does not support physically scanning QR codes. disabled: true - label: @@ -207,13 +207,13 @@ tests: process using IP Network" PICS: MCORE.DD.DISCOVERY_IP verification: | - Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the - Commissioner/Commissionee commissioning process via IP Network. + Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the + Commissioner/Commissionee commissioning process via IP Network. On DUT (CHIP-TOOL), run the following command: - ./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00 - The DUT successfully parses the QR code and commissions the TH onto the Matter network. + ./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00 + The DUT successfully parses the QR code and commissions the TH onto the Matter network. [1651105530854] [95067:65607294] CHIP: [CTL] Received CommissioningComplete response [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' @@ -222,7 +222,7 @@ tests: [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' [1651105530854] [95067:65607294] CHIP: [TOO] Device commissioning completed with success - On TH (ALL-CLUSTERS-APP), Ensure the following log output + On TH (ALL-CLUSTERS-APP), Ensure the following log output [1651105530.973166][27371:27371] CHIP:SVR: Commissioning completed successfully [1651105530.973215][27371:27371] CHIP:DIS: Updating services using commissioning mode 0 @@ -252,5 +252,5 @@ tests: process using SoftAP" PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning not currently supported + Out of Scope : SoftAP commissioning not currently supported disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml index 443ad5a2367449..25b42179613205 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml @@ -215,7 +215,7 @@ tests: commissioning process using IP Network." PICS: MCORE.DD.DISCOVERY_IP verification: | - Using the DUT, parse the QR code generated by the TH and follow the necessary steps to + Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the Commissioner/Commissionee commissioning process via IP Network. On TH (ALL-CLUSTERS-APP), Ensure the following log output [1657234324.992098][370755:370755] CHIP:SVR: Commissioning completed successfully @@ -244,9 +244,9 @@ tests: - label: "Step 4b: Scan the QR code from the previous step using the DUT." PICS: MCORE.DD.SCAN_QR_CODE verification: | - Out of Scope : SoftAP commissionin currently not supported - Verify the QR code is scanned by DUT, chip-tool does not support - physically scanning QR codes + Out of Scope : SoftAP commissionin currently not supported + Verify the QR code is scanned by DUT, chip-tool does not support + physically scanning QR codes disabled: true - label: "Step 4c: DUT parses QR code." diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml index a08c3780a2af1d..f087c3e451769d 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml @@ -204,7 +204,7 @@ tests: PICS: MCORE.DD.SCAN_QR_CODE verification: | 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. + The chip-tool does not support physically scanning QR codes. disabled: true - label: "Step 3c: DUT parses QR code." @@ -262,7 +262,7 @@ tests: PICS: MCORE.DD.SCAN_QR_CODE verification: | Out of Scope : SoftAP commissioning currently not supported - Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes + Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes disabled: true - label: "Step 4c: DUT parses QR code." From db1bf730d4fee7faf9b945e91083252449372467 Mon Sep 17 00:00:00 2001 From: Rajashreekalmane Date: Mon, 13 Jan 2025 19:14:46 +0530 Subject: [PATCH 09/13] indentation error resolved --- src/app/tests/suites/certification/Test_TC_DD_3_11.yaml | 2 +- src/app/tests/suites/certification/Test_TC_DD_3_14.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index 4670595f720eb4..5ee0d441b282db 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -251,6 +251,6 @@ tests: needed for the Commissioner/Commissionee to complete the commissioning process using SoftAP" PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | + verification: | Out of Scope : SoftAP commissioning not currently supported disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml index eb0563c33015e5..c7aa2dcedac85b 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml @@ -144,7 +144,7 @@ tests: [1657235906071] [31706:16841969] CHIP: [TOO] Device commissioning completed with success disabled: true - - label: + - label: "Step 4a: Using the QR code from Step 1, ensure the TH’s Discovery Capability bit string is NOT set to Wi-Fi PAF for discovery (i.e. set to OnNetwork discovery capability)" From a9d622fe172966aeba359b0d2abc86be4fedc9bb Mon Sep 17 00:00:00 2001 From: Rajashreekalmane Date: Mon, 13 Jan 2025 19:22:11 +0530 Subject: [PATCH 10/13] Resolved errors --- .../suites/certification/Test_TC_DD_3_14.yaml | 100 +++++++++--------- 1 file changed, 50 insertions(+), 50 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml index c7aa2dcedac85b..64a71ef9a60649 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml @@ -61,11 +61,11 @@ tests: - label: "Step 1: Locate and scan/read the Commissionees QR code using DUT" verification: | - Locate the Commissionee’s QR code and scan/read it using the DUT. Ensure the DUT successfully scans/reads the QR code. - Execute the following command on the TH: + Locate the Commissionee’s QR code and scan/read it using the DUT. Ensure the DUT successfully scans/reads the QR code. + Execute the following command on the TH: - ./chip-all-clusters-app --version 0 --vendor-id 0xFFF1 --product-id 0x8001 --custom-flow 2 --capabilities 4 --discriminator 3840 --passcode 20202021 - Expected logs on the TH: + ./chip-all-clusters-app --version 0 --vendor-id 0xFFF1 --product-id 0x8001 --custom-flow 2 --capabilities 4 --discriminator 3840 --passcode 20202021 + Expected logs on the TH: [1657235470.970680][371041:371041] CHIP:DL: Device Configuration: [1657235470.970772][371041:371041] CHIP:DL: Serial Number: (not set) [1657235470.970811][371041:371041] CHIP:DL: Vendor Id: 65521 (0xFFF1) @@ -79,7 +79,7 @@ tests: [1657235470.971199][371041:371041] CHIP:SVR: SetupQRCode: [MT:-24J029Q00KA0648G00] [1657235470.971258][371041:371041] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: [1657235470.971293][371041:371041] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J029Q00KA0648G00 - Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes + Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes disabled: true - label: @@ -87,10 +87,10 @@ tests: new QR code but substituting out the current Version String with an invalid Version String (i.e. '010' or any non-zero 3-bit value)" verification: | - Using the chip-tool, execute the following command to create a new QR code with an invalid version string ('010' or any non-zero 3-bit value): + Using the chip-tool, execute the following command to create a new QR code with an invalid version string ('010' or any non-zero 3-bit value): - Use chip-tool's "payload generate-qrcode" command to help generate the new, invalid QR code - ./chip-tool payload generate-qrcode --existing-payload MT:-24J029Q00KA0648G00 --allow-invalid-payload 1 --version 2 + Use chip-tool's "payload generate-qrcode" command to help generate the new, invalid QR code + ./chip-tool payload generate-qrcode --existing-payload MT:-24J029Q00KA0648G00 --allow-invalid-payload 1 --version 2 Expected Logs on the TH: [1657235626568] [31698:16839018] CHIP: [TOO] QR Code: MT:034J029Q00KA0648G00 disabled: true @@ -115,13 +115,13 @@ tests: OnNetwork discovery capability)" PICS: MCORE.DD.DISCOVERY_BLE verification: | - Modify the QR code from Step 1 by ensuring the Discovery Capability bit string excludes BLE and is set to OnNetwork discovery capability. - Use the following command to generate the QR code: + Modify the QR code from Step 1 by ensuring the Discovery Capability bit string excludes BLE and is set to OnNetwork discovery capability. + Use the following command to generate the QR code: - Use chip-tool's "payload generate-qrcode" command to help generate the new, invalid QR code + Use chip-tool's "payload generate-qrcode" command to help generate the new, invalid QR code - ./chip-tool payload generate-qrcode --existing-payload MT:-24J029Q00KA0648G00 --allow-invalid-payload 1 --rendezvous 4 - Expected Logs on the TH: + ./chip-tool payload generate-qrcode --existing-payload MT:-24J029Q00KA0648G00 --allow-invalid-payload 1 --rendezvous 4 + Expected Logs on the TH: [1657235754393] [31702:16840391] CHIP: [TOO] QR Code: MT:-24J029Q00KA0648G00 @@ -150,9 +150,9 @@ tests: to OnNetwork discovery capability)" PICS: MCORE.DD.DISCOVERY_PAF verification: | - WIFI - PAF feature is out of scope for V1.4 + WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] + [Verification command to be filled by NXP] User has a QR code generated to pass into DUT. Using the example provided above, the payload would be "MT:-24J029Q00KA0648G00". $ ./out/all-clusters-app/chip-all-clusters-app --version 0 --vendor-id 0xFFF1 --product-id 0x8001 --custom-flow 2 --capabilities 4 --discriminator 3840 --passcode 20202021 @@ -174,8 +174,8 @@ tests: - label: "Step 4b: Scan/read the QR code of the TH device using the DUT" PICS: MCORE.DD.DISCOVERY_PAF verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] disabled: true - label: @@ -188,10 +188,10 @@ tests: 66666666, 77777777, 88888888, 99999999, 12345678, 87654321" verification: | Using the QR code from Step 1, replace the Passcode component with each of the following invalid passcodes: 00000000, 11111111, 22222222, 33333333, 44444444, 55555555, 66666666, 77777777, 88888888, 99999999, 12345678, and 87654321. - For each invalid passcode, generate a unique QR code, resulting in the following payloads: - Execute the following command on the TH: + For each invalid passcode, generate a unique QR code, resulting in the following payloads: + Execute the following command on the TH: - ./chip-tool payload generate-qrcode --existing-payload --allow-invalid-payload 1 --rendezvous 4 + ./chip-tool payload generate-qrcode --existing-payload --allow-invalid-payload 1 --rendezvous 4 "MT:-24J029Q00OC0000000" (00000000), "MT:-24J029Q00KMSP0Z800" (11111111), "MT:-24J029Q00GWID1WH00" (22222222), @@ -211,34 +211,34 @@ tests: "Step 4b: Scan each of the generated QR codes from the previous step using DUT" verification: | - Scan each of the 12 QR codes generated in the previous step using the DUT. The DUT should parse the QR code and identify the invalid passcode. - As expected, the DUT will terminate the commissioning process based on the invalid passcode. The DUT should reject the commission and not complete the pairing process. This termination will follow the DUT manufacturer’s specific instructions. - - The following command should be run for each QR code: - Expected failure due to the invalid passcode for each of the generated QR codes: - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - Example for the first QR code: - - ./chip-tool pairing code 1 MT:-24J029Q00OC0000000 - - Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument - - Similarly, repeat the command for the rest of the QR codes: - - MT:-24J029Q00OC0000000 - MT:-24J029Q00KMSP0Z800 - MT:-24J029Q00GWID1WH00 - MT:-24J029Q00C4912TQ00 - MT:-24J029Q008E.Q2QZ00 - MT:-24J029Q004ORE3N610 - MT:-24J029Q000YH24KF10 - MT:-24J029Q00Y58S4HO10 - MT:-24J029Q00UF-F5EX10 - MT:-24J029Q00QPQ36B420 - MT:-24J029Q004QG46Y900 - MT:-24J029Q00YX018EW10 - Ensure that the error message CHIP Error 0x0000002F: Invalid argument appears for each attempt, confirming the DUT has rejected the commissioning. + Scan each of the 12 QR codes generated in the previous step using the DUT. The DUT should parse the QR code and identify the invalid passcode. + As expected, the DUT will terminate the commissioning process based on the invalid passcode. The DUT should reject the commission and not complete the pairing process. This termination will follow the DUT manufacturer’s specific instructions. + + The following command should be run for each QR code: + Expected failure due to the invalid passcode for each of the generated QR codes: + Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument + + Example for the first QR code: + + ./chip-tool pairing code 1 MT:-24J029Q00OC0000000 + + Run command failure: ../../third_party/connectedhomeip/src/controller/SetUpCodePairer.cpp:50: CHIP Error 0x0000002F: Invalid argument + + Similarly, repeat the command for the rest of the QR codes: + + MT:-24J029Q00OC0000000 + MT:-24J029Q00KMSP0Z800 + MT:-24J029Q00GWID1WH00 + MT:-24J029Q00C4912TQ00 + MT:-24J029Q008E.Q2QZ00 + MT:-24J029Q004ORE3N610 + MT:-24J029Q000YH24KF10 + MT:-24J029Q00Y58S4HO10 + MT:-24J029Q00UF-F5EX10 + MT:-24J029Q00QPQ36B420 + MT:-24J029Q004QG46Y900 + MT:-24J029Q00YX018EW10 + Ensure that the error message CHIP Error 0x0000002F: Invalid argument appears for each attempt, confirming the DUT has rejected the commissioning. disabled: true - label: @@ -247,8 +247,8 @@ tests: that is not 'MT:' (i.e. Prefix='AB:')" verification: | Generate a new QR code by replacing the current prefix (MT:) with an invalid prefix (AB:) from step 1, resulting in the - payload AB:-24J029Q00KA0648G00, and ensure the QR code is correctly generated and ready to be passed into the DUT with no applicable TH or DUT logs. - AB:-24J029Q00KA0648G00 + payload AB:-24J029Q00KA0648G00, and ensure the QR code is correctly generated and ready to be passed into the DUT with no applicable TH or DUT logs. + AB:-24J029Q00KA0648G00 disabled: true - label: From ec94a8c013a4b331b2936d29329a71b4b2a7333b Mon Sep 17 00:00:00 2001 From: Rajashreekalmane Date: Wed, 15 Jan 2025 11:15:42 +0530 Subject: [PATCH 11/13] resolving errors --- .../suites/certification/Test_TC_DD_3_11.yaml | 461 ++++++++--------- .../suites/certification/Test_TC_DD_3_12.yaml | 484 +++++++++--------- 2 files changed, 467 insertions(+), 478 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index 5ee0d441b282db..e43069b9bbf35c 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -14,243 +14,236 @@ # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default name: - 3.3.11. [TC-DD-3.11] Commissioning Flow = 0 (Standard Flow) - QR Code [DUT - - Commissioner] + 3.3.11. [TC-DD-3.11] Commissioning Flow = 0 (Standard Flow) - QR Code [DUT - + Commissioner] PICS: - - MCORE.ROLE.COMMISSIONER - - MCORE.DD.QR_COMMISSIONING - - MCORE.DD.STANDARD_COMM_FLOW + - MCORE.ROLE.COMMISSIONER + - MCORE.DD.QR_COMMISSIONING + - MCORE.DD.STANDARD_COMM_FLOW config: - nodeId: 0x12344321 - cluster: "Basic Information" - endpoint: 0 + nodeId: 0x12344321 + cluster: "Basic Information" + endpoint: 0 tests: - - label: "Note" - verification: | - Chip-tool command used below are an example to verify the DUT as commissioner test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. - disabled: true - - - label: "Preconditions" - verification: | - 1 - DUT is on an operational network and has accurate date, time, timezone, regulatory, and fabric information available. - - 2 - QR Code is printed on the Commissionee device or in additional provided materials (ex: manual, companion app, web service). - - An example onboarding QR code could be "MT:-24J029Q00KA0648G00" (following 5.1.3 "QR Code", Table 34 "Packed Binary Data Structure for Onboarding Payload") which includes: - - - 3-bit Version String=000 - - - 16-bit Vendor ID=0xFFF1 (as defined in section 2.5.2. "Vendor Identifier") - - - 16-bit Product ID=0x8001 (as defined in section 2.5.3. "Product Identifier") - - - 2-bit Custom Flow=10 (Custom Commissioning Flow = 2) - - - 8-bit Discovery Capabilities Bitmask=00000100 (OnNetwork) - - - 12-bit Discriminator=0xF00 - - - 27-bit Passcode=20202021 - - - 4-bit Padding=0000 - - - no variable-length TLV Data included (as defined in section 5.1.3.1. "Payload", subsection "TLV Data") - disabled: true - - - label: - "Step 1a: Standard Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 0 and supports BLE for its - Discovery Capability. Ensure the Version bit string follows the - current Matter spec. documentation." - PICS: MCORE.DD.DISCOVERY_BLE - verification: | - 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 - - [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) - [1667888323.967270][3151:3151] CHIP:DL: Product Id: 32769 (0x8001) - [1667888323.967351][3151:3151] CHIP:DL: Hardware Version: 0 - [1667888323.967409][3151:3151] CHIP:DL: Setup Pin Code (0 for UNKNOWN/ERROR): 20202021 - [1667888323.967489][3151:3151] CHIP:DL: Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00) - [1667888323.967566][3151:3151] CHIP:DL: Manufacturing Date: (not set) - [1667888323.967616][3151:3151] CHIP:DL: Device Type: 65535 (0xFFFF) - [1667888323.967720][3151:3151] CHIP:SVR: SetupQRCode: [MT:-24J042C00KA0648G00] - [1667888323.967788][3151:3151] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1667888323.967841][3151:3151] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J042C00KA0648G00 - [1667888323.967940][3151:3151] CHIP:SVR: Manual pairing code: [34970112332] - [1667888323.968031][3151:3151] CHIP:DMG: Endpoint 0, Cluster 0x0000_001D update version to ea7ea7b8 - disabled: true - - - label: "Step 1b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - 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: - "Step 1c: Using the DUT, parse the THs QR code and follow any steps - needed for the Commissioner/Commissionee to complete the commissioning - process using BLE" - PICS: MCORE.DD.DISCOVERY_BLE - verification: | - 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 - - 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 - [1657232374.956577][370357:370357] CHIP:DIS: Updating services using commissioning mode 0 - disabled: true - - - label: - "Step 2a: Standard Commissioning Flow: Use a Commissionee with a QR code that has - the Custom Flow field set to 0 and supports Wi-Fi PAF for its Discovery Capability. - Ensure the Version bit string follows the current Matter spec. documentation." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 0 --capabilities 8 - [1719392550.248867][1563:1563] CHIP:SVR: SetupQRCode: [MT:-24J0M3810KA0648G00] - [1719392550.248883][1563:1563] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1719392550.248892][1563:1563] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0M3810KA0648G00 - [1719392550.248911][1563:1563] CHIP:SVR: Manual pairing code: [34970112332] - disabled: true - - - label: - "Step 2b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - - $ sudo ./chip-tool payload parse-setup-payload MT:-24J0M3810KA0648G00 - [1719392883.120482][28468:28468] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs - [1719392883.120687][28468:28468] CHIP:SPL: Parsing base38Representation: MT:-24J0M3810KA0648G00 - [1719392883.120839][28468:28468] CHIP:SPL: Version: 0 - [1719392883.120859][28468:28468] CHIP:SPL: VendorID: 65521 - [1719392883.120874][28468:28468] CHIP:SPL: ProductID: 32769 - [1719392883.120890][28468:28468] CHIP:SPL: Custom flow: 0 (STANDARD) - [1719392883.120910][28468:28468] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) - [1719392883.120928][28468:28468] CHIP:SPL: Long discriminator: 3840 (0xf00) - [1719392883.120944][28468:28468] CHIP:SPL: Passcode: 20202021 disabled: true - - - label: - "Step 2c: Using the DUT, parse the TH’s QR code and follow any steps needed for the - Commissioner/Commissionee to complete the commissioning process using Wi-Fi PAF" - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - WIFI - PAF feature is out of scope for V1.4 - - [Verification command to be filled by NXP] - - $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 - MT:-24J0M3810KA0648G00 - - - label: - "Step 3a: Standard Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 0, supports IP Network for - its Discovery Capability and is already on the same IP network as the - DUT commissioner. Ensure the Version bit string follows the current - Matter spec. documentation." - PICS: MCORE.DD.DISCOVERY_IP - verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports IP Network for its Discovery Capability, - and is already on the same IP network as the DUT commissioner. Ensure the Version bit string follows the current Matter - specification documentation. - - ./chip-all-clusters-app --custom-flow 0 --capabilities 4 - - On the TH (All-Clusters App), verify that the user - has a QR code available to pass into the DUT - [1651105420.610637][27312:27312] CHIP:DL: Device Configuration: - [1651105420.610695][27312:27312] CHIP:DL: Serial Number: TEST_SN - [1651105420.610727][27312:27312] CHIP:DL: Vendor Id: 65521 (0xFFF1) - [1651105420.610761][27312:27312] CHIP:DL: Product Id: 32769 (0x8001) - [1651105420.610792][27312:27312] CHIP:DL: Hardware Version: 0 - [1651105420.610815][27312:27312] CHIP:DL: Setup Pin Code (0 for UNKNOWN/ERROR): 20202021 - [1651105420.610836][27312:27312] CHIP:DL: Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00) - [1651105420.610864][27312:27312] CHIP:DL: Manufacturing Date: (not set) - [1651105420.610886][27312:27312] CHIP:DL: Device Type: 65535 (0xFFFF) - [1651105420.610907][27312:27312] CHIP:-: ==== Onboarding payload for Standard Commissioning Flow ==== - [1651105420.610962][27312:27312] CHIP:SVR: SetupQRCode: [MT:-24J0AFN00KA0648G00] - disabled: true - - - label: "Step 3b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - 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: - "Step 3c: Using the DUT, parse the THs QR code and follow any steps - needed for the Commissioner/Commissionee to complete the commissioning - process using IP Network" - PICS: MCORE.DD.DISCOVERY_IP - verification: | - Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the - Commissioner/Commissionee commissioning process via IP Network. - - On DUT (CHIP-TOOL), run the following command: - - ./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00 - The DUT successfully parses the QR code and commissions the TH onto the Matter network. - - [1651105530854] [95067:65607294] CHIP: [CTL] Received CommissioningComplete response - [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' - [1651105530854] [95067:65607294] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' - [1651105530854] [95067:65607294] CHIP: [CTL] Performing next commissioning step 'Cleanup' - [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' - [1651105530854] [95067:65607294] CHIP: [TOO] Device commissioning completed with success - - On TH (ALL-CLUSTERS-APP), Ensure the following log output - - [1651105530.973166][27371:27371] CHIP:SVR: Commissioning completed successfully - [1651105530.973215][27371:27371] CHIP:DIS: Updating services using commissioning mode 0 - disabled: true - - - label: - "Step 4a: Standard Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 0 and supports SoftAP for - its Discovery Capability. Ensure the Version bit string follows the - current Matter spec. documentation." - PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope : SoftAP commissioning not currently supported - disabled: true - - - label: "Step 4b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - Out of Scope : SoftAP commissioning not currently supported - SoftAP commissioning not currently supported - Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes - disabled: true - - - label: - "Step 4c: Using the DUT, parse the THs QR code and follow any steps - needed for the Commissioner/Commissionee to complete the commissioning - process using SoftAP" - PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope : SoftAP commissioning not currently supported - disabled: true + - label: "Note" + verification: | + Chip-tool command used below are an example to verify the DUT as commissioner test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + disabled: true + + - label: "Preconditions" + verification: | + 1 - DUT is on an operational network and has accurate date, time, timezone, regulatory, and fabric information available. + + 2 - QR Code is printed on the Commissionee device or in additional provided materials (ex: manual, companion app, web service). + + An example onboarding QR code could be "MT:-24J029Q00KA0648G00" (following 5.1.3 "QR Code", Table 34 "Packed Binary Data Structure for Onboarding Payload") which includes: + + - 3-bit Version String=000 + + - 16-bit Vendor ID=0xFFF1 (as defined in section 2.5.2. "Vendor Identifier") + + - 16-bit Product ID=0x8001 (as defined in section 2.5.3. "Product Identifier") + + - 2-bit Custom Flow=10 (Custom Commissioning Flow = 2) + + - 8-bit Discovery Capabilities Bitmask=00000100 (OnNetwork) + + - 12-bit Discriminator=0xF00 + + - 27-bit Passcode=20202021 + + - 4-bit Padding=0000 + + - no variable-length TLV Data included (as defined in section 5.1.3.1. "Payload", subsection "TLV Data") + disabled: true + + - label: "Step 1a: Standard Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 0 and supports BLE for its + Discovery Capability. Ensure the Version bit string follows the + current Matter spec. documentation." + PICS: MCORE.DD.DISCOVERY_BLE + verification: | + 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 + + [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) + [1667888323.967270][3151:3151] CHIP:DL: Product Id: 32769 (0x8001) + [1667888323.967351][3151:3151] CHIP:DL: Hardware Version: 0 + [1667888323.967409][3151:3151] CHIP:DL: Setup Pin Code (0 for UNKNOWN/ERROR): 20202021 + [1667888323.967489][3151:3151] CHIP:DL: Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00) + [1667888323.967566][3151:3151] CHIP:DL: Manufacturing Date: (not set) + [1667888323.967616][3151:3151] CHIP:DL: Device Type: 65535 (0xFFFF) + [1667888323.967720][3151:3151] CHIP:SVR: SetupQRCode: [MT:-24J042C00KA0648G00] + [1667888323.967788][3151:3151] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1667888323.967841][3151:3151] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J042C00KA0648G00 + [1667888323.967940][3151:3151] CHIP:SVR: Manual pairing code: [34970112332] + [1667888323.968031][3151:3151] CHIP:DMG: Endpoint 0, Cluster 0x0000_001D update version to ea7ea7b8 + disabled: true + + - label: "Step 1b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + 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: "Step 1c: Using the DUT, parse the THs QR code and follow any steps + needed for the Commissioner/Commissionee to complete the commissioning + process using BLE" + PICS: MCORE.DD.DISCOVERY_BLE + verification: | + 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 + + 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 + [1657232374.956577][370357:370357] CHIP:DIS: Updating services using commissioning mode 0 + disabled: true + + - label: + "Step 2a: Standard Commissioning Flow: Use a Commissionee with a QR code that has + the Custom Flow field set to 0 and supports Wi-Fi PAF for its Discovery Capability. + Ensure the Version bit string follows the current Matter spec. documentation." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 0 --capabilities 8 + [1719392550.248867][1563:1563] CHIP:SVR: SetupQRCode: [MT:-24J0M3810KA0648G00] + [1719392550.248883][1563:1563] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1719392550.248892][1563:1563] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0M3810KA0648G00 + [1719392550.248911][1563:1563] CHIP:SVR: Manual pairing code: [34970112332] + disabled: true + + - label: "Step 2b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + + $ sudo ./chip-tool payload parse-setup-payload MT:-24J0M3810KA0648G00 + [1719392883.120482][28468:28468] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs + [1719392883.120687][28468:28468] CHIP:SPL: Parsing base38Representation: MT:-24J0M3810KA0648G00 + [1719392883.120839][28468:28468] CHIP:SPL: Version: 0 + [1719392883.120859][28468:28468] CHIP:SPL: VendorID: 65521 + [1719392883.120874][28468:28468] CHIP:SPL: ProductID: 32769 + [1719392883.120890][28468:28468] CHIP:SPL: Custom flow: 0 (STANDARD) + [1719392883.120910][28468:28468] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) + [1719392883.120928][28468:28468] CHIP:SPL: Long discriminator: 3840 (0xf00) + [1719392883.120944][28468:28468] CHIP:SPL: Passcode: 20202021 disabled: true + + - label: + "Step 2c: Using the DUT, parse the TH’s QR code and follow any steps needed for the + Commissioner/Commissionee to complete the commissioning process using Wi-Fi PAF" + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + + [Verification command to be filled by NXP] + + $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 + MT:-24J0M3810KA0648G00 + + - label: "Step 3a: Standard Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 0, supports IP Network for + its Discovery Capability and is already on the same IP network as the + DUT commissioner. Ensure the Version bit string follows the current + Matter spec. documentation." + PICS: MCORE.DD.DISCOVERY_IP + verification: | + Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports IP Network for its Discovery Capability, + and is already on the same IP network as the DUT commissioner. Ensure the Version bit string follows the current Matter + specification documentation. + + ./chip-all-clusters-app --custom-flow 0 --capabilities 4 + + On the TH (All-Clusters App), verify that the user + has a QR code available to pass into the DUT + [1651105420.610637][27312:27312] CHIP:DL: Device Configuration: + [1651105420.610695][27312:27312] CHIP:DL: Serial Number: TEST_SN + [1651105420.610727][27312:27312] CHIP:DL: Vendor Id: 65521 (0xFFF1) + [1651105420.610761][27312:27312] CHIP:DL: Product Id: 32769 (0x8001) + [1651105420.610792][27312:27312] CHIP:DL: Hardware Version: 0 + [1651105420.610815][27312:27312] CHIP:DL: Setup Pin Code (0 for UNKNOWN/ERROR): 20202021 + [1651105420.610836][27312:27312] CHIP:DL: Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00) + [1651105420.610864][27312:27312] CHIP:DL: Manufacturing Date: (not set) + [1651105420.610886][27312:27312] CHIP:DL: Device Type: 65535 (0xFFFF) + [1651105420.610907][27312:27312] CHIP:-: ==== Onboarding payload for Standard Commissioning Flow ==== + [1651105420.610962][27312:27312] CHIP:SVR: SetupQRCode: [MT:-24J0AFN00KA0648G00] + disabled: true + + - label: "Step 3b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + 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: "Step 3c: Using the DUT, parse the THs QR code and follow any steps + needed for the Commissioner/Commissionee to complete the commissioning + process using IP Network" + PICS: MCORE.DD.DISCOVERY_IP + verification: | + Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the + Commissioner/Commissionee commissioning process via IP Network. + + On DUT (CHIP-TOOL), run the following command: + + ./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00 + The DUT successfully parses the QR code and commissions the TH onto the Matter network. + + [1651105530854] [95067:65607294] CHIP: [CTL] Received CommissioningComplete response + [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' + [1651105530854] [95067:65607294] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' + [1651105530854] [95067:65607294] CHIP: [CTL] Performing next commissioning step 'Cleanup' + [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' + [1651105530854] [95067:65607294] CHIP: [TOO] Device commissioning completed with success + + On TH (ALL-CLUSTERS-APP), Ensure the following log output + + [1651105530.973166][27371:27371] CHIP:SVR: Commissioning completed successfully + [1651105530.973215][27371:27371] CHIP:DIS: Updating services using commissioning mode 0 + disabled: true + + - label: "Step 4a: Standard Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 0 and supports SoftAP for + its Discovery Capability. Ensure the Version bit string follows the + current Matter spec. documentation." + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning not currently supported + disabled: true + + - label: "Step 4b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + Out of Scope : SoftAP commissioning not currently supported + SoftAP commissioning not currently supported + Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes + disabled: true + + - label: "Step 4c: Using the DUT, parse the THs QR code and follow any steps + needed for the Commissioner/Commissionee to complete the commissioning + process using SoftAP" + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning not currently supported + disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml index 25b42179613205..008f07c9b37053 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml @@ -13,253 +13,249 @@ # limitations under the License. # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default -name: - 3.3.12. [TC-DD-3.12] Commissioning Flow = 1 (User-Intent Flow) - QR Code - [DUT - Commissioner] +name: 3.3.12. [TC-DD-3.12] Commissioning Flow = 1 (User-Intent Flow) - QR Code + [DUT - Commissioner] PICS: - - MCORE.ROLE.COMMISSIONER - - MCORE.DD.QR_COMMISSIONING - - MCORE.DD.USER_INTENT_COMM_FLOW + - MCORE.ROLE.COMMISSIONER + - MCORE.DD.QR_COMMISSIONING + - MCORE.DD.USER_INTENT_COMM_FLOW config: - nodeId: 0x12344321 - cluster: "Basic Information" - endpoint: 0 + nodeId: 0x12344321 + cluster: "Basic Information" + endpoint: 0 tests: - - label: "Note" - verification: | - Chip-tool command used below are an example to verify the DUT as commissioner test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. - disabled: true - - - label: "Preconditions" - verification: | - 1 - DUT is on an operational network and has accurate date, time, timezone, regulatory, and fabric information available. - - 2 - 5.1.3 - QR Code is printed on the Commissionee device or in additional provided materials (ex: manual, companion app, web service). - - An example onboarding QR code could be "MT:-24J029Q00KA0648G00" (following 5.1.3 "QR Code", Table 34 "Packed Binary Data Structure for Onboarding Payload") which includes: - - - 3-bit Version String=000 - - - 16-bit Vendor ID=0xFFF1 (as defined in section 2.5.2. "Vendor Identifier") - - - 16-bit Product ID=0x8001 (as defined in section 2.5.3. "Product Identifier") - - - 2-bit Custom Flow=10 (Custom Commissioning Flow = 2) - - - 8-bit Discovery Capabilities Bitmask=00000100 (OnNetwork) - - - 12-bit Discriminator=0xF00 - - - 27-bit Passcode=20202021 - - - 4-bit Padding=0000 - - - no variable-length TLV Data included (as defined in section 5.1.3.1. "Payload", subsection "TLV Data") - disabled: true - - - label: - "Step 1a: User-Intent Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 1 and supports BLE for its - Discovery Capability. Commissionee is NOT in commissioning mode. - Ensure the Version bit string follows the current Matter spec. - documentation." - PICS: MCORE.DD.DISCOVERY_BLE - verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 1, 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 --capabilities 2 --custom-flow 1 --ble-device 1 - On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT - - [1657234110.765249][370717:370717] CHIP:SVR: SetupQRCode: [MT:-24J0YXE00KA0648G00] - [1657234110.765314][370717:370717] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1657234110.765364][370717:370717] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0YXE00KA0648G00 - disabled: true - - - label: "Step 1b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - 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: "Step 1c: DUT parses QR code." - PICS: MCORE.DD.DISCOVERY_BLE - verification: | - 1. Parse the payload of the TH commissionee - - Verify on the DUT (CHIP-TOOL): - ./chip-tool payload parse-setup-payload MT:-24J0YXE00KA0648G00 - - 2. Verify that TH logs do not show the commissionee being commissioned by the DUT. - disabled: true - - - label: - "Step 1d: User should follow any TH-specific steps for putting the TH - Commissionee device into commissioning mode and to complete the - commissioning process using BLE." - PICS: MCORE.DD.DISCOVERY_BLE - verification: | - 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: - [1651101988.943015][23212:23212] CHIP:SVR: Commissioning completed successfully - [1651101988.943058][23212:23212] CHIP:DIS: Updating services using commissioning mode 0 - - On TH (ALL-CLUSTER-APP), Ensure the following log output: - ./chip-tool pairing code 1 MT:-24J0YXE00KA0648G00 - [1657234147237] [31454:16822562] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' - [1657234147237] [31454:16822562] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' - [1657234147237] [31454:16822562] CHIP: [CTL] Performing next commissioning step 'Cleanup' - [1657234147237] [31454:16822562] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' - [1657234147237] [31454:16822562] CHIP: [TOO] Device commissioning completed with success - disabled: true - - label: - "Step 2a: User-Intent Commissioning Flow: Use a Commissionee with a QR code that has the - Custom Flow field set to 1 and supports Wi-Fi PAF for its Discovery Capability. Commissionee is NOT in commissioning mode. Ensure the Version bit string follows the current Matter spec. documentation. " - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - - # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 1 --capabilities 8 - [1719393010.693198][1592:1592] CHIP:SVR: SetupQRCode: [MT:-24J0IJ910KA0648G00] - [1719393010.693213][1592:1592] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1719393010.693222][1592:1592] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0IJ910KA0648G00 - [1719393010.693246][1592:1592] CHIP:SVR: Manual pairing code: [749701123365521327694] - disabled: true - - - label: "Step 2b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - WIFI - PAF feature is out of scope for V1.4 - - [Verification command to be filled by NXP] - disabled: true - - - label: "Step 2c: DUT parses QR code." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - - $ sudo ./chip-tool payload parse-setup-payload MT:-24J0IJ910KA0648G00 - [1719393067.811966][28514:28514] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs - [1719393067.812195][28514:28514] CHIP:DL: writing settings to file (/tmp/chip_tool_kvs-PRUpuW) - [1719393067.812351][28514:28514] CHIP:DL: renamed tmp file to file (/tmp/chip_tool_kvs) - [1719393067.812455][28514:28514] CHIP:SPL: Parsing base38Representation: MT:-24J0IJ910KA0648G00 - [1719393067.812626][28514:28514] CHIP:SPL: Version: 0 - [1719393067.812647][28514:28514] CHIP:SPL: VendorID: 65521 - [1719393067.812664][28514:28514] CHIP:SPL: ProductID: 32769 - [1719393067.812679][28514:28514] CHIP:SPL: Custom flow: 1 (USER ACTION REQUIRED) - [1719393067.812698][28514:28514] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) - [1719393067.812714][28514:28514] CHIP:SPL: Long discriminator: 3840 (0xf00) - [1719393067.812729][28514:28514] CHIP:SPL: Passcode: 20202021 - disabled: true - - - label: - "Step 2d: User should follow any TH-specific steps for putting the TH Commissionee device into commissioning - mode and to complete the commissioning process using Wi-Fi PAF." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0IJ910KA0648G00 - disabled: true - - - label: - "Step 3a: User-Intent Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 1 and supports IP Network - for its Discovery Capability. Commissionee is NOT in commissioning - mode. Ensure the Version bit string follows the current Matter spec. - documentation." - PICS: MCORE.DD.DISCOVERY_IP - verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 1, supports - IP Network for its Discovery Capability, and is already on the same IP network as the DUT - commissioner. Ensure the Version bit string follows the current Matter specification documentation. - - ./chip-all-clusters-app --custom-flow 1 --capabilities 4 - On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT - [1660353382.200125][249074:249074] CHIP:SVR: SetupQRCode: [MT:-24J029Q00KA0648G00] - [1660353382.200152][249074:249074] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1660353382.200173][249074:249074] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J029Q00KA0648G00 - disabled: true - - - label: "Step 3b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - 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: "Step 3c: DUT parses QR code." - PICS: MCORE.DD.DISCOVERY_IP - verification: | - 1. Parse the payload of the TH commissionee - - Verify on the DUT (CHIP-TOOL): - ./chip-tool payload parse-setup-payload MT:-24J029Q00KA0648G00 - - 2. Verify that TH logs do not show the commissionee being commissioned by the DUT. - disabled: true - - - label: - "Step 3d: User should follow any TH-specific steps for putting the TH - Commissionee device into commissioning mode and to complete the - commissioning process using IP Network." - PICS: MCORE.DD.DISCOVERY_IP - verification: | - Using the DUT, parse the QR code generated by the TH and follow the necessary steps to - complete the Commissioner/Commissionee commissioning process via IP Network. - On TH (ALL-CLUSTERS-APP), Ensure the following log output - [1657234324.992098][370755:370755] CHIP:SVR: Commissioning completed successfully - [1657234324.992146][370755:370755] CHIP:DIS: Updating services using commissioning mode 0 - - On DUT (CHIP-TOOL), run the following command: - ./chip-tool pairing code 1 MT:-24J029Q00KA0648G00 - [1657234324847] [31475:16824564] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' - [1657234324847] [31475:16824564] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' - [1657234324847] [31475:16824564] CHIP: [CTL] Performing next commissioning step 'Cleanup' - [1657234324847] [31475:16824564] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' - [1657234324847] [31475:16824564] CHIP: [TOO] Device commissioning completed with success - disabled: true - - - label: - "Step 4a: User-Intent Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 1 and supports SoftAP for - its Discovery Capability. Commissionee is NOT in commissioning mode. - Ensure the Version bit string follows the current Matter spec. - documentation." - PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope : SoftAP commissioning currently not supported - disabled: true - - - label: "Step 4b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - Out of Scope : SoftAP commissionin currently not supported - Verify the QR code is scanned by DUT, chip-tool does not support - physically scanning QR codes - disabled: true - - - label: "Step 4c: DUT parses QR code." - PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope : SoftAP commissioning currently not supported - disabled: true - - - label: - "Step 4d: User should follow any TH-specific steps for putting the TH - Commissionee device into commissioning mode and to complete the - commissioning process using SoftAP." - PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope : SoftAP commissioning currently not supported - disabled: true + - label: "Note" + verification: | + Chip-tool command used below are an example to verify the DUT as commissioner test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + disabled: true + + - label: "Preconditions" + verification: | + 1 - DUT is on an operational network and has accurate date, time, timezone, regulatory, and fabric information available. + + 2 - 5.1.3 - QR Code is printed on the Commissionee device or in additional provided materials (ex: manual, companion app, web service). + + An example onboarding QR code could be "MT:-24J029Q00KA0648G00" (following 5.1.3 "QR Code", Table 34 "Packed Binary Data Structure for Onboarding Payload") which includes: + + - 3-bit Version String=000 + + - 16-bit Vendor ID=0xFFF1 (as defined in section 2.5.2. "Vendor Identifier") + + - 16-bit Product ID=0x8001 (as defined in section 2.5.3. "Product Identifier") + + - 2-bit Custom Flow=10 (Custom Commissioning Flow = 2) + + - 8-bit Discovery Capabilities Bitmask=00000100 (OnNetwork) + + - 12-bit Discriminator=0xF00 + + - 27-bit Passcode=20202021 + + - 4-bit Padding=0000 + + - no variable-length TLV Data included (as defined in section 5.1.3.1. "Payload", subsection "TLV Data") + disabled: true + + - label: + "Step 1a: User-Intent Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 1 and supports BLE for its + Discovery Capability. Commissionee is NOT in commissioning mode. + Ensure the Version bit string follows the current Matter spec. + documentation." + PICS: MCORE.DD.DISCOVERY_BLE + verification: | + Use a Commissionee with a QR code that has the Custom Flow field set to 1, 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 --capabilities 2 --custom-flow 1 --ble-device 1 + On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT + + [1657234110.765249][370717:370717] CHIP:SVR: SetupQRCode: [MT:-24J0YXE00KA0648G00] + [1657234110.765314][370717:370717] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1657234110.765364][370717:370717] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0YXE00KA0648G00 + disabled: true + + - label: "Step 1b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + 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: "Step 1c: DUT parses QR code." + PICS: MCORE.DD.DISCOVERY_BLE + verification: | + 1. Parse the payload of the TH commissionee + + Verify on the DUT (CHIP-TOOL): + ./chip-tool payload parse-setup-payload MT:-24J0YXE00KA0648G00 + + 2. Verify that TH logs do not show the commissionee being commissioned by the DUT. + disabled: true + + - label: "Step 1d: User should follow any TH-specific steps for putting the TH + Commissionee device into commissioning mode and to complete the + commissioning process using BLE." + PICS: MCORE.DD.DISCOVERY_BLE + verification: | + 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: + [1651101988.943015][23212:23212] CHIP:SVR: Commissioning completed successfully + [1651101988.943058][23212:23212] CHIP:DIS: Updating services using commissioning mode 0 + + On TH (ALL-CLUSTER-APP), Ensure the following log output: + ./chip-tool pairing code 1 MT:-24J0YXE00KA0648G00 + [1657234147237] [31454:16822562] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' + [1657234147237] [31454:16822562] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' + [1657234147237] [31454:16822562] CHIP: [CTL] Performing next commissioning step 'Cleanup' + [1657234147237] [31454:16822562] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' + [1657234147237] [31454:16822562] CHIP: [TOO] Device commissioning completed with success + disabled: true + - label: + "Step 2a: User-Intent Commissioning Flow: Use a Commissionee with a QR code that has the + Custom Flow field set to 1 and supports Wi-Fi PAF for its Discovery Capability. Commissionee is NOT in commissioning mode. Ensure the Version bit string follows the current Matter spec. documentation. " + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + + # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 1 --capabilities 8 + [1719393010.693198][1592:1592] CHIP:SVR: SetupQRCode: [MT:-24J0IJ910KA0648G00] + [1719393010.693213][1592:1592] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1719393010.693222][1592:1592] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0IJ910KA0648G00 + [1719393010.693246][1592:1592] CHIP:SVR: Manual pairing code: [749701123365521327694] + disabled: true + + - label: "Step 2b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + WIFI - PAF feature is out of scope for V1.4 + + [Verification command to be filled by NXP] + disabled: true + + - label: "Step 2c: DUT parses QR code." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + + $ sudo ./chip-tool payload parse-setup-payload MT:-24J0IJ910KA0648G00 + [1719393067.811966][28514:28514] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs + [1719393067.812195][28514:28514] CHIP:DL: writing settings to file (/tmp/chip_tool_kvs-PRUpuW) + [1719393067.812351][28514:28514] CHIP:DL: renamed tmp file to file (/tmp/chip_tool_kvs) + [1719393067.812455][28514:28514] CHIP:SPL: Parsing base38Representation: MT:-24J0IJ910KA0648G00 + [1719393067.812626][28514:28514] CHIP:SPL: Version: 0 + [1719393067.812647][28514:28514] CHIP:SPL: VendorID: 65521 + [1719393067.812664][28514:28514] CHIP:SPL: ProductID: 32769 + [1719393067.812679][28514:28514] CHIP:SPL: Custom flow: 1 (USER ACTION REQUIRED) + [1719393067.812698][28514:28514] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) + [1719393067.812714][28514:28514] CHIP:SPL: Long discriminator: 3840 (0xf00) + [1719393067.812729][28514:28514] CHIP:SPL: Passcode: 20202021 + disabled: true + + - label: + "Step 2d: User should follow any TH-specific steps for putting the TH Commissionee device into commissioning + mode and to complete the commissioning process using Wi-Fi PAF." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0IJ910KA0648G00 + disabled: true + + - label: + "Step 3a: User-Intent Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 1 and supports IP Network + for its Discovery Capability. Commissionee is NOT in commissioning + mode. Ensure the Version bit string follows the current Matter spec. + documentation." + PICS: MCORE.DD.DISCOVERY_IP + verification: | + Use a Commissionee with a QR code that has the Custom Flow field set to 1, supports + IP Network for its Discovery Capability, and is already on the same IP network as the DUT + commissioner. Ensure the Version bit string follows the current Matter specification documentation. + + ./chip-all-clusters-app --custom-flow 1 --capabilities 4 + On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT + [1660353382.200125][249074:249074] CHIP:SVR: SetupQRCode: [MT:-24J029Q00KA0648G00] + [1660353382.200152][249074:249074] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1660353382.200173][249074:249074] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J029Q00KA0648G00 + disabled: true + + - label: "Step 3b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + 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: "Step 3c: DUT parses QR code." + PICS: MCORE.DD.DISCOVERY_IP + verification: | + 1. Parse the payload of the TH commissionee + + Verify on the DUT (CHIP-TOOL): + ./chip-tool payload parse-setup-payload MT:-24J029Q00KA0648G00 + + 2. Verify that TH logs do not show the commissionee being commissioned by the DUT. + disabled: true + + - label: "Step 3d: User should follow any TH-specific steps for putting the TH + Commissionee device into commissioning mode and to complete the + commissioning process using IP Network." + PICS: MCORE.DD.DISCOVERY_IP + verification: | + Using the DUT, parse the QR code generated by the TH and follow the necessary steps to + complete the Commissioner/Commissionee commissioning process via IP Network. + On TH (ALL-CLUSTERS-APP), Ensure the following log output + [1657234324.992098][370755:370755] CHIP:SVR: Commissioning completed successfully + [1657234324.992146][370755:370755] CHIP:DIS: Updating services using commissioning mode 0 + + On DUT (CHIP-TOOL), run the following command: + ./chip-tool pairing code 1 MT:-24J029Q00KA0648G00 + [1657234324847] [31475:16824564] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' + [1657234324847] [31475:16824564] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' + [1657234324847] [31475:16824564] CHIP: [CTL] Performing next commissioning step 'Cleanup' + [1657234324847] [31475:16824564] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' + [1657234324847] [31475:16824564] CHIP: [TOO] Device commissioning completed with success + disabled: true + + - label: + "Step 4a: User-Intent Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 1 and supports SoftAP for + its Discovery Capability. Commissionee is NOT in commissioning mode. + Ensure the Version bit string follows the current Matter spec. + documentation." + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning currently not supported + disabled: true + + - label: "Step 4b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + Out of Scope : SoftAP commissionin currently not supported + Verify the QR code is scanned by DUT, chip-tool does not support + physically scanning QR codes + disabled: true + + - label: "Step 4c: DUT parses QR code." + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning currently not supported + disabled: true + + - label: "Step 4d: User should follow any TH-specific steps for putting the TH + Commissionee device into commissioning mode and to complete the + commissioning process using SoftAP." + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning currently not supported + disabled: true From eb0b7d61f1c741f099265550f58927b02476f3c3 Mon Sep 17 00:00:00 2001 From: "Restyled.io" Date: Wed, 15 Jan 2025 05:46:33 +0000 Subject: [PATCH 12/13] Restyled by whitespace --- .../suites/certification/Test_TC_DD_2_1.yaml | 2 +- .../suites/certification/Test_TC_DD_2_2.yaml | 20 +++++++++---------- .../suites/certification/Test_TC_DD_3_11.yaml | 14 ++++++------- .../suites/certification/Test_TC_DD_3_12.yaml | 10 +++++----- .../suites/certification/Test_TC_DD_3_13.yaml | 20 +++++++++---------- .../suites/certification/Test_TC_DD_3_14.yaml | 20 +++++++++---------- 6 files changed, 43 insertions(+), 43 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml b/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml index 152394ee37c210..0d16da6e207690 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml @@ -234,7 +234,7 @@ tests: verification: | Out of Scope : SoftAP commissioning is currently not supported. disabled: true - + - label: "Step 12: TH scans and finds the DUT SSID" PICS: MCORE.COM.WIFI && MCORE.DD.IE verification: | diff --git a/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml b/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml index 16275cdfbc1fcc..62d72f8adf4064 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml @@ -48,7 +48,7 @@ tests: verification: | Initiate the Matter announcement procedure on the TH using BLE transport, and the TH must start sending BLE advertisements successfully. ./chip-all-clusters-app --wifi --discriminator 3841 - + Verify in TH on the commissionee side: [1657221603.350406][368108:368108] CHIP:DL: Device Configuration: @@ -170,7 +170,7 @@ tests: [1651743348.446452][5072:5072] CHIP:IN: New secure session created for device , LSID:2138 PSID:14881! [1651743348.446962][5072:5072] CHIP:SVR: Commissioning completed session establishment step disabled: true - + - label: "Step 3a: TH is configured with the default channel to be Channel 6 in 2.4GHz. If TH has a 5GHz Wi-Fi radio, TH is configured with an @@ -200,26 +200,26 @@ tests: - label: "Step 4a: TH starts SoftAP and begin matter announcement procedure" PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning currently not supported + Out of Scope : SoftAP commissioning currently not supported disabled: true - label: "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 + Out of Scope : SoftAP commissioning currently not supported disabled: true - + - label: "Step 5a: DUT scans using Wi-Fi in background" PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning currently not supported + Out of Scope : SoftAP commissioning currently not supported disabled: true - label: "Step 5b: TH starts SoftAP and begin matter announcement procedure" PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning currently not supported + Out of Scope : SoftAP commissioning currently not supported disabled: true - label: "Step 5c: DUT must find TH and provide onboarding data for @@ -227,14 +227,14 @@ tests: as set on TH" PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning currently not supported - disabled: true + Out of Scope : SoftAP commissioning currently not supported + disabled: true - label: "Step 6: With DUT and TH connected to the same network over IP, DUT performs service discovery using DNS-SD" verification: | - TH is in commissioning mode and discoverable by DUT over IP through DNS-SD advertisements. + TH is in commissioning mode and discoverable by DUT over IP through DNS-SD advertisements. This can also be verified using through the DUT's pairing command over IP. Verify in TH as commissionee side: diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index e43069b9bbf35c..3b7dc923ce7388 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -66,7 +66,7 @@ tests: current Matter spec. documentation." PICS: MCORE.DD.DISCOVERY_BLE verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports BLE for its Discovery Capability, and + 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 @@ -159,7 +159,7 @@ tests: [Verification command to be filled by NXP] - $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 + $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0M3810KA0648G00 - label: "Step 3a: Standard Commissioning Flow: Use a Commissionee with a QR @@ -169,8 +169,8 @@ tests: Matter spec. documentation." PICS: MCORE.DD.DISCOVERY_IP verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports IP Network for its Discovery Capability, - and is already on the same IP network as the DUT commissioner. Ensure the Version bit string follows the current Matter + Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports IP Network for its Discovery Capability, + and is already on the same IP network as the DUT commissioner. Ensure the Version bit string follows the current Matter specification documentation. ./chip-all-clusters-app --custom-flow 0 --capabilities 4 @@ -202,7 +202,7 @@ tests: process using IP Network" PICS: MCORE.DD.DISCOVERY_IP verification: | - Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the + Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the Commissioner/Commissionee commissioning process via IP Network. On DUT (CHIP-TOOL), run the following command: @@ -217,7 +217,7 @@ tests: [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' [1651105530854] [95067:65607294] CHIP: [TOO] Device commissioning completed with success - On TH (ALL-CLUSTERS-APP), Ensure the following log output + On TH (ALL-CLUSTERS-APP), Ensure the following log output [1651105530.973166][27371:27371] CHIP:SVR: Commissioning completed successfully [1651105530.973215][27371:27371] CHIP:DIS: Updating services using commissioning mode 0 @@ -235,7 +235,7 @@ tests: - label: "Step 4b: Scan the QR code from the previous step using the DUT." PICS: MCORE.DD.SCAN_QR_CODE verification: | - Out of Scope : SoftAP commissioning not currently supported + Out of Scope : SoftAP commissioning not currently supported SoftAP commissioning not currently supported Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml index 008f07c9b37053..b2f40603d42ed7 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml @@ -67,7 +67,7 @@ tests: documentation." PICS: MCORE.DD.DISCOVERY_BLE verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 1, supports BLE for its Discovery Capability, + Use a Commissionee with a QR code that has the Custom Flow field set to 1, 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 --capabilities 2 --custom-flow 1 --ble-device 1 @@ -101,7 +101,7 @@ tests: commissioning process using BLE." PICS: MCORE.DD.DISCOVERY_BLE verification: | - Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the + 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: @@ -191,7 +191,7 @@ tests: - label: "Step 3b: Scan the QR code from the previous step using the DUT." PICS: MCORE.DD.SCAN_QR_CODE verification: | - Scan the QR code generated in the previous step using the DUT. Verify that the QR code is + 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 @@ -214,7 +214,7 @@ tests: verification: | Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the Commissioner/Commissionee commissioning process via IP Network. - On TH (ALL-CLUSTERS-APP), Ensure the following log output + On TH (ALL-CLUSTERS-APP), Ensure the following log output [1657234324.992098][370755:370755] CHIP:SVR: Commissioning completed successfully [1657234324.992146][370755:370755] CHIP:DIS: Updating services using commissioning mode 0 @@ -241,7 +241,7 @@ tests: - label: "Step 4b: Scan the QR code from the previous step using the DUT." PICS: MCORE.DD.SCAN_QR_CODE verification: | - Out of Scope : SoftAP commissionin currently not supported + Out of Scope : SoftAP commissionin currently not supported Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml index f087c3e451769d..607d40ea72dda4 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml @@ -68,8 +68,8 @@ tests: documentation." PICS: MCORE.DD.DISCOVERY_BLE verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 2, - supports BLE for its Discovery Capability, and ensures the Version bit string + Use a Commissionee with a QR code that has the Custom Flow field set to 2, + 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 2 --capabilities 2 On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT @@ -115,7 +115,7 @@ tests: verification: | 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 TH (ALL-CLUSTER-APP), Ensure the following log output + On TH (ALL-CLUSTER-APP), Ensure the following log output [1657235088.040328][370941:370941] CHIP:SVR: Commissioning completed successfully [1657235088.040371][370941:370941] CHIP:DIS: Updating services using commissioning mode 0 @@ -234,10 +234,10 @@ tests: commissioning process using IP Network." PICS: MCORE.DD.DISCOVERY_IP verification: | - Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the + Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the Commissioner/Commissionee commissioning process via IP Network. - - On TH (ALL-CLUSTERS-APP), Ensure the following log output + + On TH (ALL-CLUSTERS-APP), Ensure the following log output [1657235198.977848][370963:370963] CHIP:SVR: Commissioning completed successfully [1657235198.977943][370963:370963] CHIP:DIS: Updating services using commissioning mode 0 @@ -255,20 +255,20 @@ tests: documentation." PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning currently not supported + Out of Scope : SoftAP commissioning currently not supported disabled: true - label: "Step 4b: Scan the QR code from the previous step using the DUT." PICS: MCORE.DD.SCAN_QR_CODE verification: | - Out of Scope : SoftAP commissioning currently not supported + Out of Scope : SoftAP commissioning currently not supported Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes disabled: true - label: "Step 4c: DUT parses QR code." PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning currently not supported + Out of Scope : SoftAP commissioning currently not supported disabled: true - label: @@ -279,5 +279,5 @@ tests: commissioning process using SoftAP." PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning currently not supported + Out of Scope : SoftAP commissioning currently not supported disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml index 64a71ef9a60649..b781d737b26e6a 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_14.yaml @@ -61,9 +61,9 @@ tests: - label: "Step 1: Locate and scan/read the Commissionees QR code using DUT" verification: | - Locate the Commissionee’s QR code and scan/read it using the DUT. Ensure the DUT successfully scans/reads the QR code. + Locate the Commissionee’s QR code and scan/read it using the DUT. Ensure the DUT successfully scans/reads the QR code. Execute the following command on the TH: - + ./chip-all-clusters-app --version 0 --vendor-id 0xFFF1 --product-id 0x8001 --custom-flow 2 --capabilities 4 --discriminator 3840 --passcode 20202021 Expected logs on the TH: [1657235470.970680][371041:371041] CHIP:DL: Device Configuration: @@ -125,7 +125,7 @@ tests: [1657235754393] [31702:16840391] CHIP: [TOO] QR Code: MT:-24J029Q00KA0648G00 - Ensure the TH logs reflect the QR code during the commissioning process and Use the new QR code payload MT:-24J029Q00KA0648G00 + Ensure the TH logs reflect the QR code during the commissioning process and Use the new QR code payload MT:-24J029Q00KA0648G00 and pass it into the DUT for further processing. disabled: true @@ -141,19 +141,19 @@ tests: Check the logs on the DUT to verify that the commissioning process is proceeding over OnNetwork. The expected log should reflect discovery via DNS-SD (Domain Name System Service Discovery) rather than BLE and After successful discovery, the commissioning process should proceed, and you should see a success message confirming that the device was successfully commissioned over OnNetwork. [1657235905214] [31706:16841970] CHIP: [CTL] Discovered device to be commissioned over DNS-SD - [1657235906071] [31706:16841969] CHIP: [TOO] Device commissioning completed with success + [1657235906071] [31706:16841969] CHIP: [TOO] Device commissioning completed with success disabled: true - + - label: "Step 4a: Using the QR code from Step 1, ensure the TH’s Discovery Capability bit string is NOT set to Wi-Fi PAF for discovery (i.e. set to OnNetwork discovery capability)" PICS: MCORE.DD.DISCOVERY_PAF - verification: | + verification: | WIFI - PAF feature is out of scope for V1.4 [Verification command to be filled by NXP] - + User has a QR code generated to pass into DUT. Using the example provided above, the payload would be "MT:-24J029Q00KA0648G00". $ ./out/all-clusters-app/chip-all-clusters-app --version 0 --vendor-id 0xFFF1 --product-id 0x8001 --custom-flow 2 --capabilities 4 --discriminator 3840 --passcode 20202021 [1657235470.970680][371041:371041] CHIP:DL: Device Configuration: @@ -187,7 +187,7 @@ tests: the list: 00000000, 11111111, 22222222, 33333333, 44444444, 55555555, 66666666, 77777777, 88888888, 99999999, 12345678, 87654321" verification: | - Using the QR code from Step 1, replace the Passcode component with each of the following invalid passcodes: 00000000, 11111111, 22222222, 33333333, 44444444, 55555555, 66666666, 77777777, 88888888, 99999999, 12345678, and 87654321. + Using the QR code from Step 1, replace the Passcode component with each of the following invalid passcodes: 00000000, 11111111, 22222222, 33333333, 44444444, 55555555, 66666666, 77777777, 88888888, 99999999, 12345678, and 87654321. For each invalid passcode, generate a unique QR code, resulting in the following payloads: Execute the following command on the TH: @@ -204,7 +204,7 @@ tests: "MT:-24J029Q00QPQ36B420" (99999999), "MT:-24J029Q004QG46Y900" (12345678), "MT:-24J029Q00YX018EW10" (87654321) - After generating the QR codes, confirm that they are ready for use by the DUT for further testing. There is no applicable logs from the TH + After generating the QR codes, confirm that they are ready for use by the DUT for further testing. There is no applicable logs from the TH disabled: true - label: @@ -255,7 +255,7 @@ tests: "Step 5b: Scan/read the QR code, generated in the previous step, using the DUT" verification: | - Scan the QR code generated in the previous step using the DUT, ensuring that the DUT commissioner does not + Scan the QR code generated in the previous step using the DUT, ensuring that the DUT commissioner does not react successfully to scanning the QR code, and the DUT terminates the commissioning process in a manner specific to the DUT manufacturer's instructions. Verify on the DUT (Chip-tool): ./chip-tool pairing code 1 AB:-24J029Q00KA0648G00 From 6c757ff9782fbdfd99b23e6d53521badd65097cf Mon Sep 17 00:00:00 2001 From: "Restyled.io" Date: Wed, 15 Jan 2025 05:46:40 +0000 Subject: [PATCH 13/13] Restyled by prettier-yaml --- .../suites/certification/Test_TC_DD_2_1.yaml | 26 +- .../suites/certification/Test_TC_DD_2_2.yaml | 114 ++-- .../suites/certification/Test_TC_DD_3_11.yaml | 462 +++++++++-------- .../suites/certification/Test_TC_DD_3_12.yaml | 488 +++++++++--------- .../suites/certification/Test_TC_DD_3_13.yaml | 22 +- 5 files changed, 565 insertions(+), 547 deletions(-) diff --git a/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml b/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml index 0d16da6e207690..28e0c1eb2c1298 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_2_1.yaml @@ -185,11 +185,11 @@ tests: 2.4GHz band." PICS: MCORE.COM.WIFI && MCORE.DD.DISCOVERY_PAF verification: | - WIFI - PAF feature is out of scope for V1.4 + WIFI - PAF feature is out of scope for V1.4 - [Configuration command to be filled by NXP] + [Configuration command to be filled by NXP] - Configure the AP to the PAF working channel and connect TH to AP + Configure the AP to the PAF working channel and connect TH to AP disabled: true - label: @@ -208,22 +208,22 @@ tests: - label: "Step 9: DUT begins sending Wi-Fi PAF Publish messages." PICS: MCORE.COM.WIFI && MCORE.DD.DISCOVERY_PAF verification: | - WIFI - PAF feature is out of scope for V1.4 + WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] + [Verification command to be filled by NXP] - * 2.4g: - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 - * 5g, FCC: - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=5220 - * 5g ETSI: - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=5745 + * 2.4g: + $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 + * 5g, FCC: + $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=5220 + * 5g ETSI: + $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=5745 disabled: true - label: "Step 10: TH scans and finds the DUT SSID" PICS: MCORE.COM.WIFI && MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning is currently not supported. + Out of Scope : SoftAP commissioning is currently not supported. disabled: true - label: @@ -232,7 +232,7 @@ tests: command (or reset manually)" PICS: MCORE.COM.WIFI && MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning is currently not supported. + Out of Scope : SoftAP commissioning is currently not supported. disabled: true - label: "Step 12: TH scans and finds the DUT SSID" diff --git a/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml b/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml index 62d72f8adf4064..d931942b89dd94 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_2_2.yaml @@ -123,52 +123,52 @@ tests: as set on TH" PICS: MCORE.DD.DISCOVERY_BLE verification: | - DUT must detect the TH and retrieve the onboarding data for validation - 1. Discover commissionables over BLE using DUT=chip-tool pairing command - Verify in TH as commissionee side: - [1651743346.152716][5072:5075] CHIP:DL: Device E4:5F:01:0F:3B:B1 (Path: /org/bluez/hci0/dev_E4_5F_01_0F_3B_B1) Connected - [1651743347.908807][5072:5075] CHIP:DL: BluezCharacteristicAcquireWrite is called, conn: 0xffffa0043700 - [1651743347.911151][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 - [1651743347.911349][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 - [1651743347.911754][5072:5072] CHIP:BLE: local and remote recv window sizes = 6 - [1651743347.911829][5072:5072] CHIP:BLE: selected BTP version 4 - [1651743347.911877][5072:5072] CHIP:BLE: using BTP fragment sizes rx 244 / tx 244. - [1651743348.006770][5072:5075] CHIP:DL: CHIPoBLE subscribe received - [1651743348.007026][5072:5072] CHIP:IN: BLE EndPoint 0xaaaab7bb3c20 Connection Complete - [1651743348.007132][5072:5072] CHIP:DL: HandlePlatformSpecificBLEEvent 32778 - [1651743348.007196][5072:5072] CHIP:DL: Receive kCHIPoBLEConnectionEstablished - [1651743348.150980][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 - [1651743348.199997][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 - [1651743348.200614][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 - [1651743348.201013][5072:5072] CHIP:EM: Received message of type 0x20 with protocolId (0, 0) and MessageCounter:3306320356 on exchange 29381r - [1651743348.201117][5072:5072] CHIP:EM: Handling via exchange: 29381r, Delegate: 0xaaaab7bb2a90 - [1651743348.201191][5072:5072] CHIP:SC: Received PBKDF param request - [1651743348.201280][5072:5072] CHIP:SC: Peer assigned session ID 14881 - [1651743348.201349][5072:5072] CHIP:SC: Found MRP parameters in the message - [1651743348.201520][5072:5072] CHIP:SC: Including MRP parameters in PBKDF param response - [1651743348.201884][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2ef78 to 0x0000000000000000 (0) of type 0x21 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159088. - [1651743348.201989][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2ef78 with MessageCounter:2627159088 to 0x0000000000000000 at monotonic time: 0000000000FF6731 msec - [1651743348.202196][5072:5072] CHIP:SC: Sent PBKDF param response - [1651743348.298384][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 - [1651743348.299274][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 - [1651743348.300132][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 - [1651743348.300571][5072:5072] CHIP:EM: Received message of type 0x22 with protocolId (0, 0) and MessageCounter:3306320357 on exchange 29381r - [1651743348.300655][5072:5072] CHIP:EM: Found matching exchange: 29381r, Delegate: 0xaaaab7bb2a90 - [1651743348.300741][5072:5072] CHIP:SC: Received spake2p msg1 - [1651743348.304696][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2ee58 to 0x0000000000000000 (0) of type 0x23 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159089. - [1651743348.304817][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2ee58 with MessageCounter:2627159089 to 0x0000000000000000 at monotonic time: 0000000000FF6798 msec - [1651743348.305007][5072:5072] CHIP:SC: Sent spake2p msg2 - [1651743348.444144][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 - [1651743348.444992][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 - [1651743348.445608][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 - [1651743348.445888][5072:5072] CHIP:EM: Received message of type 0x24 with protocolId (0, 0) and MessageCounter:3306320358 on exchange 29381r - [1651743348.445943][5072:5072] CHIP:EM: Found matching exchange: 29381r, Delegate: 0xaaaab7bb2a90 - [1651743348.446001][5072:5072] CHIP:SC: Received spake2p msg3 - [1651743348.446130][5072:5072] CHIP:SC: Sending status report. Protocol code 0, exchange 29381 - [1651743348.446202][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2eea8 to 0x0000000000000000 (0) of type 0x40 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159090. - [1651743348.446262][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2eea8 with MessageCounter:2627159090 to 0x0000000000000000 at monotonic time: 0000000000FF6825 msec - [1651743348.446452][5072:5072] CHIP:IN: New secure session created for device , LSID:2138 PSID:14881! - [1651743348.446962][5072:5072] CHIP:SVR: Commissioning completed session establishment step + DUT must detect the TH and retrieve the onboarding data for validation + 1. Discover commissionables over BLE using DUT=chip-tool pairing command + Verify in TH as commissionee side: + [1651743346.152716][5072:5075] CHIP:DL: Device E4:5F:01:0F:3B:B1 (Path: /org/bluez/hci0/dev_E4_5F_01_0F_3B_B1) Connected + [1651743347.908807][5072:5075] CHIP:DL: BluezCharacteristicAcquireWrite is called, conn: 0xffffa0043700 + [1651743347.911151][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 + [1651743347.911349][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 + [1651743347.911754][5072:5072] CHIP:BLE: local and remote recv window sizes = 6 + [1651743347.911829][5072:5072] CHIP:BLE: selected BTP version 4 + [1651743347.911877][5072:5072] CHIP:BLE: using BTP fragment sizes rx 244 / tx 244. + [1651743348.006770][5072:5075] CHIP:DL: CHIPoBLE subscribe received + [1651743348.007026][5072:5072] CHIP:IN: BLE EndPoint 0xaaaab7bb3c20 Connection Complete + [1651743348.007132][5072:5072] CHIP:DL: HandlePlatformSpecificBLEEvent 32778 + [1651743348.007196][5072:5072] CHIP:DL: Receive kCHIPoBLEConnectionEstablished + [1651743348.150980][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 + [1651743348.199997][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 + [1651743348.200614][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 + [1651743348.201013][5072:5072] CHIP:EM: Received message of type 0x20 with protocolId (0, 0) and MessageCounter:3306320356 on exchange 29381r + [1651743348.201117][5072:5072] CHIP:EM: Handling via exchange: 29381r, Delegate: 0xaaaab7bb2a90 + [1651743348.201191][5072:5072] CHIP:SC: Received PBKDF param request + [1651743348.201280][5072:5072] CHIP:SC: Peer assigned session ID 14881 + [1651743348.201349][5072:5072] CHIP:SC: Found MRP parameters in the message + [1651743348.201520][5072:5072] CHIP:SC: Including MRP parameters in PBKDF param response + [1651743348.201884][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2ef78 to 0x0000000000000000 (0) of type 0x21 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159088. + [1651743348.201989][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2ef78 with MessageCounter:2627159088 to 0x0000000000000000 at monotonic time: 0000000000FF6731 msec + [1651743348.202196][5072:5072] CHIP:SC: Sent PBKDF param response + [1651743348.298384][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 + [1651743348.299274][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 + [1651743348.300132][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 + [1651743348.300571][5072:5072] CHIP:EM: Received message of type 0x22 with protocolId (0, 0) and MessageCounter:3306320357 on exchange 29381r + [1651743348.300655][5072:5072] CHIP:EM: Found matching exchange: 29381r, Delegate: 0xaaaab7bb2a90 + [1651743348.300741][5072:5072] CHIP:SC: Received spake2p msg1 + [1651743348.304696][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2ee58 to 0x0000000000000000 (0) of type 0x23 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159089. + [1651743348.304817][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2ee58 with MessageCounter:2627159089 to 0x0000000000000000 at monotonic time: 0000000000FF6798 msec + [1651743348.305007][5072:5072] CHIP:SC: Sent spake2p msg2 + [1651743348.444144][5072:5075] CHIP:BLE: Indication confirmation, 0xffffa0043700 + [1651743348.444992][5072:5075] CHIP:DL: c1 BluezCharacteristicWriteFD mtu, 517 + [1651743348.445608][5072:5075] CHIP:BLE: Write request received debug 0xffffa0043700 + [1651743348.445888][5072:5072] CHIP:EM: Received message of type 0x24 with protocolId (0, 0) and MessageCounter:3306320358 on exchange 29381r + [1651743348.445943][5072:5072] CHIP:EM: Found matching exchange: 29381r, Delegate: 0xaaaab7bb2a90 + [1651743348.446001][5072:5072] CHIP:SC: Received spake2p msg3 + [1651743348.446130][5072:5072] CHIP:SC: Sending status report. Protocol code 0, exchange 29381 + [1651743348.446202][5072:5072] CHIP:IN: Prepared unauthenticated message 0xffffdcf2eea8 to 0x0000000000000000 (0) of type 0x40 and protocolId (0, 0) on exchange 29381r with MessageCounter:2627159090. + [1651743348.446262][5072:5072] CHIP:IN: Sending unauthenticated msg 0xffffdcf2eea8 with MessageCounter:2627159090 to 0x0000000000000000 at monotonic time: 0000000000FF6825 msec + [1651743348.446452][5072:5072] CHIP:IN: New secure session created for device , LSID:2138 PSID:14881! + [1651743348.446962][5072:5072] CHIP:SVR: Commissioning completed session establishment step disabled: true - label: @@ -180,21 +180,21 @@ tests: regulatory domains." PICS: MCORE.DD.DISCOVERY_PAF verification: | - WIFI - PAF feature is out of scope for V1.4 - TH must start sending Wi-Fi PAF Publish Frames on the default channel and the channel list. - 2.4g - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 - 5g - FCC - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=5220 - 5g ETSI - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=5745 + WIFI - PAF feature is out of scope for V1.4 + TH must start sending Wi-Fi PAF Publish Frames on the default channel and the channel list. + 2.4g - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 + 5g - FCC - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=5220 + 5g ETSI - $sudo ./chip-all-clusters-app --wifi --wifipaf freq_list=5745 disabled: true - label: "Step 3b: DUT starts Wi-Fi PAF scan in its commissioning channel" PICS: MCORE.DD.DISCOVERY_PAF verification: | - WIFI - PAF feature is out of scope for V1.4 + WIFI - PAF feature is out of scope for V1.4 - DUT must find TH and provide onboarding data to for validation. Pass Criteria: DUT is able to report the Onboarding payload as set on TH + DUT must find TH and provide onboarding data to for validation. Pass Criteria: DUT is able to report the Onboarding payload as set on TH - $ sudo ./chip-tool pairing wifipaf-wifi 1 n_m_2g nxp12345 20202021 3840 + $ sudo ./chip-tool pairing wifipaf-wifi 1 n_m_2g nxp12345 20202021 3840 disabled: true - label: "Step 4a: TH starts SoftAP and begin matter announcement procedure" @@ -204,7 +204,9 @@ tests: disabled: true - label: - "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)" + "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 @@ -227,7 +229,7 @@ tests: as set on TH" PICS: MCORE.DD.DISCOVERY_SOFTAP verification: | - Out of Scope : SoftAP commissioning currently not supported + Out of Scope : SoftAP commissioning currently not supported disabled: true - label: diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml index 3b7dc923ce7388..2169a227c4843f 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_11.yaml @@ -14,236 +14,244 @@ # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default name: - 3.3.11. [TC-DD-3.11] Commissioning Flow = 0 (Standard Flow) - QR Code [DUT - - Commissioner] + 3.3.11. [TC-DD-3.11] Commissioning Flow = 0 (Standard Flow) - QR Code [DUT - + Commissioner] PICS: - - MCORE.ROLE.COMMISSIONER - - MCORE.DD.QR_COMMISSIONING - - MCORE.DD.STANDARD_COMM_FLOW + - MCORE.ROLE.COMMISSIONER + - MCORE.DD.QR_COMMISSIONING + - MCORE.DD.STANDARD_COMM_FLOW config: - nodeId: 0x12344321 - cluster: "Basic Information" - endpoint: 0 + nodeId: 0x12344321 + cluster: "Basic Information" + endpoint: 0 tests: - - label: "Note" - verification: | - Chip-tool command used below are an example to verify the DUT as commissioner test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. - disabled: true - - - label: "Preconditions" - verification: | - 1 - DUT is on an operational network and has accurate date, time, timezone, regulatory, and fabric information available. - - 2 - QR Code is printed on the Commissionee device or in additional provided materials (ex: manual, companion app, web service). - - An example onboarding QR code could be "MT:-24J029Q00KA0648G00" (following 5.1.3 "QR Code", Table 34 "Packed Binary Data Structure for Onboarding Payload") which includes: - - - 3-bit Version String=000 - - - 16-bit Vendor ID=0xFFF1 (as defined in section 2.5.2. "Vendor Identifier") - - - 16-bit Product ID=0x8001 (as defined in section 2.5.3. "Product Identifier") - - - 2-bit Custom Flow=10 (Custom Commissioning Flow = 2) - - - 8-bit Discovery Capabilities Bitmask=00000100 (OnNetwork) - - - 12-bit Discriminator=0xF00 - - - 27-bit Passcode=20202021 - - - 4-bit Padding=0000 - - - no variable-length TLV Data included (as defined in section 5.1.3.1. "Payload", subsection "TLV Data") - disabled: true - - - label: "Step 1a: Standard Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 0 and supports BLE for its - Discovery Capability. Ensure the Version bit string follows the - current Matter spec. documentation." - PICS: MCORE.DD.DISCOVERY_BLE - verification: | - 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 - - [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) - [1667888323.967270][3151:3151] CHIP:DL: Product Id: 32769 (0x8001) - [1667888323.967351][3151:3151] CHIP:DL: Hardware Version: 0 - [1667888323.967409][3151:3151] CHIP:DL: Setup Pin Code (0 for UNKNOWN/ERROR): 20202021 - [1667888323.967489][3151:3151] CHIP:DL: Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00) - [1667888323.967566][3151:3151] CHIP:DL: Manufacturing Date: (not set) - [1667888323.967616][3151:3151] CHIP:DL: Device Type: 65535 (0xFFFF) - [1667888323.967720][3151:3151] CHIP:SVR: SetupQRCode: [MT:-24J042C00KA0648G00] - [1667888323.967788][3151:3151] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1667888323.967841][3151:3151] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J042C00KA0648G00 - [1667888323.967940][3151:3151] CHIP:SVR: Manual pairing code: [34970112332] - [1667888323.968031][3151:3151] CHIP:DMG: Endpoint 0, Cluster 0x0000_001D update version to ea7ea7b8 - disabled: true - - - label: "Step 1b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - 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: "Step 1c: Using the DUT, parse the THs QR code and follow any steps - needed for the Commissioner/Commissionee to complete the commissioning - process using BLE" - PICS: MCORE.DD.DISCOVERY_BLE - verification: | - 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 - - 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 - [1657232374.956577][370357:370357] CHIP:DIS: Updating services using commissioning mode 0 - disabled: true - - - label: - "Step 2a: Standard Commissioning Flow: Use a Commissionee with a QR code that has - the Custom Flow field set to 0 and supports Wi-Fi PAF for its Discovery Capability. - Ensure the Version bit string follows the current Matter spec. documentation." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 0 --capabilities 8 - [1719392550.248867][1563:1563] CHIP:SVR: SetupQRCode: [MT:-24J0M3810KA0648G00] - [1719392550.248883][1563:1563] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1719392550.248892][1563:1563] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0M3810KA0648G00 - [1719392550.248911][1563:1563] CHIP:SVR: Manual pairing code: [34970112332] - disabled: true - - - label: "Step 2b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - - $ sudo ./chip-tool payload parse-setup-payload MT:-24J0M3810KA0648G00 - [1719392883.120482][28468:28468] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs - [1719392883.120687][28468:28468] CHIP:SPL: Parsing base38Representation: MT:-24J0M3810KA0648G00 - [1719392883.120839][28468:28468] CHIP:SPL: Version: 0 - [1719392883.120859][28468:28468] CHIP:SPL: VendorID: 65521 - [1719392883.120874][28468:28468] CHIP:SPL: ProductID: 32769 - [1719392883.120890][28468:28468] CHIP:SPL: Custom flow: 0 (STANDARD) - [1719392883.120910][28468:28468] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) - [1719392883.120928][28468:28468] CHIP:SPL: Long discriminator: 3840 (0xf00) - [1719392883.120944][28468:28468] CHIP:SPL: Passcode: 20202021 disabled: true - - - label: - "Step 2c: Using the DUT, parse the TH’s QR code and follow any steps needed for the - Commissioner/Commissionee to complete the commissioning process using Wi-Fi PAF" - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - WIFI - PAF feature is out of scope for V1.4 - - [Verification command to be filled by NXP] - - $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 - MT:-24J0M3810KA0648G00 - - - label: "Step 3a: Standard Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 0, supports IP Network for - its Discovery Capability and is already on the same IP network as the - DUT commissioner. Ensure the Version bit string follows the current - Matter spec. documentation." - PICS: MCORE.DD.DISCOVERY_IP - verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports IP Network for its Discovery Capability, - and is already on the same IP network as the DUT commissioner. Ensure the Version bit string follows the current Matter - specification documentation. - - ./chip-all-clusters-app --custom-flow 0 --capabilities 4 - - On the TH (All-Clusters App), verify that the user - has a QR code available to pass into the DUT - [1651105420.610637][27312:27312] CHIP:DL: Device Configuration: - [1651105420.610695][27312:27312] CHIP:DL: Serial Number: TEST_SN - [1651105420.610727][27312:27312] CHIP:DL: Vendor Id: 65521 (0xFFF1) - [1651105420.610761][27312:27312] CHIP:DL: Product Id: 32769 (0x8001) - [1651105420.610792][27312:27312] CHIP:DL: Hardware Version: 0 - [1651105420.610815][27312:27312] CHIP:DL: Setup Pin Code (0 for UNKNOWN/ERROR): 20202021 - [1651105420.610836][27312:27312] CHIP:DL: Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00) - [1651105420.610864][27312:27312] CHIP:DL: Manufacturing Date: (not set) - [1651105420.610886][27312:27312] CHIP:DL: Device Type: 65535 (0xFFFF) - [1651105420.610907][27312:27312] CHIP:-: ==== Onboarding payload for Standard Commissioning Flow ==== - [1651105420.610962][27312:27312] CHIP:SVR: SetupQRCode: [MT:-24J0AFN00KA0648G00] - disabled: true - - - label: "Step 3b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - 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: "Step 3c: Using the DUT, parse the THs QR code and follow any steps - needed for the Commissioner/Commissionee to complete the commissioning - process using IP Network" - PICS: MCORE.DD.DISCOVERY_IP - verification: | - Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the - Commissioner/Commissionee commissioning process via IP Network. - - On DUT (CHIP-TOOL), run the following command: - - ./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00 - The DUT successfully parses the QR code and commissions the TH onto the Matter network. - - [1651105530854] [95067:65607294] CHIP: [CTL] Received CommissioningComplete response - [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' - [1651105530854] [95067:65607294] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' - [1651105530854] [95067:65607294] CHIP: [CTL] Performing next commissioning step 'Cleanup' - [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' - [1651105530854] [95067:65607294] CHIP: [TOO] Device commissioning completed with success - - On TH (ALL-CLUSTERS-APP), Ensure the following log output - - [1651105530.973166][27371:27371] CHIP:SVR: Commissioning completed successfully - [1651105530.973215][27371:27371] CHIP:DIS: Updating services using commissioning mode 0 - disabled: true - - - label: "Step 4a: Standard Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 0 and supports SoftAP for - its Discovery Capability. Ensure the Version bit string follows the - current Matter spec. documentation." - PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope : SoftAP commissioning not currently supported - disabled: true - - - label: "Step 4b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - Out of Scope : SoftAP commissioning not currently supported - SoftAP commissioning not currently supported - Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes - disabled: true - - - label: "Step 4c: Using the DUT, parse the THs QR code and follow any steps - needed for the Commissioner/Commissionee to complete the commissioning - process using SoftAP" - PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope : SoftAP commissioning not currently supported - disabled: true + - label: "Note" + verification: | + Chip-tool command used below are an example to verify the DUT as commissioner test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + disabled: true + + - label: "Preconditions" + verification: | + 1 - DUT is on an operational network and has accurate date, time, timezone, regulatory, and fabric information available. + + 2 - QR Code is printed on the Commissionee device or in additional provided materials (ex: manual, companion app, web service). + + An example onboarding QR code could be "MT:-24J029Q00KA0648G00" (following 5.1.3 "QR Code", Table 34 "Packed Binary Data Structure for Onboarding Payload") which includes: + + - 3-bit Version String=000 + + - 16-bit Vendor ID=0xFFF1 (as defined in section 2.5.2. "Vendor Identifier") + + - 16-bit Product ID=0x8001 (as defined in section 2.5.3. "Product Identifier") + + - 2-bit Custom Flow=10 (Custom Commissioning Flow = 2) + + - 8-bit Discovery Capabilities Bitmask=00000100 (OnNetwork) + + - 12-bit Discriminator=0xF00 + + - 27-bit Passcode=20202021 + + - 4-bit Padding=0000 + + - no variable-length TLV Data included (as defined in section 5.1.3.1. "Payload", subsection "TLV Data") + disabled: true + + - label: + "Step 1a: Standard Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 0 and supports BLE for its + Discovery Capability. Ensure the Version bit string follows the + current Matter spec. documentation." + PICS: MCORE.DD.DISCOVERY_BLE + verification: | + 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 + + [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) + [1667888323.967270][3151:3151] CHIP:DL: Product Id: 32769 (0x8001) + [1667888323.967351][3151:3151] CHIP:DL: Hardware Version: 0 + [1667888323.967409][3151:3151] CHIP:DL: Setup Pin Code (0 for UNKNOWN/ERROR): 20202021 + [1667888323.967489][3151:3151] CHIP:DL: Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00) + [1667888323.967566][3151:3151] CHIP:DL: Manufacturing Date: (not set) + [1667888323.967616][3151:3151] CHIP:DL: Device Type: 65535 (0xFFFF) + [1667888323.967720][3151:3151] CHIP:SVR: SetupQRCode: [MT:-24J042C00KA0648G00] + [1667888323.967788][3151:3151] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1667888323.967841][3151:3151] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J042C00KA0648G00 + [1667888323.967940][3151:3151] CHIP:SVR: Manual pairing code: [34970112332] + [1667888323.968031][3151:3151] CHIP:DMG: Endpoint 0, Cluster 0x0000_001D update version to ea7ea7b8 + disabled: true + + - label: "Step 1b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + 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: + "Step 1c: Using the DUT, parse the THs QR code and follow any steps + needed for the Commissioner/Commissionee to complete the commissioning + process using BLE" + PICS: MCORE.DD.DISCOVERY_BLE + verification: | + 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 + + 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 + [1657232374.956577][370357:370357] CHIP:DIS: Updating services using commissioning mode 0 + disabled: true + + - label: + "Step 2a: Standard Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 0 and supports Wi-Fi PAF + for its Discovery Capability. Ensure the Version bit string follows + the current Matter spec. documentation." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 0 --capabilities 8 + [1719392550.248867][1563:1563] CHIP:SVR: SetupQRCode: [MT:-24J0M3810KA0648G00] + [1719392550.248883][1563:1563] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1719392550.248892][1563:1563] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0M3810KA0648G00 + [1719392550.248911][1563:1563] CHIP:SVR: Manual pairing code: [34970112332] + disabled: true + + - label: "Step 2b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + + $ sudo ./chip-tool payload parse-setup-payload MT:-24J0M3810KA0648G00 + [1719392883.120482][28468:28468] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs + [1719392883.120687][28468:28468] CHIP:SPL: Parsing base38Representation: MT:-24J0M3810KA0648G00 + [1719392883.120839][28468:28468] CHIP:SPL: Version: 0 + [1719392883.120859][28468:28468] CHIP:SPL: VendorID: 65521 + [1719392883.120874][28468:28468] CHIP:SPL: ProductID: 32769 + [1719392883.120890][28468:28468] CHIP:SPL: Custom flow: 0 (STANDARD) + [1719392883.120910][28468:28468] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) + [1719392883.120928][28468:28468] CHIP:SPL: Long discriminator: 3840 (0xf00) + [1719392883.120944][28468:28468] CHIP:SPL: Passcode: 20202021 disabled: true + + - label: + "Step 2c: Using the DUT, parse the TH’s QR code and follow any steps + needed for the Commissioner/Commissionee to complete the commissioning + process using Wi-Fi PAF" + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + + [Verification command to be filled by NXP] + + $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 + MT:-24J0M3810KA0648G00 + + - label: + "Step 3a: Standard Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 0, supports IP Network for + its Discovery Capability and is already on the same IP network as the + DUT commissioner. Ensure the Version bit string follows the current + Matter spec. documentation." + PICS: MCORE.DD.DISCOVERY_IP + verification: | + Use a Commissionee with a QR code that has the Custom Flow field set to 0, supports IP Network for its Discovery Capability, + and is already on the same IP network as the DUT commissioner. Ensure the Version bit string follows the current Matter + specification documentation. + + ./chip-all-clusters-app --custom-flow 0 --capabilities 4 + + On the TH (All-Clusters App), verify that the user + has a QR code available to pass into the DUT + [1651105420.610637][27312:27312] CHIP:DL: Device Configuration: + [1651105420.610695][27312:27312] CHIP:DL: Serial Number: TEST_SN + [1651105420.610727][27312:27312] CHIP:DL: Vendor Id: 65521 (0xFFF1) + [1651105420.610761][27312:27312] CHIP:DL: Product Id: 32769 (0x8001) + [1651105420.610792][27312:27312] CHIP:DL: Hardware Version: 0 + [1651105420.610815][27312:27312] CHIP:DL: Setup Pin Code (0 for UNKNOWN/ERROR): 20202021 + [1651105420.610836][27312:27312] CHIP:DL: Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00) + [1651105420.610864][27312:27312] CHIP:DL: Manufacturing Date: (not set) + [1651105420.610886][27312:27312] CHIP:DL: Device Type: 65535 (0xFFFF) + [1651105420.610907][27312:27312] CHIP:-: ==== Onboarding payload for Standard Commissioning Flow ==== + [1651105420.610962][27312:27312] CHIP:SVR: SetupQRCode: [MT:-24J0AFN00KA0648G00] + disabled: true + + - label: "Step 3b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + 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: + "Step 3c: Using the DUT, parse the THs QR code and follow any steps + needed for the Commissioner/Commissionee to complete the commissioning + process using IP Network" + PICS: MCORE.DD.DISCOVERY_IP + verification: | + Using the DUT, parse the QR code generated by the TH and follow the necessary steps to complete the + Commissioner/Commissionee commissioning process via IP Network. + + On DUT (CHIP-TOOL), run the following command: + + ./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00 + The DUT successfully parses the QR code and commissions the TH onto the Matter network. + + [1651105530854] [95067:65607294] CHIP: [CTL] Received CommissioningComplete response + [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' + [1651105530854] [95067:65607294] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' + [1651105530854] [95067:65607294] CHIP: [CTL] Performing next commissioning step 'Cleanup' + [1651105530854] [95067:65607294] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' + [1651105530854] [95067:65607294] CHIP: [TOO] Device commissioning completed with success + + On TH (ALL-CLUSTERS-APP), Ensure the following log output + + [1651105530.973166][27371:27371] CHIP:SVR: Commissioning completed successfully + [1651105530.973215][27371:27371] CHIP:DIS: Updating services using commissioning mode 0 + disabled: true + + - label: + "Step 4a: Standard Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 0 and supports SoftAP for + its Discovery Capability. Ensure the Version bit string follows the + current Matter spec. documentation." + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning not currently supported + disabled: true + + - label: "Step 4b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + Out of Scope : SoftAP commissioning not currently supported + SoftAP commissioning not currently supported + Verify the QR code is scanned by DUT, chip-tool does not support physically scanning QR codes + disabled: true + + - label: + "Step 4c: Using the DUT, parse the THs QR code and follow any steps + needed for the Commissioner/Commissionee to complete the commissioning + process using SoftAP" + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning not currently supported + disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml index b2f40603d42ed7..029783f3b81427 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_12.yaml @@ -13,249 +13,257 @@ # limitations under the License. # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default -name: 3.3.12. [TC-DD-3.12] Commissioning Flow = 1 (User-Intent Flow) - QR Code - [DUT - Commissioner] +name: + 3.3.12. [TC-DD-3.12] Commissioning Flow = 1 (User-Intent Flow) - QR Code + [DUT - Commissioner] PICS: - - MCORE.ROLE.COMMISSIONER - - MCORE.DD.QR_COMMISSIONING - - MCORE.DD.USER_INTENT_COMM_FLOW + - MCORE.ROLE.COMMISSIONER + - MCORE.DD.QR_COMMISSIONING + - MCORE.DD.USER_INTENT_COMM_FLOW config: - nodeId: 0x12344321 - cluster: "Basic Information" - endpoint: 0 + nodeId: 0x12344321 + cluster: "Basic Information" + endpoint: 0 tests: - - label: "Note" - verification: | - Chip-tool command used below are an example to verify the DUT as commissioner test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. - disabled: true - - - label: "Preconditions" - verification: | - 1 - DUT is on an operational network and has accurate date, time, timezone, regulatory, and fabric information available. - - 2 - 5.1.3 - QR Code is printed on the Commissionee device or in additional provided materials (ex: manual, companion app, web service). - - An example onboarding QR code could be "MT:-24J029Q00KA0648G00" (following 5.1.3 "QR Code", Table 34 "Packed Binary Data Structure for Onboarding Payload") which includes: - - - 3-bit Version String=000 - - - 16-bit Vendor ID=0xFFF1 (as defined in section 2.5.2. "Vendor Identifier") - - - 16-bit Product ID=0x8001 (as defined in section 2.5.3. "Product Identifier") - - - 2-bit Custom Flow=10 (Custom Commissioning Flow = 2) - - - 8-bit Discovery Capabilities Bitmask=00000100 (OnNetwork) - - - 12-bit Discriminator=0xF00 - - - 27-bit Passcode=20202021 - - - 4-bit Padding=0000 - - - no variable-length TLV Data included (as defined in section 5.1.3.1. "Payload", subsection "TLV Data") - disabled: true - - - label: - "Step 1a: User-Intent Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 1 and supports BLE for its - Discovery Capability. Commissionee is NOT in commissioning mode. - Ensure the Version bit string follows the current Matter spec. - documentation." - PICS: MCORE.DD.DISCOVERY_BLE - verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 1, 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 --capabilities 2 --custom-flow 1 --ble-device 1 - On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT - - [1657234110.765249][370717:370717] CHIP:SVR: SetupQRCode: [MT:-24J0YXE00KA0648G00] - [1657234110.765314][370717:370717] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1657234110.765364][370717:370717] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0YXE00KA0648G00 - disabled: true - - - label: "Step 1b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - 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: "Step 1c: DUT parses QR code." - PICS: MCORE.DD.DISCOVERY_BLE - verification: | - 1. Parse the payload of the TH commissionee - - Verify on the DUT (CHIP-TOOL): - ./chip-tool payload parse-setup-payload MT:-24J0YXE00KA0648G00 - - 2. Verify that TH logs do not show the commissionee being commissioned by the DUT. - disabled: true - - - label: "Step 1d: User should follow any TH-specific steps for putting the TH - Commissionee device into commissioning mode and to complete the - commissioning process using BLE." - PICS: MCORE.DD.DISCOVERY_BLE - verification: | - 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: - [1651101988.943015][23212:23212] CHIP:SVR: Commissioning completed successfully - [1651101988.943058][23212:23212] CHIP:DIS: Updating services using commissioning mode 0 - - On TH (ALL-CLUSTER-APP), Ensure the following log output: - ./chip-tool pairing code 1 MT:-24J0YXE00KA0648G00 - [1657234147237] [31454:16822562] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' - [1657234147237] [31454:16822562] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' - [1657234147237] [31454:16822562] CHIP: [CTL] Performing next commissioning step 'Cleanup' - [1657234147237] [31454:16822562] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' - [1657234147237] [31454:16822562] CHIP: [TOO] Device commissioning completed with success - disabled: true - - label: - "Step 2a: User-Intent Commissioning Flow: Use a Commissionee with a QR code that has the - Custom Flow field set to 1 and supports Wi-Fi PAF for its Discovery Capability. Commissionee is NOT in commissioning mode. Ensure the Version bit string follows the current Matter spec. documentation. " - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - - # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 1 --capabilities 8 - [1719393010.693198][1592:1592] CHIP:SVR: SetupQRCode: [MT:-24J0IJ910KA0648G00] - [1719393010.693213][1592:1592] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1719393010.693222][1592:1592] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0IJ910KA0648G00 - [1719393010.693246][1592:1592] CHIP:SVR: Manual pairing code: [749701123365521327694] - disabled: true - - - label: "Step 2b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - WIFI - PAF feature is out of scope for V1.4 - - [Verification command to be filled by NXP] - disabled: true - - - label: "Step 2c: DUT parses QR code." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - - $ sudo ./chip-tool payload parse-setup-payload MT:-24J0IJ910KA0648G00 - [1719393067.811966][28514:28514] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs - [1719393067.812195][28514:28514] CHIP:DL: writing settings to file (/tmp/chip_tool_kvs-PRUpuW) - [1719393067.812351][28514:28514] CHIP:DL: renamed tmp file to file (/tmp/chip_tool_kvs) - [1719393067.812455][28514:28514] CHIP:SPL: Parsing base38Representation: MT:-24J0IJ910KA0648G00 - [1719393067.812626][28514:28514] CHIP:SPL: Version: 0 - [1719393067.812647][28514:28514] CHIP:SPL: VendorID: 65521 - [1719393067.812664][28514:28514] CHIP:SPL: ProductID: 32769 - [1719393067.812679][28514:28514] CHIP:SPL: Custom flow: 1 (USER ACTION REQUIRED) - [1719393067.812698][28514:28514] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) - [1719393067.812714][28514:28514] CHIP:SPL: Long discriminator: 3840 (0xf00) - [1719393067.812729][28514:28514] CHIP:SPL: Passcode: 20202021 - disabled: true - - - label: - "Step 2d: User should follow any TH-specific steps for putting the TH Commissionee device into commissioning - mode and to complete the commissioning process using Wi-Fi PAF." - PICS: MCORE.DD.DISCOVERY_PAF - verification: | - WIFI - PAF feature is out of scope for V1.4 - [Verification command to be filled by NXP] - $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0IJ910KA0648G00 - disabled: true - - - label: - "Step 3a: User-Intent Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 1 and supports IP Network - for its Discovery Capability. Commissionee is NOT in commissioning - mode. Ensure the Version bit string follows the current Matter spec. - documentation." - PICS: MCORE.DD.DISCOVERY_IP - verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 1, supports - IP Network for its Discovery Capability, and is already on the same IP network as the DUT - commissioner. Ensure the Version bit string follows the current Matter specification documentation. - - ./chip-all-clusters-app --custom-flow 1 --capabilities 4 - On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT - [1660353382.200125][249074:249074] CHIP:SVR: SetupQRCode: [MT:-24J029Q00KA0648G00] - [1660353382.200152][249074:249074] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1660353382.200173][249074:249074] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J029Q00KA0648G00 - disabled: true - - - label: "Step 3b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - 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: "Step 3c: DUT parses QR code." - PICS: MCORE.DD.DISCOVERY_IP - verification: | - 1. Parse the payload of the TH commissionee - - Verify on the DUT (CHIP-TOOL): - ./chip-tool payload parse-setup-payload MT:-24J029Q00KA0648G00 - - 2. Verify that TH logs do not show the commissionee being commissioned by the DUT. - disabled: true - - - label: "Step 3d: User should follow any TH-specific steps for putting the TH - Commissionee device into commissioning mode and to complete the - commissioning process using IP Network." - PICS: MCORE.DD.DISCOVERY_IP - verification: | - Using the DUT, parse the QR code generated by the TH and follow the necessary steps to - complete the Commissioner/Commissionee commissioning process via IP Network. - On TH (ALL-CLUSTERS-APP), Ensure the following log output - [1657234324.992098][370755:370755] CHIP:SVR: Commissioning completed successfully - [1657234324.992146][370755:370755] CHIP:DIS: Updating services using commissioning mode 0 - - On DUT (CHIP-TOOL), run the following command: - ./chip-tool pairing code 1 MT:-24J029Q00KA0648G00 - [1657234324847] [31475:16824564] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' - [1657234324847] [31475:16824564] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' - [1657234324847] [31475:16824564] CHIP: [CTL] Performing next commissioning step 'Cleanup' - [1657234324847] [31475:16824564] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' - [1657234324847] [31475:16824564] CHIP: [TOO] Device commissioning completed with success - disabled: true - - - label: - "Step 4a: User-Intent Commissioning Flow: Use a Commissionee with a QR - code that has the Custom Flow field set to 1 and supports SoftAP for - its Discovery Capability. Commissionee is NOT in commissioning mode. - Ensure the Version bit string follows the current Matter spec. - documentation." - PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope : SoftAP commissioning currently not supported - disabled: true - - - label: "Step 4b: Scan the QR code from the previous step using the DUT." - PICS: MCORE.DD.SCAN_QR_CODE - verification: | - Out of Scope : SoftAP commissionin currently not supported - Verify the QR code is scanned by DUT, chip-tool does not support - physically scanning QR codes - disabled: true - - - label: "Step 4c: DUT parses QR code." - PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope : SoftAP commissioning currently not supported - disabled: true - - - label: "Step 4d: User should follow any TH-specific steps for putting the TH - Commissionee device into commissioning mode and to complete the - commissioning process using SoftAP." - PICS: MCORE.DD.DISCOVERY_SOFTAP - verification: | - Out of Scope : SoftAP commissioning currently not supported - disabled: true + - label: "Note" + verification: | + Chip-tool command used below are an example to verify the DUT as commissioner test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + disabled: true + + - label: "Preconditions" + verification: | + 1 - DUT is on an operational network and has accurate date, time, timezone, regulatory, and fabric information available. + + 2 - 5.1.3 - QR Code is printed on the Commissionee device or in additional provided materials (ex: manual, companion app, web service). + + An example onboarding QR code could be "MT:-24J029Q00KA0648G00" (following 5.1.3 "QR Code", Table 34 "Packed Binary Data Structure for Onboarding Payload") which includes: + + - 3-bit Version String=000 + + - 16-bit Vendor ID=0xFFF1 (as defined in section 2.5.2. "Vendor Identifier") + + - 16-bit Product ID=0x8001 (as defined in section 2.5.3. "Product Identifier") + + - 2-bit Custom Flow=10 (Custom Commissioning Flow = 2) + + - 8-bit Discovery Capabilities Bitmask=00000100 (OnNetwork) + + - 12-bit Discriminator=0xF00 + + - 27-bit Passcode=20202021 + + - 4-bit Padding=0000 + + - no variable-length TLV Data included (as defined in section 5.1.3.1. "Payload", subsection "TLV Data") + disabled: true + + - label: + "Step 1a: User-Intent Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 1 and supports BLE for its + Discovery Capability. Commissionee is NOT in commissioning mode. + Ensure the Version bit string follows the current Matter spec. + documentation." + PICS: MCORE.DD.DISCOVERY_BLE + verification: | + Use a Commissionee with a QR code that has the Custom Flow field set to 1, 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 --capabilities 2 --custom-flow 1 --ble-device 1 + On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT + + [1657234110.765249][370717:370717] CHIP:SVR: SetupQRCode: [MT:-24J0YXE00KA0648G00] + [1657234110.765314][370717:370717] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1657234110.765364][370717:370717] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0YXE00KA0648G00 + disabled: true + + - label: "Step 1b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + 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: "Step 1c: DUT parses QR code." + PICS: MCORE.DD.DISCOVERY_BLE + verification: | + 1. Parse the payload of the TH commissionee + + Verify on the DUT (CHIP-TOOL): + ./chip-tool payload parse-setup-payload MT:-24J0YXE00KA0648G00 + + 2. Verify that TH logs do not show the commissionee being commissioned by the DUT. + disabled: true + + - label: + "Step 1d: User should follow any TH-specific steps for putting the TH + Commissionee device into commissioning mode and to complete the + commissioning process using BLE." + PICS: MCORE.DD.DISCOVERY_BLE + verification: | + 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: + [1651101988.943015][23212:23212] CHIP:SVR: Commissioning completed successfully + [1651101988.943058][23212:23212] CHIP:DIS: Updating services using commissioning mode 0 + + On TH (ALL-CLUSTER-APP), Ensure the following log output: + ./chip-tool pairing code 1 MT:-24J0YXE00KA0648G00 + [1657234147237] [31454:16822562] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' + [1657234147237] [31454:16822562] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' + [1657234147237] [31454:16822562] CHIP: [CTL] Performing next commissioning step 'Cleanup' + [1657234147237] [31454:16822562] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' + [1657234147237] [31454:16822562] CHIP: [TOO] Device commissioning completed with success + disabled: true + - label: + "Step 2a: User-Intent Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 1 and supports Wi-Fi PAF + for its Discovery Capability. Commissionee is NOT in commissioning + mode. Ensure the Version bit string follows the current Matter spec. + documentation. " + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + + # ./chip-all-clusters-app --wifi --wifipaf freq_list=2437 --custom-flow 1 --capabilities 8 + [1719393010.693198][1592:1592] CHIP:SVR: SetupQRCode: [MT:-24J0IJ910KA0648G00] + [1719393010.693213][1592:1592] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1719393010.693222][1592:1592] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0IJ910KA0648G00 + [1719393010.693246][1592:1592] CHIP:SVR: Manual pairing code: [749701123365521327694] + disabled: true + + - label: "Step 2b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + WIFI - PAF feature is out of scope for V1.4 + + [Verification command to be filled by NXP] + disabled: true + + - label: "Step 2c: DUT parses QR code." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + + $ sudo ./chip-tool payload parse-setup-payload MT:-24J0IJ910KA0648G00 + [1719393067.811966][28514:28514] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_tool_kvs + [1719393067.812195][28514:28514] CHIP:DL: writing settings to file (/tmp/chip_tool_kvs-PRUpuW) + [1719393067.812351][28514:28514] CHIP:DL: renamed tmp file to file (/tmp/chip_tool_kvs) + [1719393067.812455][28514:28514] CHIP:SPL: Parsing base38Representation: MT:-24J0IJ910KA0648G00 + [1719393067.812626][28514:28514] CHIP:SPL: Version: 0 + [1719393067.812647][28514:28514] CHIP:SPL: VendorID: 65521 + [1719393067.812664][28514:28514] CHIP:SPL: ProductID: 32769 + [1719393067.812679][28514:28514] CHIP:SPL: Custom flow: 1 (USER ACTION REQUIRED) + [1719393067.812698][28514:28514] CHIP:SPL: Discovery Bitmask: 0x08 (Wi-Fi PAF) + [1719393067.812714][28514:28514] CHIP:SPL: Long discriminator: 3840 (0xf00) + [1719393067.812729][28514:28514] CHIP:SPL: Passcode: 20202021 + disabled: true + + - label: + "Step 2d: User should follow any TH-specific steps for putting the TH + Commissionee device into commissioning mode and to complete the + commissioning process using Wi-Fi PAF." + PICS: MCORE.DD.DISCOVERY_PAF + verification: | + WIFI - PAF feature is out of scope for V1.4 + [Verification command to be filled by NXP] + $ sudo ./chip-tool pairing code-wifi 1 n_m_2g nxp12345 MT:-24J0IJ910KA0648G00 + disabled: true + + - label: + "Step 3a: User-Intent Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 1 and supports IP Network + for its Discovery Capability. Commissionee is NOT in commissioning + mode. Ensure the Version bit string follows the current Matter spec. + documentation." + PICS: MCORE.DD.DISCOVERY_IP + verification: | + Use a Commissionee with a QR code that has the Custom Flow field set to 1, supports + IP Network for its Discovery Capability, and is already on the same IP network as the DUT + commissioner. Ensure the Version bit string follows the current Matter specification documentation. + + ./chip-all-clusters-app --custom-flow 1 --capabilities 4 + On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT + [1660353382.200125][249074:249074] CHIP:SVR: SetupQRCode: [MT:-24J029Q00KA0648G00] + [1660353382.200152][249074:249074] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1660353382.200173][249074:249074] CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J029Q00KA0648G00 + disabled: true + + - label: "Step 3b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + 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: "Step 3c: DUT parses QR code." + PICS: MCORE.DD.DISCOVERY_IP + verification: | + 1. Parse the payload of the TH commissionee + + Verify on the DUT (CHIP-TOOL): + ./chip-tool payload parse-setup-payload MT:-24J029Q00KA0648G00 + + 2. Verify that TH logs do not show the commissionee being commissioned by the DUT. + disabled: true + + - label: + "Step 3d: User should follow any TH-specific steps for putting the TH + Commissionee device into commissioning mode and to complete the + commissioning process using IP Network." + PICS: MCORE.DD.DISCOVERY_IP + verification: | + Using the DUT, parse the QR code generated by the TH and follow the necessary steps to + complete the Commissioner/Commissionee commissioning process via IP Network. + On TH (ALL-CLUSTERS-APP), Ensure the following log output + [1657234324.992098][370755:370755] CHIP:SVR: Commissioning completed successfully + [1657234324.992146][370755:370755] CHIP:DIS: Updating services using commissioning mode 0 + + On DUT (CHIP-TOOL), run the following command: + ./chip-tool pairing code 1 MT:-24J029Q00KA0648G00 + [1657234324847] [31475:16824564] CHIP: [CTL] Successfully finished commissioning step 'SendComplete' + [1657234324847] [31475:16824564] CHIP: [CTL] Commissioning stage next step: 'SendComplete' -> 'Cleanup' + [1657234324847] [31475:16824564] CHIP: [CTL] Performing next commissioning step 'Cleanup' + [1657234324847] [31475:16824564] CHIP: [CTL] Successfully finished commissioning step 'Cleanup' + [1657234324847] [31475:16824564] CHIP: [TOO] Device commissioning completed with success + disabled: true + + - label: + "Step 4a: User-Intent Commissioning Flow: Use a Commissionee with a QR + code that has the Custom Flow field set to 1 and supports SoftAP for + its Discovery Capability. Commissionee is NOT in commissioning mode. + Ensure the Version bit string follows the current Matter spec. + documentation." + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning currently not supported + disabled: true + + - label: "Step 4b: Scan the QR code from the previous step using the DUT." + PICS: MCORE.DD.SCAN_QR_CODE + verification: | + Out of Scope : SoftAP commissionin currently not supported + Verify the QR code is scanned by DUT, chip-tool does not support + physically scanning QR codes + disabled: true + + - label: "Step 4c: DUT parses QR code." + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning currently not supported + disabled: true + + - label: + "Step 4d: User should follow any TH-specific steps for putting the TH + Commissionee device into commissioning mode and to complete the + commissioning process using SoftAP." + PICS: MCORE.DD.DISCOVERY_SOFTAP + verification: | + Out of Scope : SoftAP commissioning currently not supported + disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml index 607d40ea72dda4..50f7889fdd06a2 100644 --- a/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml +++ b/src/app/tests/suites/certification/Test_TC_DD_3_13.yaml @@ -68,22 +68,22 @@ tests: documentation." PICS: MCORE.DD.DISCOVERY_BLE verification: | - Use a Commissionee with a QR code that has the Custom Flow field set to 2, - 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 2 --capabilities 2 - On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT - [1657235055.253604][370941:370941] CHIP:-: ==== Onboarding payload for Custom Commissioning Flows ==== - [1657235055.253688][370941:370941] CHIP:SVR: SetupQRCode: [MT:-24J0YXE00KA0648G00] - [1657235055.253736][370941:370941] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: - [1657235055.253774][370941:370941] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0YXE00KA0648G00 + Use a Commissionee with a QR code that has the Custom Flow field set to 2, + 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 2 --capabilities 2 + On the TH (All-Clusters App), verify that the user has a QR code available to pass into the DUT + [1657235055.253604][370941:370941] CHIP:-: ==== Onboarding payload for Custom Commissioning Flows ==== + [1657235055.253688][370941:370941] CHIP:SVR: SetupQRCode: [MT:-24J0YXE00KA0648G00] + [1657235055.253736][370941:370941] CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code: + [1657235055.253774][370941:370941] CHIP:SVR: https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0YXE00KA0648G00 disabled: true - label: "Step 1b: Scan the QR code from the previous step using the DUT." PICS: MCORE.DD.SCAN_QR_CODE verification: | - 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. + 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: "Step 1c: DUT parses QR code."