Modified scripts jul 26 (#21223)

* Modified sripts
TC-CADMIN-1.13
TC-CC-3.*
TC-CC-4.*
TC-CC-5.*
TC-CC-6.*
TC-CC-7.*
TC-CC-8.1
TC-CC-9.*
TC-DGETH-2.2
TC-DRLK-2.7
TC-LVL-3.1
TC-LVL-4.1
TC-LVL-5.1
TC-LVL-6.1
TC-PCC-2.2
TC-SC-4.2
Removed tests
TC-CADMIN-1.25
TC-CADMIN-1.26

* Added auto generated files

* Modified CC scripts

* auto generated files

* Modified CC-5.2 test

* Added auto generated files

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

@@ -4627,3 +4627,55 @@ PICS:
     - label:
           "Does device support optional key SII in operational discovery mDNS?"
       id: MCORE.SC.T_KEY
+
+    - label: "Does the device support discovery over Bluetooth Low Power (BLE)?"
+      id: MCORE.SC.BLE
+
+    - label: "Does the device support discovery over Wi-Fi?"
+      id: MCORE.SC.WIFI
+
+    - label: "Does the device support discovery over Ethernet?"
+      id: MCORE.SC.ETH
+
+    - label: "Does the device support discovery over Thread?"
+      id: MCORE.SC.THR
+
+    - label:
+          "Does device support optional subtype _V in commissionable node
+          discovery mDNS?"
+      id: MCORE.SC.VENDOR_SUBTYPE
+
+    - label:
+          "Does device support optional subtype _T in commissionable node
+          discovery mDNS?"
+      id: MCORE.SC.DEVTYPE_SUBTYPE
+
+    - label:
+          "Does device support optional key VP in commissionable node discovery
+          mDNS?"
+      id: MCORE.SC.VP_KEY
+
+    - label:
+          "Does device support optional key DT in commissionable node discovery
+          mDNS?"
+      id: MCORE.SC.DT_KEY
+
+    - label:
+          "Does device support optional key DN in commissionable node discovery
+          mDNS?"
+      id: MCORE.SC.DN_KEY
+
+    - label:
+          "Does device support optional key RI in commissionable node discovery
+          mDNS?"
+      id: MCORE.SC.RI_KEY
+
+    - label:
+          "Does device support optional key PH in commissionable node discovery
+          mDNS?"
+      id: MCORE.SC.PH_KEY
+
+    - label:
+          "Does device support optional key PI in commissionable node discovery
+          mDNS?"
+      id: MCORE.SC.PI_KEY

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

@@ -14,7 +14,7 @@
 # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default
 
 name:
-    24.1.13. [TC-CADMIN-1.15] Open commissioning window twice on DUT using BCM
+    24.1.13. [TC-CADMIN-1.13] Open commissioning window twice on DUT using BCM
     then ECM [DUT - Commissionee]
 
 config:

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

@@ -19,6 +19,18 @@ config:
     cluster: "Color Control"
     endpoint: 1
     timeout: 150
+    hueShortestDistance:
+        type: INT8U
+        defaultValue: 150
+    hueLongestDistance:
+        type: INT8U
+        defaultValue: 200
+    hueDirectionUp:
+        type: INT8U
+        defaultValue: 250
+    hueDirectionDown:
+        type: INT8U
+        defaultValue: 170
 
 tests:
     - label: "Wait for the commissioned device to be retrieved"
@@ -40,6 +52,13 @@ tests:
       response:
           value: 1
 
+    - label: "TH writes 0 to the Options attribute"
+      PICS: CC.S.F00 && CC.S.A000f
+      command: "writeAttribute"
+      attribute: "Options"
+      arguments:
+          value: 0
+
     - label: "TH reads CurrentHue attribute from DUT"
       PICS: CC.S.F00 && CC.S.A0000
       command: "readAttribute"
@@ -58,7 +77,7 @@ tests:
       arguments:
           values:
               - name: "hue"
-                value: 150
+                value: hueShortestDistance
               - name: "Direction"
                 value: 0
               - name: "TransitionTime"
@@ -117,7 +136,7 @@ tests:
       command: "readAttribute"
       attribute: "CurrentHue"
       response:
-          value: 150
+          value: hueShortestDistance
 
     - label:
           "TH sends MoveToHue command to DUT another Hue with Direction Longest
@@ -127,7 +146,7 @@ tests:
       arguments:
           values:
               - name: "hue"
-                value: 200
+                value: hueLongestDistance
               - name: "Direction"
                 value: 1
               - name: "TransitionTime"
@@ -186,7 +205,7 @@ tests:
       command: "readAttribute"
       attribute: "CurrentHue"
       response:
-          value: 200
+          value: hueLongestDistance
 
     - label:
           "TH sends MoveToHue command to DUT another Hue with Direction Up and
@@ -196,7 +215,7 @@ tests:
       arguments:
           values:
               - name: "hue"
-                value: 250
+                value: hueDirectionUp
               - name: "Direction"
                 value: 2
               - name: "TransitionTime"
@@ -255,7 +274,7 @@ tests:
       command: "readAttribute"
       attribute: "CurrentHue"
       response:
-          value: 250
+          value: hueDirectionUp
 
     - label:
           "TH sends MoveToHue command to DUT another Hue with Direction Down and
@@ -265,7 +284,7 @@ tests:
       arguments:
           values:
               - name: "hue"
-                value: 200
+                value: hueDirectionDown
               - name: "Direction"
                 value: 3
               - name: "TransitionTime"
@@ -324,7 +343,7 @@ tests:
       command: "readAttribute"
       attribute: "CurrentHue"
       response:
-          value: 200
+          value: hueDirectionDown
 
     - label: "Turn off light that we turned on"
       cluster: "On/Off"