diff --git a/src/app/tests/suites/certification/Test_TC_CNET_4_12.yaml b/src/app/tests/suites/certification/Test_TC_CNET_4_12.yaml index 8180610da3e8ec..3c2b11b4ba294d 100644 --- a/src/app/tests/suites/certification/Test_TC_CNET_4_12.yaml +++ b/src/app/tests/suites/certification/Test_TC_CNET_4_12.yaml @@ -72,7 +72,7 @@ tests: [1659623217.387917][9816:9821] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0031 Attribute 0x0000_0001 DataVersion: 4196844346 [1659623217.388007][9816:9821] CHIP:TOO: Networks: 1 entries [1659623217.388058][9816:9821] CHIP:TOO: [1]: { - [1659623217.388089][9816:9821] CHIP:TOO: NetworkID: 2111111122222222 + [1659623217.388089][9816:9821] CHIP:TOO: NetworkID: 1111111122222221 [1659623217.388110][9816:9821] CHIP:TOO: Connected: TRUE [1659623217.388129][9816:9821] CHIP:TOO: } disabled: true @@ -89,11 +89,11 @@ tests: field set to th_xpan and Breadcrumb field set to 1" PICS: CNET.S.C04.Rsp && CNET.S.C05.Tx verification: | - ./chip-tool networkcommissioning remove-network hex: 1 0 + ./chip-tool networkcommissioning remove-network hex: 1 0 --Breadcrumb 1 Below is an example: - ./chip-tool networkcommissioning remove-network hex:2111111122222222 22 0 + ./chip-tool networkcommissioning remove-network hex:1111111122222221 22 0 --Breadcrumb 1 Via the TH (chip-tool), Verify the NetworkConfigResponse that contains Networking Status value as 0 (success). @@ -112,11 +112,11 @@ tests: PIXIT.CNET.THREAD_2ND_OPERATIONALDATASET and Breadcrumb field set to 1" PICS: CNET.S.C03.Rsp && CNET.S.C05.Tx verification: | - ./chip-tool networkcommissioning add-or-update-thread-network-network hex: 1 0 + ./chip-tool networkcommissioning add-or-update-thread-network-network hex: 1 0 --Breadcrumb 1 Below is an example: - ./chip-tool networkcommissioning add-or-update-thread-network hex:0e080000000000010000000300000c35060004001fffe0020831111111222222220708fd6958bdf99a83e6051000112233445566778899aabbccddeeff030e4f70656e54687265616444656d6b0102123404101fdf27d94ddb7edc69dc3e72a0ca0ae10c0402a0f7f8 22 0 (second network dataset value) + ./chip-tool networkcommissioning add-or-update-thread-network hex:0e08000000000001000035060004001fffe00708fdd235604ef7ccb50c0402a0f7f8051000112233445566778899aabbccddeeff030f4f70656e54687265616444656d6f3104101dfb97da1e39dc596e886f52cb870a84000300000f0208111111112222222201021234 22 0 --Breadcrumb 1(second network dataset value) Via the TH (chip-tool), Verify the NetworkConfigResponse that contains Networking Status value as 0 (success). @@ -139,7 +139,7 @@ tests: [1659623451.276073][9891:9896] CHIP:TOO: Networks: 1 entries [1659623451.276194][9891:9896] CHIP:TOO: [1]: { - [1659623451.276268][9891:9896] CHIP:TOO: NetworkID: 3111111122222222 + [1659623451.276268][9891:9896] CHIP:TOO: NetworkID: 1111111122222222 [1659623451.276326][9891:9896] CHIP:TOO: Connected: FALSE [1659623451.276381][9891:9896] CHIP:TOO: } disabled: true @@ -150,11 +150,11 @@ tests: field set to 2" PICS: CNET.S.C06.Rsp verification: | - ./chip-tool networkcommissioning connect-network hex: 1 0 + ./chip-tool networkcommissioning connect-network hex: 1 0 --Breadcrumb 2 Below is an example: - ./chip-tool networkcommissioning connect-network hex:3111111122222222 22 0 --Breadcrumb 2 + ./chip-tool networkcommissioning connect-network hex:1111111122222222 22 0 --Breadcrumb 2 Via the TH (chip-tool), Verify the ConnectNetworkResponse that contains Networking Status value as 0 (success). @@ -171,7 +171,17 @@ tests: "Step 8: TH discovers and connects to DUT on the PIXIT.CNET.THREAD_2ND_OPERATIONALDATASET operational network" verification: | - Mark as not applicable and proceed to next step + ./chip-tool networkcommissioning read networks 22 0 + + Via the TH (chip-tool), Verify: + -the Networks attribute has NetworkID that should be as th_xpan(second network id). + -that the connected status should be the type of bool value as TRUE. + + [1659623451.276073][9891:9896] CHIP:TOO: Networks: 1 entries + [1659623451.276194][9891:9896] CHIP:TOO: [1]: { + [1659623451.276268][9891:9896] CHIP:TOO: NetworkID: 1111111122222222 + [1659623451.276326][9891:9896] CHIP:TOO: Connected: TRUE + [1659623451.276381][9891:9896] CHIP:TOO: } disabled: true - label: @@ -179,9 +189,6 @@ tests: cluster of the DUT" PICS: CNET.S.C06.Rsp verification: | - Mark as not applicable and proceed to next step - - ./chip-tool generalcommissioning read breadcrumb 22 0 Verify "breadcrumb value is set to 2" on the TH(Chip-tool) Log: @@ -195,8 +202,6 @@ tests: "Step 10: TH sends ArmFailSafe command to the DUT with ExpiryLengthSeconds set to 0" verification: | - Mark as not applicable and proceed to next step - ./chip-tool generalcommissioning arm-fail-safe 0 1 22 0 Verify "ArmFailSafeResponse" on the TH(Chip-tool) Log: @@ -214,25 +219,54 @@ tests: "Step 11: TH ensures it can communicate on PIXIT.CNET.THREAD_1ST_OPERATIONALDATASET" verification: | - Mark as not applicable and proceed to next step + ./chip-tool networkcommissioning read networks 22 0 + + Via the TH (chip-tool), Verify: + -the Networks attribute has NetworkID that should be as th_xpan(first network id). + -that the connected status should be the type of bool value as TRUE. + + [1659623217.387917][9816:9821] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0031 Attribute 0x0000_0001 DataVersion: 4196844346 + [1659623217.388007][9816:9821] CHIP:TOO: Networks: 1 entries + [1659623217.388058][9816:9821] CHIP:TOO: [1]: { + [1659623217.388089][9816:9821] CHIP:TOO: NetworkID: 1111111122222221 + [1659623217.388110][9816:9821] CHIP:TOO: Connected: TRUE + [1659623217.388129][9816:9821] CHIP:TOO: } disabled: true - label: "Step 12: TH discovers and connects to DUT on the PIXIT.CNET.THREAD_1ST_OPERATIONALDATASET operational network" verification: | - Mark as not applicable and proceed to next step - ./chip-tool networkcommissioning read networks 22 0 - Verify "Networks entiries and its status" on the TH(Chip-tool) Log: + Via the TH (chip-tool), Verify: + -the Networks attribute has NetworkID that should be as th_xpan(first network id). + -that the connected status should be the type of bool value as TRUE. + + [1659623217.387917][9816:9821] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0031 Attribute 0x0000_0001 DataVersion: 4196844346 + [1659623217.388007][9816:9821] CHIP:TOO: Networks: 1 entries + [1659623217.388058][9816:9821] CHIP:TOO: [1]: { + [1659623217.388089][9816:9821] CHIP:TOO: NetworkID: 1111111122222221 + [1659623217.388110][9816:9821] CHIP:TOO: Connected: TRUE + [1659623217.388129][9816:9821] CHIP:TOO: } disabled: true - label: "Step 13: TH sends ArmFailSafe command to the DUT with ExpiryLengthSeconds set to 900" verification: | - Mark as not applicable and proceed to next step + ./chip-tool generalcommissioning arm-fail-safe 900 1 22 0 + + Via the TH (chip-tool), Verify the DUT sends ArmFailSafe with timeout as 900 secs to the TH. + + [1657808518.577084][5979:5984] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0030 Command=0x0000_0001 + [1657808518.577181][5979:5984] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0030 Command 0x0000_0001 + [1657808518.577311][5979:5984] CHIP:TOO: ArmFailSafeResponse: { + [1657808518.577409][5979:5984] CHIP:TOO: errorCode: 0 + [1657808518.577466][5979:5984] CHIP:TOO: debugText: + [1657808518.577518][5979:5984] CHIP:TOO: } + [1657808518.577604][5979:5984] CHIP:DMG: ICR moving to [AwaitingDe] + [1657808518.577705][5979:5984] CHIP:EM: Sending Standalone Ack for MessageCounter:240383707 on exchange 56756i disabled: true - label: @@ -240,7 +274,21 @@ tests: field set to th_xpan and Breadcrumb field set to 1" PICS: CNET.S.C04.Rsp && CNET.S.C05.Tx verification: | - Mark as not applicable and proceed to next step + ./chip-tool networkcommissioning remove-network hex: 1 0 --Breadcrumb 1 + + Below is an example: + + ./chip-tool networkcommissioning remove-network hex:1111111122222221 22 0 --Breadcrumb 1 + + Via the TH (chip-tool), Verify the NetworkConfigResponse that contains Networking Status value as 0 (success). + + [1659623277.664477][9824:9831] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0005 + [1659623277.664556][9824:9831] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0031 Command 0x0000_0005 + [1659623277.664667][9824:9831] CHIP:TOO: NetworkConfigResponse: { + [1659623277.664758][9824:9831] CHIP:TOO: networkingStatus: 0 + [1659623277.664810][9824:9831] CHIP:TOO: networkIndex: 0 + [1659623277.664843][9824:9831] CHIP:TOO: } + [1659623277.664907][9824:9831] CHIP:DMG: ICR moving to [AwaitingDe] disabled: true - label: @@ -249,7 +297,20 @@ tests: PIXIT.CNET.THREAD_2ND_OPERATIONALDATASET and Breadcrumb field set to 1" PICS: CNET.S.C03.Rsp && CNET.S.C05.Tx verification: | - Mark as not applicable and proceed to next step + ./chip-tool networkcommissioning add-or-update-thread-network-network hex: 1 0 --Breadcrumb 1 + + Below is an example: + + ./chip-tool networkcommissioning add-or-update-thread-network hex:0e08000000000001000035060004001fffe00708fdd235604ef7ccb50c0402a0f7f8051000112233445566778899aabbccddeeff030f4f70656e54687265616444656d6f3104101dfb97da1e39dc596e886f52cb870a84000300000f0208111111112222222201021234 22 0 --Breadcrumb 1(second network dataset value) + + Via the TH (chip-tool), Verify the NetworkConfigResponse that contains Networking Status value as 0 (success). + + [1659623353.963125][9870:9875] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0031 Command 0x0000_0005 + [1659623353.963312][9870:9875] CHIP:TOO: NetworkConfigResponse: { + [1659623353.963406][9870:9875] CHIP:TOO: networkingStatus: 0 + [1659623353.963473][9870:9875] CHIP:TOO: networkIndex: 0 + [1659623353.963530][9870:9875] CHIP:TOO: } + [1659623353.963623][9870:9875] CHIP:DMG: ICR moving to [AwaitingDe] disabled: true - label: @@ -258,14 +319,39 @@ tests: PIXIT.CNET.THREAD_2ND_OPERATIONALDATASET and Breadcrumb field set to 3" PICS: CNET.S.C06.Rsp && CNET.S.C07.Tx verification: | - Mark as not applicable and proceed to next step + ./chip-tool networkcommissioning connect-network hex: 1 0 --Breadcrumb 3 + + Below is an example: + + ./chip-tool networkcommissioning connect-network hex:1111111122222222 22 0 --Breadcrumb 3 + + Via the TH (chip-tool), Verify the ConnectNetworkResponse that contains Networking Status value as 0 (success). + + 1 Command=0x0000_0007 + [1659623520.296630][9903:9908] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0031 Command 0x0000_0007 + [1659623520.296853][9903:9908] CHIP:TOO: ConnectNetworkResponse: { + [1659623520.296935][9903:9908] CHIP:TOO: networkingStatus: 0 + [1659623520.296987][9903:9908] CHIP:TOO: errorValue: null + [1659623520.297037][9903:9908] CHIP:TOO: } + [1659623520.297124][9903:9908] CHIP:DMG: ICR moving to [AwaitingDe] disabled: true - label: "Step 17: TH discovers and connects to DUT on the PIXIT.CNET.THREAD_2ND_OPERATIONALDATASET operational network" verification: | - Mark as not applicable and proceed to next step + ./chip-tool networkcommissioning read networks 22 0 + + Via the TH (chip-tool), Verify: + -the Networks attribute has NetworkID that should be as th_xpan(Second network id). + -that the connected status should be the type of bool value as TRUE. + + [1659623217.387917][9816:9821] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0031 Attribute 0x0000_0001 DataVersion: 4196844346 + [1659623217.388007][9816:9821] CHIP:TOO: Networks: 1 entries + [1659623217.388058][9816:9821] CHIP:TOO: [1]: { + [1659623217.388089][9816:9821] CHIP:TOO: NetworkID: 1111111122222222 + [1659623217.388110][9816:9821] CHIP:TOO: Connected: TRUE + [1659623217.388129][9816:9821] CHIP:TOO: } disabled: true - label: @@ -273,16 +359,41 @@ tests: cluster of the DUT" PICS: CNET.S.C06.Rsp verification: | - Mark as not applicable and proceed to next step + ./chip-tool generalcommissioning read breadcrumb 22 0 + + Verify "breadcrumb value is set to 3" on the TH(Chip-tool) Log: + + [1659623558.934419][9911:9917] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0030 Attribute 0x0000_0000 DataVersion: 808037534 + [1659623558.934529][9911:9917] CHIP:TOO: Breadcrumb: 3 + [1659623558.934681][9911:9917] CHIP:EM: Sending Standalone Ack for MessageCounter:244248455 on exchange 8477i disabled: true - label: "Step 19: TH sends the CommissioningComplete command to the DUT" verification: | - Mark as not applicable and proceed to next step + ./chip-tool generalcommissioning commissioning-complete 22 0 + + Via the TH (chip-tool), Verify the DUT sends CommissioningComplete command and the errorCode field is 0(OK). + + [1657734803.411199][7802:7808] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0030 Command 0x0000_0005 + [1657734803.411256][7802:7808] CHIP:TOO: CommissioningCompleteResponse: { + [1657734803.411306][7802:7808] CHIP:TOO: errorCode: 0 + [1657734803.411333][7802:7808] CHIP:TOO: debugText: + [1657734803.411356][7802:7808] CHIP:TOO: } disabled: true - label: "Step 20: TH reads Networks attribute from the DUT" PICS: CNET.S.A0001 verification: | - Mark as not applicable and proceed to next step + ./chip-tool networkcommissioning read networks 22 0 + + Via the TH (chip-tool), Verify: + -the Networks attribute has NetworkID that should be as th_xpan(Second network id). + -that the connected status should be the type of bool value as TRUE. + + [1659623217.387917][9816:9821] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0031 Attribute 0x0000_0001 DataVersion: 4196844346 + [1659623217.388007][9816:9821] CHIP:TOO: Networks: 1 entries + [1659623217.388058][9816:9821] CHIP:TOO: [1]: { + [1659623217.388089][9816:9821] CHIP:TOO: NetworkID: 1111111122222222 + [1659623217.388110][9816:9821] CHIP:TOO: Connected: TRUE + [1659623217.388129][9816:9821] CHIP:TOO: } disabled: true 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 index 8937b63fd15a22..45111b016974d2 100644 --- a/src/app/tests/suites/certification/Test_TC_DLOG_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_DLOG_2_1.yaml @@ -29,138 +29,394 @@ tests: - label: "Precondition" verification: | DUT supports BDX + Length of TransferFileDesignator is zero + Length of TransferFileDesignator is within 32 characters + Length of TransferFileDesignator is equal to 32 characters + Length of TransferFileDesignator is greater than 32 characters + To send a message that mismatches the current transfer mode disabled: true - - label: "Step 1: Reboot DUT" + - label: "Step 1: Commission DUT to TH" verification: | disabled: true - - label: "Step 2: Commission DUT to TH" + - label: + "Step 2: TH sends RetrieveLogsRequest Command to DUT with + RequestedProtocol argument as BDX : RetrieveLogsRequest (Intent = + EndUserSupport, RequestedProtocol= BDX, TransferFileDesignator = + TH_LOG_OK_FULL_LENGTH)" + PICS: MCORE.BDX.Initiator + verification: | + diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator Length_123456789123456789123.txt + + On TH(chip-tool), Verify that the DUT sends SendInit message with TransferFileDesignator field set to Length_1234567891234567891 + + 1707966626.594544][10635:10638] CHIP:ATM: SendInit + [1707966626.594550][10635:10638] CHIP:ATM: Proposed Transfer Control: 0x10 + [1707966626.594558][10635:10638] CHIP:ATM: Range Control: 0x0 + [1707966626.594563][10635:10638] CHIP:ATM: Proposed Max Block Size: 1024 + [1707966626.594569][10635:10638] CHIP:ATM: Start Offset: 0x0000000000000000 + [1707966626.594577][10635:10638] CHIP:ATM: Proposed Max Length: 0x0000000000000000 + [1707966626.594584][10635:10638] CHIP:ATM: File Designator Length: 32 + [1707966626.594588][10635:10638] CHIP:ATM: File Designator: Length_123456789123456789123.txt + + Note: end_user_support_log > 1024 bytes so that BDX inititation happens from DUT + SendInitMsgfromDUT = true + disabled: true + + - label: + "Step 3: if (SendInitMsgfromDUT = true) TH Sends BDX SendAccept + message to DUT" + PICS: MCORE.BDX.Initiator + verification: | + On chip-tool TH will send the SendAccept Message to the DUT + + [1707894873.734698][34353:34356] CHIP:ATM: Sending BDX Message + [1707894873.734710][34353:34356] CHIP:ATM: SendAccept + [1707894873.734715][34353:34356] CHIP:ATM: Transfer Control: 0x10 + [1707894873.734720][34353:34356] CHIP:ATM: Max Block Size: 1024 + [1707894874.235405][34353:34356] CHIP:BDX: Got an event MsgToSend + + On TH(chip-tool), verify that the DUT responds by sending RetrieveLogsResponse Command with Success(0) status code to TH after receiving the SendAccept Message + 1707894874.239127][34353:34356] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0032 Command 0x0000_0001 + [1707894874.239189][34353:34356] CHIP:TOO: RetrieveLogsResponse: { + [1707894874.239208][34353:34356] CHIP:TOO: status: 0 + [1707894874.239219][34353:34356] CHIP:TOO: logContent: + [1707894874.239227][34353:34356] CHIP:TOO: } + + Check for the size of the file that was specified in the File Deginator field of the RetrieveLogsRequest Command sent to DUT and verify that the size is greater than 1024 bytes. + The file: Length_123456789123456789123.txt (as mentioned in the file designator field) is transferred to /tmp folder on the build system and the size is > 1024 bytes + + Note: The file can be stored in any location on the build system. The current SDK imlemnetstion stores the log file transferred using BDX protocol in /tmp folder. + disabled: true + + - label: + "Step 4: if (SendInitMsgfromDUT = false) TH does not send BDX + SendAccept message to DUT" + PICS: MCORE.BDX.Initiator + verification: | + As SendInitMsgfromDUT = true this step is not applicable + disabled: true + + - label: + "Step 5: Repeat Steps from 2 to 4 by setting Intent field to + NetworkDiag and CrashLogs" verification: | disabled: true - label: - "Step 3: TH sends RetrieveLogsRequest Command (Intent = - EndUserSupport,TransferFileDesignator = 'test.txt', RequestedProtocol= - BDX) to DUT" + "Step 2a: TH sends RetrieveLogsRequest Command to DUT with + RequestedProtocol argument as BDX : RetrieveLogsRequest (Intent = + EndUserSupport, RequestedProtocol= BDX, TransferFileDesignator = + TH_LOG_OK_FULL_LENGTH)" + PICS: MCORE.BDX.Initiator + verification: | + Repeating steps from 2 to 4 by setting Intent field to NetworkDiag + + diagnosticlogs retrieve-logs-request 1 1 1 0 --TransferFileDesignator Length_123456789123456789123.txt + + Note: nw_log does not exist and DUT does not initiate the BDX transfer + SendInitMsgfromDUT = false + disabled: true + + - label: + "Step 3a: if (SendInitMsgfromDUT = true) TH Sends BDX SendAccept + message to DUT" + PICS: MCORE.BDX.Initiator verification: | - sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 1 "test.txt" 1 0 + SendInitMsgfromDUT = false this step is not applicable + disabled: true + - label: + "Step 4a: if (SendInitMsgfromDUT = false) TH does not send BDX + SendAccept message to DUT" + PICS: MCORE.BDX.Initiator + verification: | + On TH(chip-tool), verify that the DUT responds by sending RetrieveLogsResponse Command with NoLogs(2) status code to TH and LogContent field is empty - [1651207333.385887][2441:2446] CHIP:DMG: StatusIB = - [1651207333.385937][2441:2446] CHIP:DMG: { - [1651207333.385985][2441:2446] CHIP:DMG: status = 0x00 (SUCCESS), - [1651207333.386037][2441:2446] CHIP:DMG: }, + [1707967219.637228][10723:10726] CHIP:TOO: RetrieveLogsResponse: { + [1707967219.637242][10723:10726] CHIP:TOO: status: 2 + [1707967219.637248][10723:10726] CHIP:TOO: logContent: + [1707967219.637253][10723:10726] CHIP:TOO: } disabled: true - label: - "Step 4: Verify that the DUT initiates a BDX Transfer, sending a BDX - SendInit message with the File Designator field of the message set to - the value of the TransferFileDesignator field of the - RetrieveLogsRequest" + "Step 2b: TH sends RetrieveLogsRequest Command to DUT with + RequestedProtocol argument as BDX : RetrieveLogsRequest (Intent = + EndUserSupport, RequestedProtocol= BDX, TransferFileDesignator = + TH_LOG_OK_FULL_LENGTH)" + PICS: MCORE.BDX.Initiator verification: | - Not Verifiable + Repeating steps from 2 to 4 by setting Intent field to CrashLogs + + diagnosticlogs retrieve-logs-request 2 1 1 0 --TransferFileDesignator Length_123456789123456789123.txt + + Note: crash_log < 1024 Bytes and DUT does not inittiate the BDX transfer + SendInitMsgfromDUT = false disabled: true - - label: "Step 5: TH Sends BDX SendAccept message" - PICS: DLOG.S.C01.Tx + - label: + "Step 3b: if (SendInitMsgfromDUT = true) TH Sends BDX SendAccept + message to DUT" + PICS: MCORE.BDX.Initiator verification: | - Not Verifiable + SendInitMsgfromDUT = false this step is not applicable disabled: true - label: - "Step 6: Verify that DUT sends RetrieveLogsResponse Command,Verify - that the Status field is set to Success,If LogContent size < 1024 - octets,Verify that the BDX transfer is not initiated from DUT Verify - that DUT sends RetrieveLogsResponse command with a Status field set to - Exhausted Note: In this case steps 5 and 6 does not hold good. else - Verify that the BDX transfer is initiated from DUT Verify that the - LogContent field of RetrieveLogsResponse is empty Verify that DUT - sends RetrieveLogsResponse command with a Status field set to Success - Verify that UTCTimeStamp is included in the RetrieveLogsResponse - command Verify that TimeSinceBoot is included in the - RetrieveLogsResponse command Note: In this case steps 5 and 6 holds - good." - PICS: DLOG.S.C01.Tx + "Step 4b: if (SendInitMsgfromDUT = false) TH does not send BDX + SendAccept message to DUT" + PICS: MCORE.BDX.Initiator verification: | - sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 1 "test.txt" 1 0 + On TH(chip-tool), verify that the DUT responds by sending RetrieveLogsResponse Command with Exhausted(1) status code to TH and LogContent field of RetrieveLogsResponse contains at most 1024 bytes - [1651207369.743117][2450:2455] CHIP:DMG: StatusIB = - [1651207369.743155][2450:2455] CHIP:DMG: { - [1651207369.743192][2450:2455] CHIP:DMG: status = 0x00 (SUCCESS), - [1651207369.743228][2450:2455] CHIP:DMG: }, + 1707894938.009997][34371:34374] CHIP:TOO: RetrieveLogsResponse: { + [1707894938.010025][34371:34374] CHIP:TOO: status: 1 + [1707894938.010057][34371:34374] CHIP:TOO: logContent: RetrieveLogsResponse: { + [1707967525.484222][10866:10869] CHIP:TOO: status: 1 + [1707967525.484229][10866:10869] CHIP:TOO: logContent: 353535350A + [1707967525.484233][10866:10869] CHIP:TOO: } disabled: true - label: - "Step 7: TH sends RetrieveLogsRequest Command (Intent = - EndUserSupport,TransferFileDesignator = 'test.txt', RequestedProtocol= - BDX) to DUT" + "Step 6: TH sends RetrieveLogsRequest Command to DUT with + RequestedProtocol argument as BDX : RetrieveLogsRequest(Intent = + EndUserSupport, RequestedProtocol= BDX, TransferFileDesignator = + TH_LOG_OK_NORMAL)" + PICS: MCORE.BDX.Initiator verification: | - sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 1 "test.txt" 1 0 + "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 + [1707967645.770997][10882:10885] CHIP:ATM: Proposed Transfer Control: 0x10 + [1707967645.771001][10882:10885] CHIP:ATM: Range Control: 0x0 + [1707967645.771004][10882:10885] CHIP:ATM: Proposed Max Block Size: 1024 + [1707967645.771009][10882:10885] CHIP:ATM: Start Offset: 0x0000000000000000 + [1707967645.771011][10882:10885] CHIP:ATM: Proposed Max Length: 0x0000000000000000 + [1707967645.771014][10882:10885] CHIP:ATM: File Designator Length: 18 + [1707967645.771018][10882:10885] CHIP:ATM: File Designator: Length_1234567.txt - [1651207386.883337][2457:2462] CHIP:DMG: - [1651207386.883383][2457:2462] CHIP:DMG: StatusIB = - [1651207386.883443][2457:2462] CHIP:DMG: { - [1651207386.883498][2457:2462] CHIP:DMG: status = 0x00 (SUCCESS), - [1651207386.883563][2457:2462] CHIP:DMG: }, + Note: end_user_support_log > 1024 bytes so that BDX inititation happens from DUT + SendInitMsgfromDUT = true" disabled: true - label: - "Step 8: Verify that the DUT initiates a BDX Transfer, sending a BDX - SendInit message with the File Designator field of the message set to - the value of the TransferFileDesignator field of the - RetrieveLogsRequest" - PICS: DLOG.S.C01.Tx + "Step 7: if (SendInitMsgfromDUT = true) TH Sends + StatusReport(GeneralCode: FAILURE, ProtocolId: BDX, ProtocolCode: + TH_LOG_ERROR_TRANSFER_METHOD_NOT_SUPPORTED) to DUT" + PICS: MCORE.BDX.Initiator verification: | - Not Verifiable + Not Verifiable. This step requires additional API for error injection.(Not available in the Chip-tool) + disabled: true + + - label: + "Step 8: TH sends RetrieveLogsRequest Command RequestedProtocol as + ResponsePayload : RetrieveLogsRequest(Intent = + EndUserSupport,RequestedProtocol = ResponsePayload) Repeat this step + by setting Intent field to . NetworkDiag . CrashLogs" + PICS: MCORE.BDX.Initiator + verification: | + "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 + + RetrieveLogsResponse: { + [1707901602.742523][36080:36083] CHIP:TOO: status: 0 + [1707901602.742542][36080:36083] CHIP:TOO: logContent: 31353238303033363031313533353030333730303234303030303234303133653234303230313138333530313331303034373032313533313031316230323330383230323137303630393261383634383836663730643031303730326130383230323038333038323032303430323031303333313064333030623036303936303836343830313635303330343032303133303832303137303036303932613836343838366637306430313037303161303832303136313034383230313564313532343030303132353031663166663336303230353030383030353031383030353032383030353033383030353034383030353035383030353036383030353037383030353038383030353039383030353061383030353062383030353063383030353064383030353065383030353066383030353130383030353131383030353132383030353133383030353134383030353135383030353136383030353137383030353138383030353139383030353161383030353162383030353163383030353164383030353165383030353166383030353230383030353231383030353232383030353233383030353234383030353235383030353236383030353237383030353238383030353239383030353261383030353262383030353263383030353264383030353265383030353266383030353330383030353331383030353332383030353333383030353334383030353335383030353336383030353337383030353338383030353339383030353361383030353362383030353363383030353364383030353365383030353366383030353430383030353431383030353432383030353433383030353434383030353435383030353436383030353437383030353438383030353439383030353461383030353462383030353463383030353464383030353465383030353466383030353530383030353531383030353532383030353533383030353534383030353535383030353536383030353537383030353538383030353539383030353561383030353562383030353563383030353564383030353565383030353566383030353630383030353631383030353632383030353633383031383234303331363263303431333433353334313330333033303330333035333537343333303330333033303330326433303330323430353030323430363030323430373031323430383030313833313763333037613032303130333830313466653334336639353939343737363362363165653435333931333133333834393466653637643865333030623036303936303836343830633733653461363039363038363438303630393630383634383036303936303836343830363039363038363438303630393630383634383036303936303836 + + Repeat this setp by setting Intent filed to NetworkDiag + diagnosticlogs retrieve-logs-request 1 0 1 0 + + On TH(chip-tool), verify that the DUT responds with NoLogs(2) status code to TH for the RetrieveLogsResponse command and LogContent field is empty + + [1707967219.637228][10723:10726] CHIP:TOO: RetrieveLogsResponse: { + [1707967219.637242][10723:10726] CHIP:TOO: status: 2 + [1707967219.637248][10723:10726] CHIP:TOO: logContent: + [1707967219.637253][10723:10726] CHIP:TOO: } + + Repeat this setp by setting Intent filed to Crash_log + diagnosticlogs retrieve-logs-request 2 0 1 0 + + On TH(chip-tool), verify that the DUT responds with success(0) status code to TH for the RetrieveLogsResponse command and LogContent field of RetrieveLogsResponse contains at most 1024 bytes + + [1707982645.639415][11765:11767] CHIP:TOO: RetrieveLogsResponse: { + [1707982645.639457][11765:11767] CHIP:TOO: status: 0 + [1707982645.639489][11765:11767] CHIP:TOO: logContent: logContent: 353535350A + }" disabled: true - label: - "Step 9: TH Sends StatusReport(GeneralCode: FAILURE, ProtocolId: BDX, - ProtocolCode: TRANSFER_METHOD_NOT_SUPPORTED)" + "Step 9: TH sends RetrieveLogsRequest Command to DUT without + TransferFileDesignator argument : RetrieveLogsRequest(Intent = + EndUserSupport, RequestedProtocol= BDX)" + PICS: MCORE.BDX.Initiator verification: | - Not Verifiable + "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 + + [1707924172.241489][42120:42123] CHIP:DMG: InvokeResponseIB = + [1707924172.241494][42120:42123] CHIP:DMG: { + [1707924172.241497][42120:42123] CHIP:DMG: CommandStatusIB = + [1707924172.241500][42120:42123] CHIP:DMG: { + [1707924172.241503][42120:42123] CHIP:DMG: CommandPathIB = + [1707924172.241507][42120:42123] CHIP:DMG: { + [1707924172.241511][42120:42123] CHIP:DMG: EndpointId = 0x0, + [1707924172.241514][42120:42123] CHIP:DMG: ClusterId = 0x32, + [1707924172.241519][42120:42123] CHIP:DMG: CommandId = 0x0, + [1707924172.241527][42120:42123] CHIP:DMG: }, + [1707924172.241536][42120:42123] CHIP:DMG: + [1707924172.241539][42120:42123] CHIP:DMG: StatusIB = + [1707924172.241543][42120:42123] CHIP:DMG: { + [1707924172.241546][42120:42123] CHIP:DMG: status = 0x85 (INVALID_COMMAND), + [1707924172.241549][42120:42123] CHIP:DMG: }, + [1707924172.241553][42120:42123] CHIP:DMG: + [1707924172.241555][42120:42123] CHIP:DMG: }, + [1707924172.241560][42120:42123] CHIP:DMG: + [1707924172.241562][42120:42123] CHIP:DMG: }, + [1707924172.241567][42120:42123] CHIP:DMG: + [1707924172.241573][42120:42123] CHIP:DMG: ], + [1707924172.241577][42120:42123] CHIP:DMG: + [1707924172.241579][42120:42123] CHIP:DMG: InteractionModelRevision = 11 + [1707924172.241582][42120:42123] CHIP:DMG: }," disabled: true - label: - "Step 10: Verify that DUT sends RetrieveLogsResponse command with a - Status field set to Denied" + "Step 10: TH sends RetrieveLogsRequest Command to DUT that does not + support BDX : RetrieveLogsRequest(Intent = EndUserSupport, + RequestedProtocol= BDX, TransferFileDesignator = TH_LOG_OK_NORMAL)" + PICS: "!MCORE.BDX.Initiator" verification: | - Not Verifiable + "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 + + [1707979121.749537][7593:7596] CHIP:TOO: RetrieveLogsResponse: { + [1707979121.749565][7593:7596] CHIP:TOO: status: 1 + [1707979121.749593][7593:7596] CHIP:TOO: logContent: 31353238303033363031313533353030333730303234303030303234303133653234303230313138333530313331303034373032313533313031316230323330383230323137303630393261383634383836663730643031303730326130383230323038333038323032303430323031303333313064333030623036303936303836343830313635303330343032303133303832303137303036303932613836343838366637306430313037303161303832303136313034383230313564313532343030303132353031663166663336303230353030383030353031383030353032383030353033383030353034383030353035383030353036383030353037383030353038383030353039383030353061383030353062383030353063383030353064383030353065383030353066383030353130383030353131383030353132383030353133383030353134383030353135383030353136383030353137383030353138383030353139383030353161383030353162383030353163383030353164383030353165383030353166383030353230383030353231383030353232383030353233383030353234383030353235383030353236383030353237383030353238383030353239383030353261383030353262383030353263383030353264383030353265383030353266383030353330383030353331383030353332383030353333383030353334383030353335383030353336383030353337383030353338383030353339383030353361383030353362383030353363383030353364383030353365383030353366383030353430383030353431383030353432383030353433383030353434383030353435383030353436383030353437383030353438383030353439383030353461383030353462383030353463383030353464383030353465383030353466383030353530383030353531383030353532383030353533383030353534383030353535383030353536383030353537383030353538383030353539383030353561383030353562383030353563383030353564383030353565383030353566383030353630383030353631383030353632383030353633383031383234303331363263303431333433353334313330333033303330333035333537343333303330333033303330326433303330323430353030323430363030323430373031323430383030313833313763333037613032303130333830313466653334336639353939343737363362363165653435333931333133333834393466653637643865333030623036303936303836343830633733653461363039363038363438303630393630383634383036303936303836343830363039363038363438303630393630383634383036303936303836}" disabled: true - label: - "Step 11: TH sends RetrieveLogsRequest Command (Intent = - EndUserSupport, RequestedProtocol = ResponsePayload) to DUT" + "Step 12: TH sends RetrieveLogsRequest Command to DUT with Invalid + RequestedProtocol : RetrieveLogsRequest(Intent = + EndUserSupport,RequestedProtocol= 2, TransferFileDesignator = + TH_LOG_OK_NORMAL)" + PICS: MCORE.BDX.Initiator verification: | - sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 0 "test.txt" 1 0 + "diagnosticlogs retrieve-logs-request 0 2 1 0 --TransferFileDesignator Length_1234567.txt - [1651207416.783607][2465:2470] CHIP:DMG: StatusIB = - [1651207416.783676][2465:2470] CHIP:DMG: { - [1651207416.783722][2465:2470] CHIP:DMG: status = 0x00 (SUCCESS), - [1651207416.783766][2465:2470] CHIP:DMG: }, + On TH(chip-tool), Verify that the DUT responds with INVALID_COMMAND for the RetrieveLogsRequest that was sent Invalid RequestedProtocol(2) + + 707901794.468418][36124:36127] CHIP:DMG: InvokeResponseMessage = + [1707901794.468425][36124:36127] CHIP:DMG: { + [1707901794.468433][36124:36127] CHIP:DMG: suppressResponse = false, + [1707901794.468440][36124:36127] CHIP:DMG: InvokeResponseIBs = + [1707901794.468452][36124:36127] CHIP:DMG: [ + [1707901794.468459][36124:36127] CHIP:DMG: InvokeResponseIB = + [1707901794.468471][36124:36127] CHIP:DMG: { + [1707901794.468477][36124:36127] CHIP:DMG: CommandStatusIB = + [1707901794.468485][36124:36127] CHIP:DMG: { + [1707901794.468492][36124:36127] CHIP:DMG: CommandPathIB = + [1707901794.468501][36124:36127] CHIP:DMG: { + [1707901794.468510][36124:36127] CHIP:DMG: EndpointId = 0x0, + [1707901794.468518][36124:36127] CHIP:DMG: ClusterId = 0x32, + [1707901794.468526][36124:36127] CHIP:DMG: CommandId = 0x0, + [1707901794.468533][36124:36127] CHIP:DMG: }, + [1707901794.468545][36124:36127] CHIP:DMG: + [1707901794.468552][36124:36127] CHIP:DMG: StatusIB = + [1707901794.468560][36124:36127] CHIP:DMG: { + [1707901794.468569][36124:36127] CHIP:DMG: status = 0x85 (INVALID_COMMAND), + [1707901794.468576][36124:36127] CHIP:DMG: }, + [1707901794.468584][36124:36127] CHIP:DMG: + [1707901794.468591][36124:36127] CHIP:DMG: }, + [1707901794.468602][36124:36127] CHIP:DMG: + [1707901794.468608][36124:36127] CHIP:DMG: }, + [1707901794.468619][36124:36127] CHIP:DMG: + [1707901794.468624][36124:36127] CHIP:DMG: ], + [1707901794.468635][36124:36127] CHIP:DMG:" disabled: true - label: - "Step 12: Verify that the BDX transfer is not initiated from DUT, - Verify that the LogContent field of RetrieveLogsResponse has the size - < = 1024 octets" + "Step 13: TH sends RetrieveLogsRequest Command with Invalid + TransferFileDesignator length : RetrieveLogsRequest(Intent = + EndUserSupport,RequestedProtocol= BDX, TransferFileDesignator = + TH_LOG_ERROR_EMPTY)" verification: | - Not Verifiable + "diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator '' + + [1707904517.151453][36678:36681] CHIP:DMG: ICR moving to [ResponseRe] + [1707904517.151489][36678:36681] CHIP:DMG: InvokeResponseMessage = + [1707904517.151501][36678:36681] CHIP:DMG: { + [1707904517.151511][36678:36681] CHIP:DMG: suppressResponse = false, + [1707904517.151522][36678:36681] CHIP:DMG: InvokeResponseIBs = + [1707904517.151541][36678:36681] CHIP:DMG: [ + [1707904517.151548][36678:36681] CHIP:DMG: InvokeResponseIB = + [1707904517.151565][36678:36681] CHIP:DMG: { + [1707904517.151573][36678:36681] CHIP:DMG: CommandStatusIB = + [1707904517.151582][36678:36681] CHIP:DMG: { + [1707904517.151590][36678:36681] CHIP:DMG: CommandPathIB = + [1707904517.151599][36678:36681] CHIP:DMG: { + [1707904517.151613][36678:36681] CHIP:DMG: EndpointId = 0x0, + [1707904517.151627][36678:36681] CHIP:DMG: ClusterId = 0x32, + [1707904517.151640][36678:36681] CHIP:DMG: CommandId = 0x0, + [1707904517.151652][36678:36681] CHIP:DMG: }, + [1707904517.151670][36678:36681] CHIP:DMG: + [1707904517.151681][36678:36681] CHIP:DMG: StatusIB = + [1707904517.151696][36678:36681] CHIP:DMG: { + [1707904517.151708][36678:36681] CHIP:DMG: status = 0x87 (CONSTRAINT_ERROR), + [1707904517.151720][36678:36681] CHIP:DMG: }, + [1707904517.151734][36678:36681] CHIP:DMG: + [1707904517.151745][36678:36681] CHIP:DMG: }, + [1707904517.151763][36678:36681] CHIP:DMG: + [1707904517.151772][36678:36681] CHIP:DMG: }, + [1707904517.151790][36678:36681] CHIP:DMG: + [1707904517.151798][36678:36681] CHIP:DMG: ], + [1707904517.151816][36678:36681] CHIP:DMG: + [1707904517.151824][36678:36681] CHIP:DMG: InteractionModelRevision = 11 + [1707904517.151830][36678:36681] CHIP:DMG: }," disabled: true - label: - "Step 13: Verify that DUT sends RetrieveLogsResponse command with a - Status field set to Success, Verify that UTCTimeStamp is included in - the RetrieveLogsResponse command,Verify that TimeSinceBoot is included - in the RetrieveLogsResponse command" + "Step 14: TH sends RetrieveLogsRequest Command to DUT with Invalid + TransferFileDesignator length : RetrieveLogsRequest(Intent = + EndUserSupport,RequestedProtocol= BDX, TransferFileDesignator = + TH_LOG_BAD_LENGTH)" verification: | - sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 1 "test.txt" 1 0 + "diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator Length_1234567891234567891234567891212345.txt + + On TH(chip-tool), Verify that the DUT responds with CONSTRAINT_ERRORfor the RetrieveLogsRequest that was sent Invalid Invalid TransferFileDesignator length(> 32) - [1651207438.423557][2475:2480] CHIP:DMG: StatusIB = - [1651207438.423594][2475:2480] CHIP:DMG: { - [1651207438.423648][2475:2480] CHIP:DMG: status = 0x00 (SUCCESS), - [1651207438.423708][2475:2480] CHIP:DMG: }, + [1707904517.151453][36678:36681] CHIP:DMG: ICR moving to [ResponseRe] + [1707904517.151489][36678:36681] CHIP:DMG: InvokeResponseMessage = + [1707904517.151501][36678:36681] CHIP:DMG: { + [1707904517.151511][36678:36681] CHIP:DMG: suppressResponse = false, + [1707904517.151522][36678:36681] CHIP:DMG: InvokeResponseIBs = + [1707904517.151541][36678:36681] CHIP:DMG: [ + [1707904517.151548][36678:36681] CHIP:DMG: InvokeResponseIB = + [1707904517.151565][36678:36681] CHIP:DMG: { + [1707904517.151573][36678:36681] CHIP:DMG: CommandStatusIB = + [1707904517.151582][36678:36681] CHIP:DMG: { + [1707904517.151590][36678:36681] CHIP:DMG: CommandPathIB = + [1707904517.151599][36678:36681] CHIP:DMG: { + [1707904517.151613][36678:36681] CHIP:DMG: EndpointId = 0x0, + [1707904517.151627][36678:36681] CHIP:DMG: ClusterId = 0x32, + [1707904517.151640][36678:36681] CHIP:DMG: CommandId = 0x0, + [1707904517.151652][36678:36681] CHIP:DMG: }, + [1707904517.151670][36678:36681] CHIP:DMG: + [1707904517.151681][36678:36681] CHIP:DMG: StatusIB = + [1707904517.151696][36678:36681] CHIP:DMG: { + [1707904517.151708][36678:36681] CHIP:DMG: status = 0x87 (CONSTRAINT_ERROR), + [1707904517.151720][36678:36681] CHIP:DMG: }, + [1707904517.151734][36678:36681] CHIP:DMG: + [1707904517.151745][36678:36681] CHIP:DMG: }, + [1707904517.151763][36678:36681] CHIP:DMG: + [1707904517.151772][36678:36681] CHIP:DMG: }, + [1707904517.151790][36678:36681] CHIP:DMG: + [1707904517.151798][36678:36681] CHIP:DMG: ], + [1707904517.151816][36678:36681] CHIP:DMG: + [1707904517.151824][36678:36681] CHIP:DMG: InteractionModelRevision = 11 + [1707904517.151830][36678:36681] CHIP:DMG: }," disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DLOG_2_2.yaml b/src/app/tests/suites/certification/Test_TC_DLOG_2_2.yaml deleted file mode 100644 index 800553226d6cf0..00000000000000 --- a/src/app/tests/suites/certification/Test_TC_DLOG_2_2.yaml +++ /dev/null @@ -1,116 +0,0 @@ -# Copyright (c) 2021 Project CHIP Authors -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# 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: - 55.2.2. [TC-DLOG-2.2] Diagnostic Logs Cluster Commands Checks without BDX - [DUT-Server] - -PICS: - - DLOG.S - -config: - nodeId: 0x12344321 - cluster: "Basic Information" - endpoint: 0 - -tests: - - label: "Precondition" - verification: | - DUT does not support BDX - disabled: true - - - label: "Step 1: Commission DUT to TH" - verification: | - - disabled: true - - - label: - "Step 2: TH sends RetrieveLogsRequest Command (Intent = - EndUserSupport,TransferFileDesignator = 'test.txt',RequestedProtocol= - BDX) to DUT" - verification: | - sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 0 "test.txt" 1 0 - - [1646209207.288823][3223:3228] CHIP:DMG: InvokeResponseMessage = - [1646209207.288859][3223:3228] CHIP:DMG: { - [1646209207.288893][3223:3228] CHIP:DMG: suppressResponse = false, - [1646209207.288928][3223:3228] CHIP:DMG: InvokeResponseIBs = - [1646209207.288972][3223:3228] CHIP:DMG: [ - [1646209207.289006][3223:3228] CHIP:DMG: InvokeResponseIB = - [1646209207.289056][3223:3228] CHIP:DMG: { - [1646209207.289096][3223:3228] CHIP:DMG: CommandStatusIB = - [1646209207.289146][3223:3228] CHIP:DMG: { - [1646209207.289189][3223:3228] CHIP:DMG: CommandPathIB = - [1646209207.289237][3223:3228] CHIP:DMG: { - [1646209207.289285][3223:3228] CHIP:DMG: EndpointId = 0x0, - [1646209207.289338][3223:3228] CHIP:DMG: ClusterId = 0x32, - [1646209207.289391][3223:3228] CHIP:DMG: CommandId = 0x0, - [1646209207.289434][3223:3228] CHIP:DMG: }, - [1646209207.289479][3223:3228] CHIP:DMG: - [1646209207.289521][3223:3228] CHIP:DMG: StatusIB = - [1646209207.289573][3223:3228] CHIP:DMG: { - [1646209207.289619][3223:3228] CHIP:DMG: status = 0x0, - [1646209207.289666][3223:3228] CHIP:DMG: }, - [1646209207.289715][3223:3228] CHIP:DMG: - [1646209207.289756][3223:3228] CHIP:DMG: }, - [1646209207.289804][3223:3228] CHIP:DMG: - [1646209207.289842][3223:3228] CHIP:DMG: }, - [1646209207.289889][3223:3228] CHIP:DMG: - [1646209207.289923][3223:3228] CHIP:DMG: ], - [1646209207.289966][3223:3228] CHIP:DMG: - [1646209207.289999][3223:3228] CHIP:DMG: InteractionModelRevision = 1 - [1646209207.290032][3223:3228] CHIP:DMG: }, - [1646209207.290116][3223:3228] CHIP:DMG: Received Command Response Status for Endpoint=0 Cluster=0x0000_0032 Command=0x0000_0000 Status=0x0 - disabled: true - - - label: - "Step 3: Verify that the BDX transfer is not initiated from DUT,Verify - that DUT sends RetrieveLogsResponse command,Verify that the LogContent - field of RetrieveLogsResponse command has the DUT log entries up to < - = 1024 octets,Verify that Status field is set to Exhausted" - verification: | - ubuntu@ubuntu:~/apps$ sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 0 "test.txt" 1 0 - - [1646209207.288823][3223:3228] CHIP:DMG: InvokeResponseMessage = - [1646209207.288859][3223:3228] CHIP:DMG: { - [1646209207.288893][3223:3228] CHIP:DMG: suppressResponse = false, - [1646209207.288928][3223:3228] CHIP:DMG: InvokeResponseIBs = - [1646209207.288972][3223:3228] CHIP:DMG: [ - [1646209207.289006][3223:3228] CHIP:DMG: InvokeResponseIB = - [1646209207.289056][3223:3228] CHIP:DMG: { - [1646209207.289096][3223:3228] CHIP:DMG: CommandStatusIB = - [1646209207.289146][3223:3228] CHIP:DMG: { - [1646209207.289189][3223:3228] CHIP:DMG: CommandPathIB = - [1646209207.289237][3223:3228] CHIP:DMG: { - [1646209207.289285][3223:3228] CHIP:DMG: EndpointId = 0x0, - [1646209207.289338][3223:3228] CHIP:DMG: ClusterId = 0x32, - [1646209207.289391][3223:3228] CHIP:DMG: CommandId = 0x0, - [1646209207.289434][3223:3228] CHIP:DMG: }, - [1646209207.289479][3223:3228] CHIP:DMG: - [1646209207.289521][3223:3228] CHIP:DMG: StatusIB = - [1646209207.289573][3223:3228] CHIP:DMG: { - [1646209207.289619][3223:3228] CHIP:DMG: status = 0x0, - [1646209207.289666][3223:3228] CHIP:DMG: }, - [1646209207.289715][3223:3228] CHIP:DMG: - [1646209207.289756][3223:3228] CHIP:DMG: }, - [1646209207.289804][3223:3228] CHIP:DMG: - [1646209207.289842][3223:3228] CHIP:DMG: }, - [1646209207.289889][3223:3228] CHIP:DMG: - [1646209207.289923][3223:3228] CHIP:DMG: ], - [1646209207.289966][3223:3228] CHIP:DMG: - [1646209207.289999][3223:3228] CHIP:DMG: InteractionModelRevision = 1 - [1646209207.290032][3223:3228] CHIP:DMG: }, - [1646209207.290116][3223:3228] CHIP:DMG: Received Command Response Status for Endpoint=0 Cluster=0x0000_0032 Command=0x0000_0000 Status=0x0 - disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DLOG_3_1.yaml b/src/app/tests/suites/certification/Test_TC_DLOG_3_1.yaml deleted file mode 100644 index 0cba5b0421fa35..00000000000000 --- a/src/app/tests/suites/certification/Test_TC_DLOG_3_1.yaml +++ /dev/null @@ -1,108 +0,0 @@ -# Copyright (c) 2021 Project CHIP Authors -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# 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: 55.3.1. [TC-DLOG-3.1] Diagnostic Logs Cluster Commands Checks[DUT-Client] - -PICS: - - DLOG.C - -config: - nodeId: 0x12344321 - cluster: "Basic Information" - endpoint: 0 - -tests: - - label: "Note" - verification: | - For DUT as client test cases, Chip-tool command used below are an example to verify the functionality. For certification test, we expect DUT should have a capability or way to run the equivalent command. - disabled: true - - - label: "Precondition" - verification: | - DUT supports BDX - TH supports BDX - disabled: true - - - label: "Step 1: Commission DUT to TH" - verification: | - - disabled: true - - - label: "Step 2: DUT sends RetrieveLogsRequest Command to TH" - PICS: DLOG.C.C00.Tx - verification: | - ./chip-tool diagnosticlogs retrieve-logs-request 0 0 "test.txt" 1 0 - - - [1646215088531] [15387:2221674] CHIP: [DMG] - [1646215088531] [15387:2221674] CHIP: [DMG] StatusIB = - [1646215088531] [15387:2221674] CHIP: [DMG] { - [1646215088531] [15387:2221674] CHIP: [DMG] status = 0x0, - [1646215088531] [15387:2221674] CHIP: [DMG] }, - [1646215088531] [15387:2221674] CHIP: [DMG] - [1646215088531] [15387:2221674] CHIP: [DMG] }, - [1646215088531] [15387:2221674] CHIP: [DMG] - [1646215088531] [15387:2221674] CHIP: [DMG] }, - [1646215088531] [15387:2221674] CHIP: [DMG] - [1646215088531] [15387:2221674] CHIP: [DMG] ], - [1646215088532] [15387:2221674] CHIP: [DMG] - [1646215088532] [15387:2221674] CHIP: [DMG] InteractionModelRevision = 1 - [1646215088532] [15387:2221674] CHIP: [DMG] }, - [1646215088532] [15387:2221674] CHIP: [DMG] Received Command Response Status for Endpoint=0 Cluster=0x0000_0032 Command=0x0000_0000 Status=0x0 - disabled: true - - - label: "Step 3: In case TH initiates a BDX Transfer" - verification: | - grl_matter@GRL-Matters-MacBook-Air debug % sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 1 "test.txt" 1 0 - - - [1646208340.192138][3171:3176] CHIP:DMG: - [1646208340.192177][3171:3176] CHIP:DMG: StatusIB = - [1646208340.192224][3171:3176] CHIP:DMG: { - [1646208340.192271][3171:3176] CHIP:DMG: status = 0x0, - [1646208340.192319][3171:3176] CHIP:DMG: }, - [1646208340.192362][3171:3176] CHIP:DMG: - [1646208340.192401][3171:3176] CHIP:DMG: }, - [1646208340.192450][3171:3176] CHIP:DMG: - [1646208340.192486][3171:3176] CHIP:DMG: }, - [1646208340.192530][3171:3176] CHIP:DMG: - [1646208340.192562][3171:3176] CHIP:DMG: ], - [1646208340.192602][3171:3176] CHIP:DMG: - [1646208340.192634][3171:3176] CHIP:DMG: InteractionModelRevision = 1 - [1646208340.192665][3171:3176] CHIP:DMG: }, - [1646208340.192744][3171:3176] CHIP:DMG: Received Command Response Status for Endpoint=0 Cluster=0x0000_0032 Command=0x0000_0000 Status=0x0 - disabled: true - - - label: "Step 4: In case TH does not initiate BDX Transfer" - verification: | - ./chip-tool diagnosticlogs retrieve-logs-request 0 0 "test.txt" 1 0 - - - [1646215088531] [15387:2221674] CHIP: [DMG] - [1646215088531] [15387:2221674] CHIP: [DMG] StatusIB = - [1646215088531] [15387:2221674] CHIP: [DMG] { - [1646215088531] [15387:2221674] CHIP: [DMG] status = 0x0, - [1646215088531] [15387:2221674] CHIP: [DMG] }, - [1646215088531] [15387:2221674] CHIP: [DMG] - [1646215088531] [15387:2221674] CHIP: [DMG] }, - [1646215088531] [15387:2221674] CHIP: [DMG] - [1646215088531] [15387:2221674] CHIP: [DMG] }, - [1646215088531] [15387:2221674] CHIP: [DMG] - [1646215088531] [15387:2221674] CHIP: [DMG] ], - [1646215088532] [15387:2221674] CHIP: [DMG] - [1646215088532] [15387:2221674] CHIP: [DMG] InteractionModelRevision = 1 - [1646215088532] [15387:2221674] CHIP: [DMG] }, - [1646215088532] [15387:2221674] CHIP: [DMG] Received Command Response Status for Endpoint=0 Cluster=0x0000_0032 Command=0x0000_0000 Status=0x0 - disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_EEVSE_2_1.yaml b/src/app/tests/suites/certification/Test_TC_EEVSE_2_1.yaml index a448a969c7e44e..9079aa4a2cfa37 100644 --- a/src/app/tests/suites/certification/Test_TC_EEVSE_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_EEVSE_2_1.yaml @@ -88,7 +88,6 @@ tests: constraints: type: amperage_ma minValue: 0 - maxValue: 80000 - label: "Step 8: TH reads from the DUT the MinimumChargeCurrent attribute" PICS: EEVSE.S.A0006 @@ -98,7 +97,6 @@ tests: constraints: type: amperage_ma minValue: 0 - maxValue: 80000 - label: "Step 9: TH reads from the DUT the MaximumChargeCurrent attribute" PICS: EEVSE.S.A0007 @@ -108,7 +106,6 @@ tests: constraints: type: amperage_ma minValue: 0 - maxValue: 80000 - label: "Step 10: TH reads from the DUT the MaximumDischargeCurrent attribute" @@ -119,7 +116,6 @@ tests: constraints: type: amperage_ma minValue: 0 - maxValue: 80000 - label: "Step 11: TH writes to the DUT the UserMaximumChargeCurrent attribute diff --git a/src/app/tests/suites/certification/Test_TC_GRPKEY_2_1.yaml b/src/app/tests/suites/certification/Test_TC_GRPKEY_2_1.yaml index 7bc77c9534bbb0..218e0274f7e75c 100644 --- a/src/app/tests/suites/certification/Test_TC_GRPKEY_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_GRPKEY_2_1.yaml @@ -68,34 +68,7 @@ tests: value: [{ FabricIndex: 1, GroupId: 0x0103, GroupKeySetID: 0x01a3 }] - label: - "Step 4: TH sends KeySetWrite command in the GroupKeyManagement - cluster to DUT. GroupKeySet fields are as follows:1)GroupKeySetID: - 0x01a3 2)GroupKeySecurityPolicy: TrustFirst (0) 3)EpochKey0: - d0d1d2d3d4d5d6d7d8d9dadbdcdddedf 4)EpochStartTime0:1 5)EpochKey1: - d1d1d2d3d4d5d6d7d8d9dadbdcdddedf 6)EpochStartTime1: - 18446744073709551613 7)EpochKey2: d2d1d2d3d4d5d6d7d8d9dadbdcdddedf - 8)EpochStartTime2: 18446744073709551614" - PICS: GRPKEY.S.C00.Rsp - command: "KeySetWrite" - arguments: - values: - - name: GroupKeySet - value: - { - GroupKeySetID: 0x01a3, - GroupKeySecurityPolicy: 0, - EpochKey0: "hex:d0d1d2d3d4d5d6d7d8d9dadbdcdddedf", - EpochStartTime0: 1, - EpochKey1: "hex:d1d1d2d3d4d5d6d7d8d9dadbdcdddedf", - EpochStartTime1: "18446744073709551613", - EpochKey2: "hex:d2d1d2d3d4d5d6d7d8d9dadbdcdddedf", - EpochStartTime2: "18446744073709551614", - } - - # Step 5 does not exist in the test plan. - - - label: - "Step 6: TH reads GroupTable attribute from GroupKeyManagement cluster + "Step 4: TH reads GroupTable attribute from GroupKeyManagement cluster on DUT." PICS: GRPKEY.S.A0001 command: "readAttribute" @@ -104,47 +77,7 @@ tests: value: [] - label: - "Step 7a: TH attempts to write to the GroupTable attribute from - GroupKeyManagement cluster on DUT with one entry as follows:1)GroupId: - 0x0104 2)Endpoints: [PIXIT.G.ENDPOINT] 3)GroupName: 'Test Group2'" - PICS: GRPKEY.S.A0001 && G.S.F00 - command: "writeAttribute" - attribute: "GroupTable" - arguments: - value: - [ - { - FabricIndex: 1, - GroupId: 0x0104, - Endpoints: [Groups.Endpoint], - GroupName: "Test Group2", - }, - ] - response: - error: UNSUPPORTED_WRITE - - - label: - "Step 7b: TH attempts to write to the GroupTable attribute from - GroupKeyManagement cluster on DUT with one entry as follows:1)GroupId: - 0x0104 2)Endpoints: [PIXIT.G.ENDPOINT] 3)GroupName: '' " - PICS: GRPKEY.S.A0001 && !G.S.F00 - command: "writeAttribute" - attribute: "GroupTable" - arguments: - value: - [ - { - FabricIndex: 1, - GroupId: 0x0104, - Endpoints: [Groups.Endpoint], - GroupName: "", - }, - ] - response: - error: UNSUPPORTED_WRITE - - - label: - "Step 8: TH reads MaxGroupsPerFabric attribute from GroupKeyManagement + "Step 5: TH reads MaxGroupsPerFabric attribute from GroupKeyManagement cluster on DUT using a fabric-filtered read." PICS: GRPKEY.S.A0002 command: "readAttribute" @@ -158,18 +91,7 @@ tests: maxValue: 65535 - label: - "Step 9: TH attempts to write MaxGroupsPerFabric attribute of - GroupKeyManagement cluster to the same value as read in step 8." - PICS: GRPKEY.S.A0002 - command: "writeAttribute" - attribute: "MaxGroupsPerFabric" - arguments: - value: MaxGroupsPerFabricValue - response: - error: UNSUPPORTED_WRITE - - - label: - "Step 10: TH reads MaxGroupKeysPerFabric attribute from + "Step 6: TH reads MaxGroupKeysPerFabric attribute from GroupKeyManagement cluster on DUT using a fabric-filtered read." PICS: GRPKEY.S.A0003 command: "readAttribute" @@ -181,15 +103,3 @@ tests: type: int16u minValue: 1 maxValue: 65535 - - - label: - "Step 11: TH attempts to write MaxGroupKeysPerFabric attribute of - GroupKeyManagement cluster on DUT to the same value as read in step - 10." - PICS: GRPKEY.S.A0003 - command: "writeAttribute" - attribute: "MaxGroupKeysPerFabric" - arguments: - value: MaxGroupKeysPerFabricValue - response: - error: UNSUPPORTED_WRITE diff --git a/src/app/tests/suites/certification/Test_TC_PWRTL_1_1.yaml b/src/app/tests/suites/certification/Test_TC_PWRTL_1_1.yaml index cfe6fd860be240..da8b19b8bf7e1b 100644 --- a/src/app/tests/suites/certification/Test_TC_PWRTL_1_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_PWRTL_1_1.yaml @@ -117,3 +117,28 @@ tests: constraints: type: list contains: [0, 1] + + - label: "Step 5*: TH reads EventList attribute from DUT" + PICS: PICS_EVENT_LIST_ENABLED + command: "readAttribute" + attribute: "EventList" + response: + value: [] + constraints: + type: list + + - label: "Step 6: TH reads the AcceptedCommandList attribute from the DUT" + command: "readAttribute" + attribute: "AcceptedCommandList" + response: + value: [] + constraints: + type: list + + - label: "Step 7: TH reads the GeneratedCommandList attribute from the DUT" + command: "readAttribute" + attribute: "GeneratedCommandList" + response: + value: [] + constraints: + type: list diff --git a/src/app/tests/suites/certification/Test_TC_TMP_2_1.yaml b/src/app/tests/suites/certification/Test_TC_TMP_2_1.yaml index 7f0af0d3bb9f03..a239c77b01dd05 100644 --- a/src/app/tests/suites/certification/Test_TC_TMP_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_TMP_2_1.yaml @@ -50,7 +50,7 @@ tests: saveAs: CurrentMaxMeasured constraints: type: int16s - minValue: CurrentMinMeasured + minValue: CurrentMinMeasured+1 maxValue: 32767 - label: "Step 4: TH reads the MeasuredValue attribute from the DUT"