Added Updated Manual scripts (#21797)

* Added Manual scripts * Added Auto generated Files * Added PICS.yaml script * Restyled by clang-format Co-authored-by: Restyled.io <commits@restyled.io>
project-chip · Feb 12, 2024 · 1535508 · 1535508
1 parent 36bfff0
commit 1535508
Show file tree

Hide file tree

Showing 77 changed files with 1,888 additions and 1,698 deletions.
diff --git a/src/app/tests/suites/certification/PICS.yaml b/src/app/tests/suites/certification/PICS.yaml
@@ -1676,6 +1676,11 @@ PICS:
           QueryImageResponse Command?"
       id: OTAP.S.M.UserConsentNeeded
 
+    - label:
+          "Does the DUT support sending the DelayedActionTime field in
+          QueryImageResponse Command?"
+      id: OTAP.S.M.DelayedActionTime
+
     - label: "Does the DUT support sending the AnnounceOTAProvider Command?"
       id: OTAR.C.M.AnnounceOTAProvider
 
@@ -2394,6 +2399,11 @@ PICS:
           NavigateTarget command?"
       id: TGTNAV.S.C00.Rsp
 
+    - label:
+          "Does the DUT support the Target Navigator client cluster,
+          NavigateTarget command?"
+      id: TGTNAV.C.C00.Tx
+
     - label:
           "Does the DUT support the Application Basic server cluster VendorName
           attribute?"
@@ -3219,6 +3229,11 @@ PICS:
           advertisements?"
       id: MCORE.DD.COMMISSIONING_SUBTYPE_T
 
+    - label:
+          "Does the commissioner support fetching DCL data from a device being
+          commissioned?"
+      id: MCORE.DD.FETCH_DCL
+
     #Ethernet Network Diagnostics Cluster
     - label: "Does the device implement the ResetCounts command?"
       id: DGETH.S.C00.Rsp
@@ -5078,6 +5093,9 @@ PICS:
     - label: "Does the Controller DUT support Service Advertising?"
       id: MCORE.SC.ADV
 
+    - label: "Does the Controller DUT support Service Advertising?"
+      id: MCORE.SC.ADV
+
     #133.1. Bridged Device Basic Information Cluster
     - label: "Does the DUT(server) support the DataModelRevision attribute?"
       id: BRBINFO.S.A0000

diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_1.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_1.yaml
@@ -47,7 +47,7 @@ tests:
 
           ./chip-tool  pairing open-commissioning-window 1 1 400 2000 3841
 
-          Controller:
+          On TH1(chip-tool) Log
 
           CHIP:IN: Sending encrypted msg 0xaaaad3464d10 with MessageCounter:0 to 0x0000000000000001 at monotonic time: 5805157 msec
           [1635691999.946536][3822:3827] CHIP:DMG: ICR moving to [CommandSen]
@@ -58,7 +58,7 @@ tests:
           [1635691999.946895][3822:3827] CHIP:IN: Sending plaintext msg 0xffffaa58a960 with MessageCounter:1726016118 to 0x0000000000000000 at monotonic time: 5805158 msec
           [1635691999.946983][3822:3827] CHIP:EM: Flushed pending ack for MessageCounter:3234931243 on exchange 35324i
 
-          Device:
+          On DUT as server side
 
           CHIP minimal mDNS started advertising.
           [1635687658.683388][3792:3792] CHIP:DIS: Failed to find a valid admin pairing. Node ID unknown
@@ -399,6 +399,7 @@ tests:
           ./chip-tool pairing code 1  34995354639
 
           verify you got the following message in the TH log
+
           CHIP:SC: PASESession timed out while waiting for a response from the peer. Expected message type was 33
           CHIP:TOO: Secure Pairing Failed
           CHIP:TOO: Pairing Failure: ../../third_party/connectedhomeip/src/protocols/secure_channel/PASESession.cpp:324: CHIP Error 0x00000032: Timeout
@@ -446,7 +447,7 @@ tests:
           ./chip-tool basic read node-label 2 0
 
           CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0005 DataVersion: 3061847068
-          [1649245950.006849][10116:10121] CHIP:TOO:   NodeLabel: te8
+          [1649245950.006849][10116:10121] CHIP:TOO:   NodeLabel: te5new
           [1649245950.007024][10116:10121] CHIP:EM: Sending Standalone Ack for MessageCounter:12495101 on exchange 24816i
       disabled: true
 

diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_15.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_15.yaml
@@ -143,7 +143,7 @@ tests:
           CHIP:EM: Sending Standalone Ack for MessageCounter:9143157 on exchange 1147i
       disabled: true
 
-    - label: "TH_CR2 sends RemoveFabric with FabricIndex = 2command to DUT_CE"
+    - label: "TH_CR2 sends RemoveFabric with FabricIndex = 2 command to DUT_CE"
       PICS: OPCREDS.S.C0a.Rsp
       verification: |
           on 2nd controller using chip tool, remove fabric with FabricIndex=2
@@ -170,13 +170,13 @@ tests:
           ./chip-tool basic write node-label te5new 2 0
 
            Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter
-          [1651819620.929567][4359:4364] CHIP:CTL: OperationalSessionSetup[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
+          [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
           [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53
 
           ./chip-tool basic read node-label 2 0
 
            Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter
-          [1651819620.929567][4359:4364] CHIP:CTL: OperationalSessionSetup[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
+          [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
           [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53
       disabled: true
 
@@ -210,26 +210,6 @@ tests:
           [1647863260.287515][9294:9299] CHIP:EM: Sending Standalone Ack for MessageCounter:11301761 on exchange 13180i"
       disabled: true
 
-    - label:
-          "Verify DUT_CE is now discoverable over DNS-SD with 2 Operational
-          service records (_matter._tcp SRV records)."
-      verification: |
-          grl@grl-ThinkPad-L480:~/may16_cntrl03/connectedhomeip/examples/chip-tool/out/debug$ avahi-browse -rt _matter._tcp
-          + wlp5s0 IPv6 8E50A59FAF52A809-0000000000000001             _matter._tcp         local
-          + wlp5s0 IPv6 03E707466A904C7E-0000000000000003             _matter._tcp         local
-          = wlp5s0 IPv6 8E50A59FAF52A809-0000000000000001             _matter._tcp         local
-             hostname = [E45F010F27530000.local]
-             address = [fe80::e65f:1ff:fe0f:2753]
-             port = [5540]
-             txt = ["T=1" "SAI=300" "SII=5000"]
-          = wlp5s0 IPv6 03E707466A904C7E-0000000000000003             _matter._tcp         local
-             hostname = [E45F010F27530000.local]
-             address = [fe80::e65f:1ff:fe0f:2753]
-             port = [5540]
-             txt = ["T=1" "SAI=300" "SII=5000"]
-          grl@grl-ThinkPad-L480:~/may16_cntrl03/connectedhomeip/examples/chip-tool/out/debug$
-      disabled: true
-
     - label:
           "TH_CR1 opens a commissioning window on DUT_CE using a commissioning
           timeout of PIXIT.CADMIN.CwDuration seconds using ECM"

diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_16.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_16.yaml
@@ -181,7 +181,7 @@ tests:
           CHIP:EM: Sending Standalone Ack for MessageCounter:9143157 on exchange 1147i
       disabled: true
 
-    - label: "TH_CR2 sends RemoveFabric with FabricIndex = 2command to DUT_CE"
+    - label: "TH_CR2 sends RemoveFabric with FabricIndex = 2 command to DUT_CE"
       PICS: OPCREDS.S.C0a.Rsp
       verification: |
           on 2nd controller using chip tool, remove fabric with FabricIndex=2
@@ -208,13 +208,13 @@ tests:
           ./chip-tool basic write node-label te5new 2 0
 
            Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter
-          [1651819620.929567][4359:4364] CHIP:CTL: OperationalSessionSetup[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
+          [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
           [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53
 
           ./chip-tool basic read node-label 2 0
 
            Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter
-          [1651819620.929567][4359:4364] CHIP:CTL: OperationalSessionSetup[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
+          [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
           [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53
       disabled: true
 

diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_17.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_17.yaml
@@ -203,13 +203,13 @@ tests:
           ./chip-tool basic write node-label te5new 2 0
 
            Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter
-          [1651819620.929567][4359:4364] CHIP:CTL: OperationalSessionSetup[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
+          [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
           [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53
 
           ./chip-tool basic read node-label 2 0
 
            Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter
-          [1651819620.929567][4359:4364] CHIP:CTL: OperationalSessionSetup[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
+          [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
           [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53
       disabled: true
 

diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_18.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_18.yaml
@@ -215,13 +215,13 @@ tests:
           ./chip-tool basic write node-label te5new 2 0
 
            Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter
-          [1651819620.929567][4359:4364] CHIP:CTL: OperationalSessionSetup[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
+          [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
           [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53
 
           ./chip-tool basic read node-label 2 0
 
            Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter
-          [1651819620.929567][4359:4364] CHIP:CTL: OperationalSessionSetup[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
+          [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2
           [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53
       disabled: true
 
@@ -370,3 +370,9 @@ tests:
           [1647863342.982512][9309:9314] CHIP:TOO:      }
           [1647863342.982738][9309:9314] CHIP:EM: Sending Standalone Ack for MessageCounter:5772016 on exchange 3310i
       disabled: true
+
+    - label: "TH_CR2 sends command to TH_CE to read the list of Fabrics"
+      PICS: OPCREDS.C.A0001
+      verification: |
+          verification step to be updated.
+      disabled: true
diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_22.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_22.yaml
@@ -66,7 +66,25 @@ tests:
 
     - label: "Wait for commissioning Window to 901 seconds"
       verification: |
-          Wait for commissioning Window to Timeout
+          On 1st controller chip tool, open commissioning window
+
+          Below is the example when using chip tool as controller
+
+
+          For ECM,
+          ./chip-tool pairing open-commissioning-window 1 1 900 1000 3840
+
+          [1635925713.966786][9695:9700] CHIP:SC: Success status report received. Session was established
+          [1635925713.966839][9695:9700] CHIP:IN: New secure session created for device 0x0000000000000001, key 33!!
+          [1635925713.966938][9695:9700] CHIP:CTL: OpenCommissioningWindow for device ID 1
+          [1635925713.972601][9695:9700] CHIP:DMG: ICR moving to [AddingComm]
+          [1635925713.972705][9695:9700] CHIP:DMG: ICR moving to [AddedComma]
+          [1635925713.972815][9695:9700] CHIP:IN: Prepared encrypted message 0xaaaad9b57d10 to 0x0000000000000001 of type 0x8 and protocolId (0, 1) on exchange 31056i with MessageCounter:0.
+          [1635925713.972876][9695:9700] CHIP:IN: Sending encrypted msg 0xaaaad9b57d10 with MessageCounter:0 to 0x0000000000000001 at monotonic time: 13449459 msec
+          [1635925713.973006][9695:9700] CHIP:DMG: ICR moving to [CommandSen]
+          [1635925713.973061][9695:9700] CHIP:CTL: Manual pairing code: [35484132896]
+          [1635925713.973120][9695:9700] CHIP:CTL: SetupQRCode: [MT:00000CQM00A7F87ZT10]
+          [1635925713.973178][9695:9700] CHIP:EM: Sending Standalone Ack for MessageCounter:1964916542 on exchange 31055i
       disabled: true
 
     - label:

diff --git a/src/app/tests/suites/certification/Test_TC_DD_1_12.yaml b/src/app/tests/suites/certification/Test_TC_DD_1_12.yaml
@@ -75,8 +75,7 @@ tests:
           $  ./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00
           ...
           [1657214364908] [29006:16612760] CHIP: [CTL] Starting commissioning discovery over DNS-SD
-          [1657214364908] [29006:16612760] CHIP: [DL] Browsing for: _matterc._udp,_L3840
-          [1657214365080] [29006:16612761] CHIP: [DL] Mdns: OnBrowseAdd  name: E5EFE5FB9DC494B9, type: _matterc._udp., domain: local., interface: 7        [1657214365080] [29006:16612761] CHIP: [DL] Resolve type=_matterc._udp name=E5EFE5FB9DC494B9 interface=7
+          [1657214364908] [29006:16612760] CHIP: [DL] Browsing for: _matterc._udp,_L3840         [1657214365080] [29006:16612761] CHIP: [DL] Mdns: OnBrowseAdd  name: E5EFE5FB9DC494B9, type: _matterc._udp., domain: local., interface: 7        [1657214365080] [29006:16612761] CHIP: [DL] Resolve type=_matterc._udp name=E5EFE5FB9DC494B9 interface=7
           [1657214365080] [29006:16612761] CHIP: [DL] Mdns : OnNewInterface hostname:DCA6328D2B9F0000.local. fullname:E5EFE5FB9DC494B9._matterc._udp.local. interface: 7        [1657214365082] [29006:16612761] CHIP: [DL] Mdns: OnNewAddress interface: 7 ip:fd54:23a1:c6de:4637:4c4:ee82:2a0f:b5e2
           [1657214365082] [29006:16612761] CHIP: [DL] Mdns: OnNewAddress interface: 7 ip:fe80::1e81:3e0:3865:2d29
           [1657214365082] [29006:16612761] CHIP: [DL] Mdns: OnNewAddress interface: 7 ip:192.168.1.10

diff --git a/src/app/tests/suites/certification/Test_TC_DD_1_5.yaml b/src/app/tests/suites/certification/Test_TC_DD_1_5.yaml
@@ -30,7 +30,6 @@ tests:
     - label:
           "Keep the DUT in packaging and bring in TH NFC scanner close to the
           DUT packaging."
-      PICS: MCORE.DD.SCAN_NFC
       verification: |
           Vendor specific field verification
       disabled: true
@@ -39,15 +38,14 @@ tests:
           "Unpack DUT from its packaging, make sure DUT is not powered on and do
           not put the DUT in pairing mode. Bring in TH NFC scanner close to the
           DUTs NFC tag"
-      PICS: MCORE.DD.SCAN_NFC
       verification: |
           Vendor specific field verification
       disabled: true
 
     - label:
           "Power on DUT and do not put the DUT in pairing mode. Bring in TH NFC
           scanner close to the DUTs NFC tag"
-      PICS: MCORE.DD.PHYSICAL_TAMPERING && MCORE.DD.SCAN_NFC
+      PICS: MCORE.DD.PHYSICAL_TAMPERING
       verification: |
           Vendor specific field verification
       disabled: true
@@ -61,13 +59,13 @@ tests:
     - label:
           "Power on DUT and put the DUT in pairing mode. Bring in TH NFC scanner
           close to NFC tag"
-      PICS: MCORE.DD.PHYSICAL_TAMPERING && MCORE.DD.SCAN_NFC
+      PICS: MCORE.DD.PHYSICAL_TAMPERING
       verification: |
           Vendor specific field verification
       disabled: true
 
     - label: "Power on DUT. Bring in NFC scanner close to NFC tag"
-      PICS: MCORE.DD.PHYSICAL_TAMPERING && MCORE.DD.SCAN_NFC
+      PICS: MCORE.DD.PHYSICAL_TAMPERING
       verification: |
           Vendor specific field verification
       disabled: true
@@ -97,7 +95,6 @@ tests:
       disabled: true
 
     - label: "Using TH NFC scanner - read NFC tag Reader type"
-      PICS: MCORE.DD.SCAN_NFC
       verification: |
           Vendor specific field verification
       disabled: true