updated pICS and removed extra quotes

sumaky · Aug 23, 2024 · 12666ac · 12666ac
1 parent e09c237
commit 12666ac
Showing 1 changed file with 8 additions and 9 deletions.
diff --git a/src/app/tests/suites/certification/Test_TC_DLOG_2_1.yaml b/src/app/tests/suites/certification/Test_TC_DLOG_2_1.yaml
@@ -199,7 +199,7 @@ tests:
           TH_LOG_OK_NORMAL)"
       PICS: MCORE.BDX.Initiator
       verification: |
-          "diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator Length_1234567.txt
+          diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator Length_1234567.txt
 
           On TH(chip-tool), Verify that the DUT sends SendInit message with TransferFileDesignator field set to Length_1234567891234567891
           [1707967645.770994][10882:10885] CHIP:ATM: SendInit
@@ -231,7 +231,7 @@ tests:
           by setting Intent field to . NetworkDiag . CrashLogs"
       PICS: MCORE.BDX.Initiator
       verification: |
-          "diagnosticlogs retrieve-logs-request 0 0 1 0
+          diagnosticlogs retrieve-logs-request 0 0 1 0
 
           On TH(chip-tool), Verify that the DUT responds with Success(0) status code for the RetrieveLogsResponse command Verify that LogContent field contains at most 1024 bytes
 
@@ -266,7 +266,7 @@ tests:
           EndUserSupport, RequestedProtocol= BDX)"
       PICS: MCORE.BDX.Initiator
       verification: |
-          "diagnosticlogs retrieve-logs-request 0 1 1 0
+          diagnosticlogs retrieve-logs-request 0 1 1 0
 
           On TH(chip-tool), Verify that the DUT responds with INVALID_COMMAND for the RetrieveLogsRequest that was sent without TransferFileDesignator
 
@@ -302,7 +302,7 @@ tests:
           RequestedProtocol= BDX, TransferFileDesignator = TH_LOG_OK_NORMAL)"
       PICS: "!MCORE.BDX.Initiator"
       verification: |
-          "diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator Length_1234567.txt
+          diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator Length_1234567.txt
 
           On TH(chip-tool), Verify that the DUT responds with Exhausted(1)  status code for the RetrieveLogsResponse command with the  LogContent field containing at most 1024 bytes
 
@@ -317,7 +317,7 @@ tests:
           TransferFileDesignator = TH_LOG_OK_NORMAL) Repeat this step with
           RequestedProtocol as ResponsePayload"
       verification: |
-          "diagnosticlogs retrieve-logs-request 3 0 1 0 --TransferFileDesignator Length_1234567.txt
+          diagnosticlogs retrieve-logs-request 3 0 1 0 --TransferFileDesignator Length_1234567.txt
 
           On TH(chip-tool), Verify that the DUT responds with INVALID_COMMAND for the RetrieveLogsRequest that was sent invalid Intent(3)
 
@@ -343,9 +343,8 @@ tests:
           RequestedProtocol : RetrieveLogsRequest(Intent =
           EndUserSupport,RequestedProtocol= 2, TransferFileDesignator =
           TH_LOG_OK_NORMAL)"
-      PICS: MCORE.BDX.Initiator
       verification: |
-          "diagnosticlogs retrieve-logs-request 0 2 1 0 --TransferFileDesignator Length_1234567.txt
+          diagnosticlogs retrieve-logs-request 0 2 1 0 --TransferFileDesignator Length_1234567.txt
 
           On TH(chip-tool), Verify that the DUT responds with INVALID_COMMAND for the RetrieveLogsRequest that was sent Invalid RequestedProtocol(2)
 
@@ -385,7 +384,7 @@ tests:
           TH_LOG_ERROR_EMPTY)"
       PICS: MCORE.BDX.Initiator
       verification: |
-          "diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator ''
+          diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator ''
            On TH(chip-tool), Verify that DUT sends RetrieveLogsResponse command to TH with Denied(4) status code.
           [1719990173.360981][8053:8056] CHIP:TOO:   RetrieveLogsResponse: {
           [1719990173.361009][8053:8056] CHIP:TOO:     status: 4
@@ -399,7 +398,7 @@ tests:
           EndUserSupport,RequestedProtocol= BDX, TransferFileDesignator =
           TH_LOG_BAD_LENGTH)"
       verification: |
-          "diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator Length_1234567891234567891234567891212345.txt
+          diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator Length_1234567891234567891234567891212345.txt
 
           On TH(chip-tool), Verify that the DUT responds with CONSTRAINT_ERROR for the RetrieveLogsRequest that was sent Invalid Invalid TransferFileDesignator length(> 32)