Restyled by prettier-yaml

project-chip · Jul 21, 2023 · 50f26f6 · 50f26f6
1 parent ee6fac8
commit 50f26f6
Show file tree

Hide file tree

Showing 5 changed files with 104 additions and 59 deletions.
diff --git a/src/app/tests/suites/certification/Test_TC_IDM_4_2.yaml b/src/app/tests/suites/certification/Test_TC_IDM_4_2.yaml
@@ -13,7 +13,8 @@
 # limitations under the License.
 # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default
 
-name: 3.4.2. [TC-IDM-4.2] Subscription Response Messages from DUT Test Cases.
+name:
+    3.4.2. [TC-IDM-4.2] Subscription Response Messages from DUT Test Cases.
     [{DUT_Server}]
 
 PICS:
@@ -32,20 +33,22 @@ tests:
       disabled: true
 
     - label:
-          If the device is has the ICD Management cluster, TH reads from the DUT the IdleModeInterval attribute
-          and sets the SubscriptionMaxIntervalPublisherLimit to the value read.
-          If the device does not have the ICD Management cluster, set the SubscriptionMaxIntervalPublisherLimit
-          to 60 minutes.
+          If the device is has the ICD Management cluster, TH reads from the DUT
+          the IdleModeInterval attribute and sets the
+          SubscriptionMaxIntervalPublisherLimit to the value read. If the device
+          does not have the ICD Management cluster, set the
+          SubscriptionMaxIntervalPublisherLimit to 60 minutes.
       verification: |
           The cluster used in the below command is an example,
           icdmanagement read idle-mode-interval 12344321 0
       disabled: true
 
-    - label: "Step 1: TH sends a subscription message to the DUT with
-          MaxIntervalCeiling set to a value greater than the SubscriptionMaxIntervalPublisherLimit.
-          DUT sends a report data action to the TH. TH sends a success status response to the DUT.
-          DUT sends a Subscribe Response Message to the TH to activate
-          the subscription."
+    - label:
+          "Step 1: TH sends a subscription message to the DUT with
+          MaxIntervalCeiling set to a value greater than the
+          SubscriptionMaxIntervalPublisherLimit. DUT sends a report data action
+          to the TH. TH sends a success status response to the DUT. DUT sends a
+          Subscribe Response Message to the TH to activate the subscription."
       verification: |
           onoff subscribe on-off  100  3900 1 1 --keepSubscriptions true
 
@@ -79,11 +82,12 @@ tests:
           [1686294743.441504][101362:101364] CHIP:DMG: MoveToState ReadClient[0x7fc7ec011c50]: Moving to [Subscripti]
       disabled: true
 
-    - label: "Step 2: TH sends a subscription message to the DUT with
-          MaxIntervalCeiling set to a value less than han the SubscriptionMaxIntervalPublisherLimit.
-          DUT sends a report data action to the TH. TH sends a success status response to
-          the DUT. DUT sends a Subscribe Response Message to the TH to activate
-          the subscription."
+    - label:
+          "Step 2: TH sends a subscription message to the DUT with
+          MaxIntervalCeiling set to a value less than han the
+          SubscriptionMaxIntervalPublisherLimit. DUT sends a report data action
+          to the TH. TH sends a success status response to the DUT. DUT sends a
+          Subscribe Response Message to the TH to activate the subscription."
       verification: |
           basicinformation subscribe location 10 2400 1 0 --keepSubscriptions true
           On the TH(chip-tool), verify a report data message is received and verify it contains the following data :
@@ -459,7 +463,8 @@ tests:
           On TH(chip-tool) Verify that the Subscription succeeds and the DUT sends back the attribute values for the global attribute
       disabled: true
 
-    - label: "Step 11: TH sends a subscription request to subscribe to a global
+    - label:
+          "Step 11: TH sends a subscription request to subscribe to a global
           attribute on an endpoint on all clusters. AttributePath = [[Attribute
           = Global Attribute, Endpoint = EndpointID ]]. +"
       verification: |

diff --git a/src/app/tests/suites/certification/Test_TC_SC_2_1.yaml b/src/app/tests/suites/certification/Test_TC_SC_2_1.yaml
@@ -13,7 +13,8 @@
 # limitations under the License.
 # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default
 
-name: 14.2.1. [TC-SC-2.1] Session Establishment - Passcode Authenticated Session
+name:
+    14.2.1. [TC-SC-2.1] Session Establishment - Passcode Authenticated Session
     Establishment (PASE)
 
 PICS:
@@ -25,7 +26,8 @@ config:
     endpoint: 0
 
 tests:
-    - label: "Initiator constructs and sends a TLV-encoded PBKDFParamRequest
+    - label:
+          "Initiator constructs and sends a TLV-encoded PBKDFParamRequest
           message"
       verification: |
           Verify that the responder receives the PBKDFParamRequest message. Verify that the protocol header is properly constructed: Message Flags: S Flag is set to 0, and DSIZ field is set to 0 Session ID is set to 0 Security Flags: Session Type bits are set to 0 Exchange Flags: I Flag is set to 1 Protocol Opcode is set to 32 (0x20) Protocol ID is set to 0 Verify, if possible in a debug mode, that the PBKDFParamRequest message contains: initiatorRandom - randomly generated 32-bit octet string initiatorSessionId - max size 16-bits unsigned integer that does not overlap with existing initiator session identifiers passcodeId - max size 16-bits unsigned integer hasPBKDFParameters - boolean If hasPBKDFParameters is set to true then PBKDF parameters are not known for the given passcodeId If hasPBKDFParameters is set to false then PBKDF parameters are known for the given passcodeId initiatorSessionParams - optional session-parameter-struct which contains SESSION_IDLE_INTERVAL - max size 32-bits unsigned integer SESSION_ACTIVE_INTERVAL - max size 32-bits unsigned integer SESSION_ACTIVE_THRESHOLD - max size 16-bits unsigned integer

diff --git a/src/app/tests/suites/certification/Test_TC_SC_3_3.yaml b/src/app/tests/suites/certification/Test_TC_SC_3_3.yaml
@@ -47,7 +47,8 @@ tests:
             In the response of above read request command, please verify the below test steps
       disabled: true
 
-    - label: "Step 2b: Responder receives the Sigma1 message and extracts the
+    - label:
+          "Step 2b: Responder receives the Sigma1 message and extracts the
           following initiatorRandom initiatorSessionId destinationId
           resumptionID initiatorResumeMIC initiatorEphPubKey initiatorSEDParams"
       verification: |
@@ -122,7 +123,8 @@ tests:
           [1683973662.299943][21637:21637] CHIP:EM: >>> [E:32997r S:0 M:167307433] (U) Msg RX from 0:D379FA4FB43AD140 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
       disabled: true
 
-    - label: "Step 2c: Responder sends a TLV-encoded Sigma2_Resume message to
+    - label:
+          "Step 2c: Responder sends a TLV-encoded Sigma2_Resume message to
           Initiator containing resumptionID responderSessionID sigma2ResumeMIC
           responderMRPParams"
       verification: |
@@ -179,7 +181,8 @@ tests:
           [1683973662.301880][21648:21650] CHIP:SC: Peer assigned session session ID 688
       disabled: true
 
-    - label: "Step 3a: Responder receives the SigmaFinished message and extracts
+    - label:
+          "Step 3a: Responder receives the SigmaFinished message and extracts
           the following 1.ProtocolId 2.ProtocolCode"
       verification: |
           On Responder(chip-tool),  verify that responder(chip-tool) received  the SigmaFinished(The status report should be GeneralCode:SUCCESS,