Test added JUN 28 (#27521)

* Fixes issue: 871 & 568
Modifed tests
TC-CC-6.1
TC-CC-6.2
TC-CC-6.3
TC-CC-6.5
TC-ACE-1.6
Semi-Automated tests
TC-ContentLauncher-10.3
TC-ContentLauncher-10.5
TC-ContentLauncher-10.7

* Auto generated files

* Modified tests
TC-FLW-2.1
TC-PRS-2.1
TC-RH-2.1
TC-TMP-2.1
Semi-Automated test
TC-SC-4.1
Auto generated files

* Restyled by whitespace

* Added new testcases
TC-ICDM-1.1
TC-ICDM-2.1
Added auto generated files

* Modified tests
TC-CONTENTLAUNCHER-10.5
TC-MEDIAPLAYBACK-6.4
Auto generated files

* Added YAML test for TIMESYNC-2.3

* Restyled by prettier-json

---------

Co-authored-by: Restyled.io <commits@restyled.io>

Author: manjunath-grl

examples/darwin-framework-tool/templates/tests/ciTests.json

@@ -1,7 +1,7 @@
 {
     "include": "../../../../src/app/tests/suites/ciTests.json",
     "disable": [
-        "Test_TC_SC_4_2",
+        "Test_TC_SC_4_1",
         "Test_TC_SC_5_2",
         "TestClusterComplexTypes",
         "TestEvents",
@@ -33,8 +33,11 @@
         "DL_LockUnlock",
         "Disabled due to using ICD Management (ICDManagement) cluster, which is provisional on Darwin for now:",
         "TestIcdManagementCluster",
+        "Test_TC_ICDM_1_1",
+        "Test_TC_ICDM_2_1",
         "Disabled due to using Time Synchronization (TimeSynchronization) cluster, which is provisional on Darwin for now:",
         "Test_TC_TIMESYNC_1_1",
+        "Test_TC_TIMESYNC_2_3",
         "TestTimeSynchronization",
         "Disabled due to using provisional Ceramic Filter Monitoring (CeramicFilterMonitoring) cluster:",
         "Test_TC_CFREMON_1_1",

scripts/tests/chiptest/__init__.py

@@ -134,6 +134,7 @@ def _GetInDevelopmentTests() -> Set[str]:
         "TestEqualities.yaml",              # chip-repl does not support pseudo-cluster commands that return a value
         "TestExampleCluster.yaml",          # chip-repl does not load custom pseudo clusters
         "Test_TC_TIMESYNC_1_1.yaml",         # Time sync SDK is not yet ready
+        "Test_TC_TIMESYNC_2_3.yaml",         # Time sync SDK is not yet ready
         "TestAttributesById.yaml",           # chip-repl does not support AnyCommands (06/06/2023)
         "TestCommandsById.yaml",             # chip-repl does not support AnyCommands (06/06/2023)
         "TestEventsById.yaml",               # chip-repl does not support AnyCommands (06/06/2023)

src/app/tests/suites/certification/PICS.yaml

@@ -9463,3 +9463,76 @@ PICS:
     #
     - label: "Does the device implement receiving the Step command?"
       id: FAN.S.C00.Rsp
+
+    #ICD Management
+    #
+    # Server Attribute
+    #
+    - label: "Does the device implement the IdleModeInterval attribute?"
+      id: ICDM.S.A0000
+
+    - label: "Does the device implement the ActiveModeInterval attribute?"
+      id: ICDM.S.A0001
+
+    - label: "Does the device implement the ActiveModeThreshold attribute?"
+      id: ICDM.S.A0002
+
+    - label: "Does the device implement the RegisteredClients attribute?"
+      id: ICDM.S.A0003
+
+    - label: "Does the device implement the IcdCounter attribute?"
+      id: ICDM.S.A0004
+
+    - label:
+          "Does the device implement the ClientsSupportedPerFabric attribute?"
+      id: ICDM.S.A0005
+
+    #
+    # Features
+    #
+    - label: "Does the device support this specific cluster feature?"
+      id: ICDM.S.F00
+
+    #
+    #Commands:
+    #
+    - label:
+          "Does the device implement receiving the StayActiveRequest command?"
+      id: ICDM.S.C03.Rsp
+
+    #
+    #RVC Clean Mode Select
+    #
+    #Feature
+    - label:
+          "Does the device support depending on an On/Off cluster implemented on
+          the same DUT?"
+      id: RVCCLEANMS.S.F00
+
+    - label: "Does the device support the extended status feature?"
+      id: RVCCLEANMS.S.F01
+
+    - label:
+          "Does the device implementation deprecate the ChangeToMode command?"
+      id: RVCCLEANMS.S.F02
+
+    #Server Attributes
+    - label: "Does the device implement the StartUpMode attribute?"
+      id: RVCCLEANMS.S.A0004
+
+    - label: "Does the device implement the OnMode attribute?"
+      id: RVCCLEANMS.S.A0005
+
+    #Server Commands recived
+    - label: "Does the device implement receiving the ChangeToMode command?"
+      id: RVCCLEANMS.S.C00.Rsp
+
+    - label:
+          "Does the device implement receiving the ChangeToModeWithStatus
+          command?"
+      id: RVCCLEANMS.S.C01.Rsp
+
+    #server commands generated
+    - label:
+          "Does the device implement sending the ChangeToModeResponse command?"
+      id: RVCCLEANMS.S.C03.Tx

src/app/tests/suites/certification/Test_TC_ACE_1_6.yaml

@@ -219,10 +219,10 @@ tests:
           Manage privileges for group 0x0103 and maintain the current
           administrative privileges for the TH on the Access Control cluster.
           The following access control list shall be used: List item 1 (TH
-          admin): Privilege: Administer (5) AuthMode: CASE (2) Subjects: [N1]
-          Targets: [{Cluster: AccessControl (0x001f), Endpoint: 0}] List item 2
-          (group Manage access): Privilege: Manage (4) AuthMode: Group (3)
-          Subjects: group 0x0103 ([0x0103]) Targets: {Cluster: Groups (0x001d),
+          admin): Privilege: Administer (5), AuthMode: CASE (2), Subjects: [N1],
+          Targets: [{Cluster: AccessControl (0x001f), Endpoint: 0}]. List item 2
+          (group Manage access): Privilege: Manage (4), AuthMode: Group (3),
+          Subjects: group 0x0103 ([0x0103]), Targets: {Cluster: Groups (0x0004),
           Endpoint: PIXIT.G.ENDPOINT}"
       verification: |
           ./chip-tool accesscontrol write acl '[{ "privilege": 5, "authMode": 2, "subjects": [112233], "targets": [{ "cluster": 31, "endpoint": 0, "deviceType": null }]},{ "privilege": 4, "authMode": 3, "subjects": [259], "targets": [{ "cluster": 4, "endpoint": 0, "deviceType": null }]}]' 1 0

src/app/tests/suites/certification/Test_TC_CC_6_1.yaml

@@ -23,6 +23,9 @@ config:
     nodeId: 0x12344321
     cluster: "Color Control"
     endpoint: 1
+    ConfigWait:
+        type: int16u
+        defaultValue: 5000
 
 tests:
     - label: "Wait for the commissioned device to be retrieved"
@@ -215,6 +218,14 @@ tests:
       cluster: "On/Off"
       command: "Off"
 
+    - label: "Wait to turn Off light"
+      cluster: "DelayCommands"
+      command: "WaitForMs"
+      arguments:
+          values:
+              - name: "ms"
+                value: ConfigWait
+
     - label: "Check on/off attribute value is false after off command"
       cluster: "On/Off"
       command: "readAttribute"

src/app/tests/suites/certification/Test_TC_CC_6_2.yaml

@@ -22,6 +22,9 @@ config:
     nodeId: 0x12344321
     cluster: "Color Control"
     endpoint: 1
+    ConfigWait:
+        type: int16u
+        defaultValue: 5000
 
 tests:
     - label: "Wait for the commissioned device to be retrieved"
@@ -367,6 +370,14 @@ tests:
       cluster: "On/Off"
       command: "Off"
 
+    - label: "Wait to turn Off light"
+      cluster: "DelayCommands"
+      command: "WaitForMs"
+      arguments:
+          values:
+              - name: "ms"
+                value: ConfigWait
+
     - label: "Check on/off attribute value is false after off command"
       cluster: "On/Off"
       command: "readAttribute"

src/app/tests/suites/certification/Test_TC_CC_6_3.yaml

@@ -22,6 +22,9 @@ config:
     nodeId: 0x12344321
     cluster: "Color Control"
     endpoint: 1
+    ConfigWait:
+        type: int16u
+        defaultValue: 5000
 
 tests:
     - label: "Wait for the commissioned device to be retrieved"
@@ -289,6 +292,14 @@ tests:
       cluster: "On/Off"
       command: "Off"
 
+    - label: "Wait to turn Off light"
+      cluster: "DelayCommands"
+      command: "WaitForMs"
+      arguments:
+          values:
+              - name: "ms"
+                value: ConfigWait
+
     - label: "Check on/off attribute value is false after off command"
       cluster: "On/Off"
       command: "readAttribute"

src/app/tests/suites/certification/Test_TC_CC_6_5.yaml

@@ -23,6 +23,9 @@ config:
     nodeId: 0x12344321
     cluster: "Color Control"
     endpoint: 1
+    ConfigWait:
+        type: int16u
+        defaultValue: 5000
 
 tests:
     - label: "Wait for the commissioned device to be retrieved"
@@ -91,6 +94,8 @@ tests:
       verification: |
           ./chip-tool colorcontrol write start-up-color-temperature-mireds 32639 1 1
 
+          Verify DUT responds with a successful (value 0x00) status response On TH(chip-tool) Log and below is the sample log provided for the raspi platform
+
           [1684869285516] [29746:343264] [DMG] WriteResponseMessage =
           [1684869285516] [29746:343264] [DMG] {
           [1684869285516] [29746:343264] [DMG]    AttributeStatusIBs =
@@ -211,3 +216,24 @@ tests:
           constraints:
               minValue: 0
               maxValue: 3
+
+    - label: "Turn Off light that we turned on"
+      PICS: OO.S.C00.Rsp
+      cluster: "On/Off"
+      command: "Off"
+
+    - label: "Wait to turn Off light"
+      cluster: "DelayCommands"
+      command: "WaitForMs"
+      arguments:
+          values:
+              - name: "ms"
+                value: ConfigWait
+
+    - label: "Check on/off attribute value is false after off command"
+      cluster: "On/Off"
+      command: "readAttribute"
+      attribute: "OnOff"
+      PICS: OO.S.A0000
+      response:
+          value: 0