Added Manual scripts (#21748)

* Added Updated Manual Scripts * Added Auto generated File * Fixing restyle Co-authored-by: Justin Wood <[email protected]>
project-chip · Feb 18, 2024 · 508d272 · 508d272
1 parent 7d82572
commit 508d272
Show file tree

Hide file tree

Showing 110 changed files with 6,071 additions and 3,920 deletions.
diff --git a/src/app/tests/suites/certification/PICS.yaml b/src/app/tests/suites/certification/PICS.yaml
@@ -506,15 +506,15 @@ PICS:
     - label:
           "Does the device implement receiving the MoveToColorTemperature
           command?"
-      id: CC.C.C0A.Rsp
+      id: CC.C.C0a.Rsp
 
     - label:
           "Does the device implement receiving the MoveColorTemperature command?"
-      id: CC.C.C4B.Rsp
+      id: CC.C.C4b.Rsp
 
     - label:
           "Does the device implement receiving the StepColorTemperature command?"
-      id: CC.C.C4C.Rsp
+      id: CC.C.C4c.Rsp
 
     - label:
           "Does the device implement receiving the EnhancedMoveToHue command?"
@@ -534,6 +534,10 @@ PICS:
     - label: "Does the device implement receiving the ColorLoopSet command?"
       id: CC.C.C44.Rsp
 
+    - label:
+          "Does the device implement sending the MoveToColorTemperature command?"
+      id: CC.C.C0a.Rsp
+
       # Relative Humidity cluster
     - label: "Does the device implement the MeasuredValue attribute?"
       id: RH.S.A0000
@@ -1939,6 +1943,11 @@ PICS:
           command?"
       id: KEYPADINPUT.S.C00.Rsp
 
+    - label:
+          "Does the DUT support the Keypad Input client cluster, SendKey
+          command?"
+      id: KEYPADINPUT.C.C00.Tx
+
     - label:
           "Does the DUT support the Application Launcher server cluster
           Application Platform feature?"

diff --git a/src/app/tests/suites/certification/Test_TC_BOOL_2_2.yaml b/src/app/tests/suites/certification/Test_TC_BOOL_2_2.yaml
@@ -40,7 +40,7 @@ tests:
       verification: |
           ./chip-tool booleanstate read state-value 1 1
 
-          On TH, verify the StateValue value as FALSE
+          On TH(chip-tool), verify the StateValue value as FALSE
 
           [1646118838.087500][3279:3284] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0045 Attribute 0x0000_0000DataVersion: 2127727071
           [1646118838.087536][3279:3284] CHIP:TOO:   StateValue: FALSE
@@ -57,7 +57,7 @@ tests:
       verification: |
           ./chip-tool booleanstate read state-value 1 1
 
-          On TH, verify the StateValue value as TRUE
+          On TH(chip-tool), verify the StateValue value as TRUE
 
           [1646118838.087500][3279:3284] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0045 Attribute 0x0000_0000DataVersion: 2127727071
           [1646118838.087536][3279:3284] CHIP:TOO:   StateValue: TRUE
@@ -69,15 +69,15 @@ tests:
           Run the below command to start interactive mode
           ./chip-tool interactive start
 
-          Subscribe the event using below command in Interactive mode. Once the event occurs, TH get the subscription message.
+          Subscribe the event using below command in Interactive mode. Once the event occurs, TH(chip-tool) get the subscription message.
 
            booleanstate subscribe-event-by-id 0x0 1 100 2 1
       disabled: true
 
     - label: "Bring the DUT into a state so StateValue is FALSE"
       PICS: BOOL.M.ManuallyControlled && BOOL.S.E00 && BOOL.S.A0000
       verification: |
-          On TH, verify the StateValue value as FALSE
+          On TH(chip-tool), verify the StateValue value as FALSE
 
           [1646119162.628169][3311:3316] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0045 Attribute 0x0000_0000DataVersion: 2127727071
           [1646119162.628207][3311:3316] CHIP:TOO:   StateValue: FALSE
@@ -88,7 +88,7 @@ tests:
       verification: |
           ./chip-tool booleanstate read state-value 1 1
 
-          On TH, verify the StateValue value as FALSE
+          On TH(chip-tool), verify the StateValue value as FALSE
 
           [1646118838.087500][3279:3284] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0045 Attribute 0x0000_0000DataVersion: 2127727071
           [1646118838.087536][3279:3284] CHIP:TOO:   StateValue: FALSE
@@ -97,7 +97,7 @@ tests:
     - label: "Bring the DUT into a state so StateValue is TRUE"
       PICS: BOOL.M.ManuallyControlled && BOOL.S.E00 && BOOL.S.A0000
       verification: |
-          On TH, verify the StateValue value as TRUE
+          On TH(chip-tool), verify the StateValue value as TRUE
 
           [1646119162.628169][3311:3316] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0045 Attribute 0x0000_0000DataVersion: 2127727071
           [1646119162.628207][3311:3316] CHIP:TOO:   StateValue: TRUE
@@ -108,7 +108,7 @@ tests:
       verification: |
           ./chip-tool booleanstate read state-value 1 1
 
-          On TH, verify the StateValue value as TRUE
+          On TH(chip-tool), verify the StateValue value as TRUE
 
           [1646118838.087500][3279:3284] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0045 Attribute 0x0000_0000DataVersion: 2127727071
           [1646118838.087536][3279:3284] CHIP:TOO:   StateValue: TRUE

diff --git a/src/app/tests/suites/certification/Test_TC_BOOL_3_1.yaml b/src/app/tests/suites/certification/Test_TC_BOOL_3_1.yaml
@@ -28,13 +28,18 @@ config:
     endpoint: 0
 
 tests:
+    - label: "Note"
+      verification: |
+          For DUT as client test cases, Chip-tool command used below are an example to verify the functionality. For certification test, we expect DUT should have a capability or way to run the equivalent command.
+      disabled: true
+
     - label:
           "DUT reads all supported mandatory attributes from TH one at a time in
           a manufacturer specific order"
       verification: |
           ./chip-tool booleanstate read state-value 1 1
 
-          Verify read command is received in DUT as client side log
+          Verify read command is received on TH(all-clusters-app) Log successfully
 
           [1658847009.838448][28392:28392] CHIP:IM: Received Read request
           [1658847009.838537][28392:28392] CHIP:DMG: ReadRequestMessage =
@@ -90,7 +95,7 @@ tests:
       verification: |
           ./chip-tool booleanstate read attribute-list 1 1
 
-          Verify none of the optional attributes of the server-side of the cluster is listed  in DUT as client side log
+          Verify none of the optional attributes of the server-side of the cluster is listed  on TH(all-clusters-app) Log
           [1654244313219] [91456:3997555] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0045 Attribute 0x0000_FFFB DataVersion: 2739318439
           [1654244313220] [91456:3997555] CHIP: [TOO]   AttributeList: 6 entries
           [1654244313220] [91456:3997555] CHIP: [TOO]     [1]: 0
@@ -102,7 +107,7 @@ tests:
 
            ./chip-tool booleanstate read state-value 1 1
 
-          Verify read command is received in DUT as client side log
+          Verify read command is received on TH (all-clusters-minimal-app) Log
 
           [1658847009.838448][28392:28392] CHIP:IM: Received Read request
           [1658847009.838537][28392:28392] CHIP:DMG: ReadRequestMessage =

diff --git a/src/app/tests/suites/certification/Test_TC_BRBINFO_1_1.yaml b/src/app/tests/suites/certification/Test_TC_BRBINFO_1_1.yaml
@@ -32,7 +32,7 @@ tests:
       verification: |
           ./chip-tool bridgeddevicebasic read cluster-revision 1 3
 
-          On TH, verify  DUT responsds ClusterRevision attribute as the value 1
+          On TH(chip-tool), verify  DUT responsds ClusterRevision attribute has  value 1
 
           [1657695910.794487][15411:15416] CHIP:TOO: Endpoint: 3 Cluster: 0x0000_0039 Attribute 0x0000_FFFD DataVersion: 2577979325
           [1657695910.794568][15411:15416] CHIP:TOO:   ClusterRevision: 1
@@ -42,7 +42,7 @@ tests:
       verification: |
           ./chip-tool bridgeddevicebasic read  feature-map 1 3
 
-          On TH, verify that DUT responds the  Featuremap  value as 0
+          On TH(chip-tool), verify at DUT responds   Featuremap  value as 0
 
           [1658749277.166884][10254:10259] CHIP:TOO: Endpoint: 3 Cluster: 0x0000_0039 Attribute 0x0000_FFFC DataVersion: 3297319126
           [1658749277.166945][10254:10259] CHIP:TOO:   FeatureMap: 0
@@ -53,7 +53,7 @@ tests:
       verification: |
           ./chip-tool bridgeddevicebasic read attribute-list 1 3
 
-          On TH, verify that DUT responds as list of supported attributes as 7 entries
+          On TH(chip-tool), verify TH(chip-tool)at DUT responds as list of supported attributes as entries matching TH(chip-tool)e PICS items (see column F)
 
           [1658833518.065647][9014:9019] CHIP:TOO: Endpoint: 3 Cluster: 0x0000_0039 Attribute 0x0000_FFFB DataVersion: 270848876
           [1658833518.065723][9014:9019] CHIP:TOO:   AttributeList: 7 entries
@@ -77,7 +77,7 @@ tests:
       verification: |
           ./chip-tool bridgeddevicebasic read accepted-command-list 1 3
 
-          On TH, verify that DUT responds as list of Accepted Commands as 0 entries
+          On TH(chip-tool), verify  DUT responds as list of Accepted Commands as 0 entries
 
           [1657696300.165081][15447:15452] CHIP:TOO: Endpoint: 3 Cluster: 0x0000_0039 Attribute 0x0000_FFF9 DataVersion: 2577979325
           [1657696300.165174][15447:15452] CHIP:TOO:   AcceptedCommandList: 0 entries
@@ -87,7 +87,7 @@ tests:
       verification: |
           ./chip-tool bridgeddevicebasic read generated-command-list 1 3
 
-          On TH, verify that DUT responds as list of GeneratedCommands as 0 entries
+          On TH(chip-tool), verify that DUT responds as list of GeneratedCommands as 0 entries
 
           [1657696328.889936][15454:15459] CHIP:TOO: Endpoint: 3 Cluster: 0x0000_0039 Attribute 0x0000_FFF8 DataVersion: 2577979325
           [1657696328.890017][15454:15459] CHIP:TOO:   GeneratedCommandList: 0 entries