Skip to content

Commit

Permalink
Restyled by whitespace
Browse files Browse the repository at this point in the history
  • Loading branch information
@restyled-commits @manjunath-grl
restyled-commits authored and manjunath-grl committed Dec 1, 2023
1 parent dbc6611 commit ed9515c
Show file tree
Hide file tree
Showing 3 changed files with 27 additions and 27 deletions.
16 changes: 8 additions & 8 deletions src/app/tests/suites/certification/Test_TC_CADMIN_1_3.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ tests:
"Step 2a: TH_CR1 opens a commissioning window on DUT_CE using a
commissioning timeout of PIXIT.CADMIN.CwDuration seconds using ECM"
verification: |
On TH_CR1 send the below command
On TH_CR1 send the below command
./chip-tool pairing open-commissioning-window 1 1 PIXIT.CADMIN.CwDuration 2000 3840
Expand Down Expand Up @@ -208,8 +208,8 @@ tests:
#Issue https://github.com/project-chip/connectedhomeip/issues/26127
- label: "Step 3: TH_CR2 starts a commissioning process with DUT_CE"
verification: |
On TH_CR2 send the below command
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
On TH_CR2 send the below command
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
./chip-tool pairing code 0xCAFE 36177160937 --commissioner-name beta
Expand Down Expand Up @@ -241,9 +241,9 @@ tests:
"Step 4: Verify DUT_CE is now discoverable over DNS-SD with two SRV
Records"
verification: |
On TH_CR2 send the below command
On TH_CR2 send the below command
Verify if the DUT_CE is broadcasting using
Verify if the DUT_CE is broadcasting using
avahi-browse -rt _matter._tcp
Expand Down Expand Up @@ -389,7 +389,7 @@ tests:
#Issue https://github.com/project-chip/connectedhomeip/issues/26127
- label: "Step 9: TH_CR2 opens a commissioning window on DUT_CE using ECM"
verification: |
On TH_CR2 send the below command
On TH_CR2 send the below command
./chip-tool pairing open-commissioning-window 2 1 PIXIT.CADMIN.CwDuration 1000 3840 --commissioner-name beta
Expand Down Expand Up @@ -464,7 +464,7 @@ tests:
#Issue https://github.com/project-chip/connectedhomeip/issues/26127
- label: "Step 12: TH_CR2 opens a commissioning window on DUT_CE using ECM"
verification: |
On TH_CR2 send the below command
On TH_CR2 send the below command
./chip-tool pairing open-commissioning-window 2 1 PIXIT.CADMIN.CwDuration 1000 3840 --commissioner-name beta
Expand Down Expand Up @@ -510,7 +510,7 @@ tests:
"Step 13: TH_CR1 starts a commissioning process with DUT_CE before the
timeout from step 12"
verification: |
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
./chip-tool pairing code 0xCAFE 36177160937
Expand Down
36 changes: 18 additions & 18 deletions src/app/tests/suites/certification/Test_TC_CADMIN_1_5.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ tests:
"Step 2: TH_CR1 opens a commissioning window on DUT_CE using a
commissioning timeout of PIXIT.CADMIN.CwDuration seconds using ECM"
verification: |
On TH_CR1 send the below command
On TH_CR1 send the below command
./chip-tool pairing open-commissioning-window 1 1 PIXIT.CADMIN.CwDuration 1000 3841
Expand Down Expand Up @@ -177,8 +177,8 @@ tests:
#Issue https://github.com/project-chip/connectedhomeip/issues/26127
- label: "Step 4b: TH_CR2 starts a commissioning process with DUT_CE"
verification: |
On TH_CR2 send the below command
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
On TH_CR2 send the below command
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
./chip-tool pairing code 0xCAFE 36177160937 --commissioner-name beta
Expand Down Expand Up @@ -223,7 +223,7 @@ tests:
"Step 5: TH_CR1 opens a new commissioning window on DUT_CE using a
commissioning timeout of PIXIT.CADMIN.CwDuration seconds using ECM"
verification: |
On TH_CR1 send the below command
On TH_CR1 send the below command
./chip-tool pairing open-commissioning-window 1 1 PIXIT.CADMIN.CwDuration 2000 3840
Expand Down Expand Up @@ -282,8 +282,8 @@ tests:
#Issue https://github.com/project-chip/connectedhomeip/issues/26127
- label: "Step 7: TH_CR2 starts a commissioning process with DUT_CE"
verification: |
On TH_CR2 send the below command
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
On TH_CR2 send the below command
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
./chip-tool pairing code 0xCAFE 36177160937 --commissioner-name beta
Expand Down Expand Up @@ -354,7 +354,7 @@ tests:
"Step 10: TH_CR1 opens a commissioning window on DUT_CE using a
commissioning timeout of PIXIT.CADMIN.CwDuration seconds using ECM"
verification: |
On TH_CR1 send the below command
On TH_CR1 send the below command
Below is example command by considering the "\x06\xc7\x56\xdf\xfc\xd7\x22\x65\x34\x52\xa1\x2d\xcd\x94\x5d\x8c\x54\xda\x2b\x0f\x3c\xbd\x1b\x4d\xc3\xf1\xad\xb2\x23\xae\xb2\x6b\x04\x7c\xd2\x4c\x96\x86\x6f\x97\x9b\x1d\x83\xec\x50\xe2\xb4\xae\x30\xcd\xf2\xfd\xb3\x2b\xd8\xa2\x11\xb8\x37\xdc\x94\xed\xcd\x56\xf4\xd1\x43\x77\x19\x10\x76\xbf\xc5\x9d\x99\xb7\xdd\x30\x53\xef\xd6\xf0\x2c\x44\x34\xf2\xbd " as a wrong PakeVerifier value
Expand All @@ -367,15 +367,15 @@ tests:
[1656434435.691287][3836:3842] CHIP:DMG: ClusterId = 0x3c,
[1656434435.691377][3836:3842] CHIP:DMG: CommandId = 0x0,
[1656434435.691456][3836:3842] CHIP:DMG: },
[1656434435.691548][3836:3842] CHIP:DMG:
[1656434435.691548][3836:3842] CHIP:DMG:
[1656434435.691620][3836:3842] CHIP:DMG: StatusIB =
[1656434435.691707][3836:3842] CHIP:DMG: {
[1656434435.691788][3836:3842] CHIP:DMG: status = 0x01 (FAILURE),
[1656434435.691874][3836:3842] CHIP:DMG: cluster-status = 0x3,
[1656434435.691954][3836:3842] CHIP:DMG: },
[1656434435.692041][3836:3842] CHIP:DMG:
[1656434435.692041][3836:3842] CHIP:DMG:
[1656434435.692112][3836:3842] CHIP:DMG: },
[1656434435.692191][3836:3842] CHIP:DMG:
[1656434435.692191][3836:3842] CHIP:DMG:
[1656434435.692257][3836:3842] CHIP:DMG: },
cluster: "LogCommands"
command: "UserPrompt"
Expand Down Expand Up @@ -420,7 +420,7 @@ tests:
"Step 11: TH_CR1 opens a commissioning window on DUT_CE using a
commissioning timeout of PIXIT.CADMIN.CwDuration seconds using ECM"
verification: |
On TH_CR1 send the below command
On TH_CR1 send the below command
./chip-tool pairing open-commissioning-window 1 1 PIXIT.CADMIN.CwDuration 1000 3841
Expand Down Expand Up @@ -475,9 +475,9 @@ tests:
"Step 13: TH_CR1 opens a commissioning window on DUT_CE using a
commissioning timeout of PIXIT.CADMIN.CwDuration seconds using ECM"
verification: |
On TH_CR1 send the below command
On TH_CR1 send the below command
./chip-tool pairing open-commissioning-window 1 1 200 1000 3840
./chip-tool pairing open-commissioning-window 1 1 200 1000 3840
Verify that the DUT_CE is rejecting the opening of second commissioning session with the response status 0x01 failure
Expand All @@ -486,7 +486,7 @@ tests:
[1656405166.757033][5933:5938] CHIP:DMG: ClusterId = 0x3c,
[1656405166.757120][5933:5938] CHIP:DMG: CommandId = 0x0,
[1656405166.757222][5933:5938] CHIP:DMG: },
[1656405166.757333][5933:5938] CHIP:DMG:
[1656405166.757333][5933:5938] CHIP:DMG:
[1656405166.757452][5933:5938] CHIP:DMG: StatusIB =
[1656405166.757557][5933:5938] CHIP:DMG: {
[1656405166.757641][5933:5938] CHIP:DMG: status = 0x01 (FAILURE),
Expand Down Expand Up @@ -529,8 +529,8 @@ tests:
#Issue https://github.com/project-chip/connectedhomeip/issues/26127
- label: "Step 13: TH_CR2 starts a commissioning process with DUT_CE"
verification: |
On TH_CR2 send the below command
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
On TH_CR2 send the below command
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
./chip-tool pairing code 0xCAFE 36177160937 --commissioner-name beta
Expand Down Expand Up @@ -583,8 +583,8 @@ tests:
#Issue https://github.com/project-chip/connectedhomeip/issues/26127
- label: "Step 15: TH_CR2 starts a commissioning process with DUT_CE"
verification: |
On TH_CR2 send the below command
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
On TH_CR2 send the below command
Below is the example when using chip tool as controller (considering 36177160937 as the manual code generated by 1st controller)
./chip-tool pairing code 0xCAFE 36177160937 --commissioner-name beta
Expand Down
2 changes: 1 addition & 1 deletion src/app/tests/suites/certification/Test_TC_CADMIN_1_9.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ tests:
"Step 2: TH_CR1 opens a commissioning window on DUT_CE using a
commissioning timeout of PIXIT.CADMIN.CwDuration seconds using ECM"
verification: |
On TH_CR1 send the below command
On TH_CR1 send the below command
./chip-tool pairing open-commissioning-window 1 1 PIXIT.CADMIN.CwDuration 1000 3841
Expand Down

0 comments on commit ed9515c

Please sign in to comment.