Fixing restyle

project-chip · Aug 10, 2022 · d8b4f76 · d8b4f76
1 parent 345fd23
commit d8b4f76
Show file tree

Hide file tree

Showing 95 changed files with 2,556 additions and 2,245 deletions.
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
@@ -52,10 +52,10 @@ tests:
           [1658847009.838766][28392:28392] CHIP:DMG:                         Cluster = 0x45,
           [1658847009.838806][28392:28392] CHIP:DMG:                         Attribute = 0x0000_0000,
           [1658847009.838843][28392:28392] CHIP:DMG:                 }
-          [1658847009.838878][28392:28392] CHIP:DMG:                         
+          [1658847009.838878][28392:28392] CHIP:DMG:
           [1658847009.838909][28392:28392] CHIP:DMG:         ],
-          [1658847009.838943][28392:28392] CHIP:DMG:                 
-          [1658847009.838975][28392:28392] CHIP:DMG:         isFabricFiltered = true, 
+          [1658847009.838943][28392:28392] CHIP:DMG:
+          [1658847009.838975][28392:28392] CHIP:DMG:         isFabricFiltered = true,
           [1658847009.839006][28392:28392] CHIP:DMG:         InteractionModelRevision = 1
           [1658847009.839034][28392:28392] CHIP:DMG: },
           [1658847009.839120][28392:28392] CHIP:DMG: IM RH moving to [GeneratingReports]
@@ -120,10 +120,10 @@ tests:
           [1658847009.838766][28392:28392] CHIP:DMG:                         Cluster = 0x45,
           [1658847009.838806][28392:28392] CHIP:DMG:                         Attribute = 0x0000_0000,
           [1658847009.838843][28392:28392] CHIP:DMG:                 }
-          [1658847009.838878][28392:28392] CHIP:DMG:                         
+          [1658847009.838878][28392:28392] CHIP:DMG:
           [1658847009.838909][28392:28392] CHIP:DMG:         ],
-          [1658847009.838943][28392:28392] CHIP:DMG:                 
-          [1658847009.838975][28392:28392] CHIP:DMG:         isFabricFiltered = true, 
+          [1658847009.838943][28392:28392] CHIP:DMG:
+          [1658847009.838975][28392:28392] CHIP:DMG:         isFabricFiltered = true,
           [1658847009.839006][28392:28392] CHIP:DMG:         InteractionModelRevision = 1
           [1658847009.839034][28392:28392] CHIP:DMG: },
           [1658847009.839120][28392:28392] CHIP:DMG: IM RH moving to [GeneratingReports]

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
@@ -77,7 +77,7 @@ tests:
       verification: |
           ./chip-tool bridgeddevicebasic read accepted-command-list 1 3
 
-          On TH(chip-tool), verify  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(chip-tool), 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

diff --git a/src/app/tests/suites/certification/Test_TC_BRBINFO_2_1.yaml b/src/app/tests/suites/certification/Test_TC_BRBINFO_2_1.yaml
@@ -132,14 +132,14 @@ tests:
 
           NOTE the quotes: single-quote/double-quote/string/double-quote/single-quote
 
-          On TH(chip-tool) verify that DUT sends a success response 
+          On TH(chip-tool) verify that DUT sends a success response
           [1656495932.122094][2236:2241] CHIP:DMG:                         }
-          [1656495932.122264][2236:2241] CHIP:DMG:                                 
+          [1656495932.122264][2236:2241] CHIP:DMG:
           [1656495932.122332][2236:2241] CHIP:DMG:                         StatusIB =
           [1656495932.122398][2236:2241] CHIP:DMG:                         {
           [1656495932.122466][2236:2241] CHIP:DMG:                                 status = 0x00 (SUCCESS),
           [1656495932.122538][2236:2241] CHIP:DMG:                         },
-          [1656495932.122602][2236:2241] CHIP:DMG:                         
+          [1656495932.122602][2236:2241] CHIP:DMG:
           [1656495932.122660][2236:2241] CHIP:DMG:                 },
       disabled: true
 
@@ -249,7 +249,7 @@ tests:
       verification: |
           ./chip-tool bridgeddevicebasic read software-version-string  1 3
 
-          Verify the SoftwareVersionString is of type string and has length of 1 to 64 bytes 
+          Verify the SoftwareVersionString is of type string and has length of 1 to 64 bytes
 
           [1656496498.568951][2362:2367] CHIP:TOO:   SoftwareVersionString: 1.0
       disabled: true

diff --git a/src/app/tests/suites/certification/Test_TC_BRBINFO_2_2.yaml b/src/app/tests/suites/certification/Test_TC_BRBINFO_2_2.yaml
@@ -26,7 +26,7 @@ tests:
           new) TH receives the StartUp event from DUT"
       PICS: BRBINFO.S.E00
       verification: |
-          StartUp is an optional Event - 
+          StartUp is an optional Event -
           As its an optional event we cannot generate the event as of now , hence no example logs provided.
 
 
@@ -43,7 +43,7 @@ tests:
           To verify thi ReachableChanged follow the below procedure
 
           1. ./chip-tool interactive start
-          2. bridgeddevicebasic subscribe reachable 1 60 1 4 
+          2. bridgeddevicebasic subscribe reachable 1 60 1 4
           3. press "u" on bridge-app to change reachable to false for endpoint 4 and see the reachable value has been changed compared with precondition
 
           [1659441181.388547][2392:2397] CHIP:TOO: Endpoint: 4 Cluster: 0x0000_0039 Attribute 0x0000_0011 DataVersion: 2189020906

diff --git a/src/app/tests/suites/certification/Test_TC_BRBINFO_2_3.yaml b/src/app/tests/suites/certification/Test_TC_BRBINFO_2_3.yaml
@@ -59,7 +59,7 @@ tests:
     - label: "DUT reads NodeLabel from the TH"
       PICS: BRBINFO.C.A0005
       verification: |
-          Nodelabel is an optional Attribute - 
+          Nodelabel is an optional Attribute -
 
           ./chip-tool bridgeddevicebasic read node-label 1 3
 

diff --git a/src/app/tests/suites/certification/Test_TC_BR_1.yaml b/src/app/tests/suites/certification/Test_TC_BR_1.yaml
@@ -646,7 +646,7 @@ tests:
           which is an actuator (e.g. light, window covering)"
       PICS: MCORE.BRIDGE
       verification: |
-          From Step 5 output , choose one of the device type and identfy the device from the device librray. 
+          From Step 5 output , choose one of the device type and identfy the device from the device librray.
           For Ex: on-off cluster has been taken as example to run tfurther steps
       disabled: true
 
@@ -672,7 +672,7 @@ tests:
           Verify state change response of the bridged device in TH(chip-tool) Log
 
           [1657522278.539407][16698:16703] CHIP:DMG: {
-          [1657522278.539447][16698:16703] CHIP:DMG:         suppressResponse = false, 
+          [1657522278.539447][16698:16703] CHIP:DMG:         suppressResponse = false,
           [1657522278.539495][16698:16703] CHIP:DMG:         InvokeResponseIBs =
           [1657522278.539545][16698:16703] CHIP:DMG:         [
           [1657522278.539585][16698:16703] CHIP:DMG:                 InvokeResponseIB =
@@ -685,18 +685,18 @@ tests:
           [1657522278.539977][16698:16703] CHIP:DMG:                                         ClusterId = 0x6,
           [1657522278.540039][16698:16703] CHIP:DMG:                                         CommandId = 0x2,
           [1657522278.540097][16698:16703] CHIP:DMG:                                 },
-          [1657522278.540162][16698:16703] CHIP:DMG:                                 
+          [1657522278.540162][16698:16703] CHIP:DMG:
           [1657522278.540214][16698:16703] CHIP:DMG:                                 StatusIB =
           [1657522278.540276][16698:16703] CHIP:DMG:                                 {
           [1657522278.540332][16698:16703] CHIP:DMG:                                         status = 0x00 (SUCCESS),
           [1657522278.540386][16698:16703] CHIP:DMG:                                 },
-          [1657522278.540446][16698:16703] CHIP:DMG:                                 
+          [1657522278.540446][16698:16703] CHIP:DMG:
           [1657522278.540499][16698:16703] CHIP:DMG:                         },
-          [1657522278.540560][16698:16703] CHIP:DMG:                         
+          [1657522278.540560][16698:16703] CHIP:DMG:
           [1657522278.540605][16698:16703] CHIP:DMG:                 },
-          [1657522278.540658][16698:16703] CHIP:DMG:                 
+          [1657522278.540658][16698:16703] CHIP:DMG:
           [1657522278.540696][16698:16703] CHIP:DMG:         ],
-          [1657522278.540744][16698:16703] CHIP:DMG:         
+          [1657522278.540744][16698:16703] CHIP:DMG:
           [1657522278.540783][16698:16703] CHIP:DMG:         InteractionModelRevision = 1
           [1657522278.540825][16698:16703] CHIP:DMG: },
           [1657522278.540916][16698:16703] CHIP:DMG: Received Command Response Status for Endpoint=3 Cluster=0x0000_0006 Command=0x0000_0002 Status=0x0
@@ -719,7 +719,7 @@ tests:
           sensor)"
       PICS: MCORE.BRIDGE
       verification: |
-          From Step 5 output , choose one of the sensor device type and identfy the device from the device librray. 
+          From Step 5 output , choose one of the sensor device type and identfy the device from the device librray.
           For Ex:  temperature sensor, being added to bridge-app as example to run further steps
       disabled: true
 

diff --git a/src/app/tests/suites/certification/Test_TC_BR_2.yaml b/src/app/tests/suites/certification/Test_TC_BR_2.yaml
@@ -32,7 +32,7 @@ tests:
           endpoint"
       PICS: MCORE.BRIDGE
       verification: |
-          Read parts-list and device-list with endpoint 0, and for each of the endpoint listed for endpoint 0 read device-list and parts-list and verify the below log in TH  
+          Read parts-list and device-list with endpoint 0, and for each of the endpoint listed for endpoint 0 read device-list and parts-list and verify the below log in TH
 
           ./chip-tool descriptor read parts-list 1 0
 
@@ -859,8 +859,8 @@ tests:
       verification: |
           Verify step 6 and 7 of TC-BR-1 for bridged device added in step 2 of TC-BR-2
 
-          For actuator, 
-          "From Step 5 output of TC-BR-1 , choose one of the device type and identfy the device from the device librray. 
+          For actuator,
+          "From Step 5 output of TC-BR-1 , choose one of the device type and identfy the device from the device librray.
           For Ex: on-off cluster has been taken as example to run tfurther steps" follow below steps
 
           1) Choose on-off cluster as the bridged devices which is an actuator
@@ -880,7 +880,7 @@ tests:
 
           Verify actual state of the bridged device changes accordingly in TH(chip-tool) Log
           [1657522278.539407][16698:16703] CHIP:DMG: {
-          [1657522278.539447][16698:16703] CHIP:DMG:         suppressResponse = false, 
+          [1657522278.539447][16698:16703] CHIP:DMG:         suppressResponse = false,
           [1657522278.539495][16698:16703] CHIP:DMG:         InvokeResponseIBs =
           [1657522278.539545][16698:16703] CHIP:DMG:         [
           [1657522278.539585][16698:16703] CHIP:DMG:                 InvokeResponseIB =
@@ -893,18 +893,18 @@ tests:
           [1657522278.539977][16698:16703] CHIP:DMG:                                         ClusterId = 0x6,
           [1657522278.540039][16698:16703] CHIP:DMG:                                         CommandId = 0x2,
           [1657522278.540097][16698:16703] CHIP:DMG:                                 },
-          [1657522278.540162][16698:16703] CHIP:DMG:                                 
+          [1657522278.540162][16698:16703] CHIP:DMG:
           [1657522278.540214][16698:16703] CHIP:DMG:                                 StatusIB =
           [1657522278.540276][16698:16703] CHIP:DMG:                                 {
           [1657522278.540332][16698:16703] CHIP:DMG:                                         status = 0x00 (SUCCESS),
           [1657522278.540386][16698:16703] CHIP:DMG:                                 },
-          [1657522278.540446][16698:16703] CHIP:DMG:                                 
+          [1657522278.540446][16698:16703] CHIP:DMG:
           [1657522278.540499][16698:16703] CHIP:DMG:                         },
-          [1657522278.540560][16698:16703] CHIP:DMG:                         
+          [1657522278.540560][16698:16703] CHIP:DMG:
           [1657522278.540605][16698:16703] CHIP:DMG:                 },
-          [1657522278.540658][16698:16703] CHIP:DMG:                 
+          [1657522278.540658][16698:16703] CHIP:DMG:
           [1657522278.540696][16698:16703] CHIP:DMG:         ],
-          [1657522278.540744][16698:16703] CHIP:DMG:         
+          [1657522278.540744][16698:16703] CHIP:DMG:
           [1657522278.540783][16698:16703] CHIP:DMG:         InteractionModelRevision = 1
           [1657522278.540825][16698:16703] CHIP:DMG: },
           [1657522278.540916][16698:16703] CHIP:DMG: Received Command Response Status for Endpoint=3 Cluster=0x0000_0006 Command=0x0000_0002 Status=0x0
@@ -916,8 +916,8 @@ tests:
           [1657004565.254635][4804:4809] CHIP:TOO:   OnOff: TRUE
 
 
-          For sensor 
-          "From Step 5 output , choose one of the sensor device type and identfy the device from the device librray. 
+          For sensor
+          "From Step 5 output , choose one of the sensor device type and identfy the device from the device librray.
           For Ex:  temperature sensor, being added to bridge-app as example to run further steps "follow below steps:
 
           1) Choose a sensor device (e.g. temperature sensor, being added to bridge-app)

diff --git a/src/app/tests/suites/certification/Test_TC_BR_3.yaml b/src/app/tests/suites/certification/Test_TC_BR_3.yaml
@@ -42,7 +42,7 @@ tests:
           "Using manufacturer provided means (i.e. NOT using Matter protocol),
           update the name of this bridged device"
       verification: |
-          Press b in bridge-app 
+          Press b in bridge-app
 
           b
           [1657013342.067936][16436:16443] CHIP:DL: Device[Light 1]: New Name="Light 1b"
@@ -52,7 +52,7 @@ tests:
           "Read the NodeLabel attribute of the Bridged Device Basic Information
           cluster on the same endpoint as in 1a"
       verification: |
-          Read the NodeLabel attribute of the Bridged Device Basic Information cluster with EP 3, verify the name is changed 
+          Read the NodeLabel attribute of the Bridged Device Basic Information cluster with EP 3, verify the name is changed
 
           ./chip-tool bridgeddevicebasic read node-label 1 3
 
@@ -73,7 +73,7 @@ tests:
 
     - label: "Read the state (e.g. on/off, brightness) of that bridged device"
       verification: |
-          Read OnOff attribute of On/Off cluster 
+          Read OnOff attribute of On/Off cluster
 
           ./chip-tool onoff read on-off 1 3
 

diff --git a/src/app/tests/suites/certification/Test_TC_BR_4.yaml b/src/app/tests/suites/certification/Test_TC_BR_4.yaml
@@ -33,7 +33,7 @@ tests:
           "Start bridge-app on TH. Commission TH to DUT. Monitor traffic between
           DUT and TH."
       verification: |
-          sudo ./chip-bridge-app 
+          sudo ./chip-bridge-app
 
           ./chip-tool pairing ethernet 1 20202021 3840 fe80::e65f:1ff:fe0f:2753  5540