Restyle Modifying the existing DD YAMLs to also include the steps for WiFi-PAF… (#34654)

* Restyled by whitespace

* Restyled by prettier-yaml

---------

Co-authored-by: Restyled.io <[email protected]>

Author: restyled-io[bot]

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

@@ -181,7 +181,13 @@ tests:
           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 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 regulatory domains and includes Channel 149 if it is operating in ETSI regulatory domains."
+    - label:
+          "Step 3c: 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
+          regulatory domains and includes Channel 149 if it is operating in ETSI
+          regulatory domains."
       PICS: MCORE.DD.DISCOVERY_PAF
       verification: |
           TH must start sending Wi-Fi PAF Publish Frames on the default channel and the channel list.
@@ -190,8 +196,7 @@ tests:
           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 3d: DUT starts Wi-Fi PAF scan in its commissioning channel"
       PICS: MCORE.DD.DISCOVERY_PAF
       verification: |
           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

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

@@ -187,7 +187,7 @@ tests:
       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
@@ -200,11 +200,14 @@ tests:
           [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"
+    - 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
 

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

@@ -170,7 +170,9 @@ 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. "
+          "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.
@@ -181,15 +183,13 @@ tests:
           [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."
+    - 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."
+    - 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.
@@ -208,7 +208,9 @@ tests:
       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."
+          "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.

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

@@ -182,7 +182,12 @@ tests:
           [1657235198856] [31506:16834043] CHIP: [TOO] Device commissioning completed with success
       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."
+    - 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.
@@ -218,7 +223,12 @@ tests:
 
       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."
+    - 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.

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

@@ -212,7 +212,10 @@ tests:
           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)"
+    - 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".