From 142597268ee1e4ae5af4c62610ca1ac0d44ef812 Mon Sep 17 00:00:00 2001 From: kowsisoundhar12 <57476670+kowsisoundhar12@users.noreply.github.com> Date: Thu, 18 Aug 2022 20:51:00 +0530 Subject: [PATCH] Test added aug18 (#21996) * Added Manual Scripts * Added Auto generated file * Restyled by whitespace * Restyled by clang-format * Added Manual scripts Co-authored-by: Restyled.io --- src/app/tests/suites/certification/PICS.yaml | 65 ++++++ .../suites/certification/Test_TC_ACL_2_3.yaml | 51 ++++- .../certification/Test_TC_BIND_2_1.yaml | 42 +++- .../certification/Test_TC_BIND_2_2.yaml | 59 ++++- .../certification/Test_TC_BIND_2_3.yaml | 67 ++++-- .../certification/Test_TC_BINFO_2_2.yaml | 15 +- .../certification/Test_TC_BOOL_2_2.yaml | 7 +- .../certification/Test_TC_BRBINFO_1_1.yaml | 17 +- .../certification/Test_TC_BRBINFO_2_1.yaml | 91 ++++++-- .../certification/Test_TC_CADMIN_1_1.yaml | 134 +++++++---- .../certification/Test_TC_CADMIN_1_11.yaml | 8 +- .../certification/Test_TC_CADMIN_1_12.yaml | 8 +- .../certification/Test_TC_CADMIN_1_14.yaml | 8 +- .../certification/Test_TC_CADMIN_1_15.yaml | 14 +- .../certification/Test_TC_CADMIN_1_16.yaml | 14 +- .../certification/Test_TC_CADMIN_1_17.yaml | 16 +- .../certification/Test_TC_CADMIN_1_18.yaml | 26 +-- .../certification/Test_TC_CADMIN_1_19.yaml | 2 +- .../certification/Test_TC_CADMIN_1_2.yaml | 101 ++++++++- .../certification/Test_TC_CADMIN_1_20.yaml | 2 +- .../certification/Test_TC_CADMIN_1_21.yaml | 12 +- .../certification/Test_TC_CADMIN_1_22.yaml | 43 +--- .../certification/Test_TC_CADMIN_1_7.yaml | 15 ++ .../certification/Test_TC_CADMIN_1_8.yaml | 48 +++- .../certification/Test_TC_CGEN_2_2.yaml | 3 +- .../suites/certification/Test_TC_DA_1_4.yaml | 15 +- .../suites/certification/Test_TC_DA_1_5.yaml | 38 ++-- .../suites/certification/Test_TC_DA_1_6.yaml | 11 +- .../certification/Test_TC_DGGEN_2_2.yaml | 65 ++---- .../certification/Test_TC_DGSW_3_1.yaml | 48 ++-- .../certification/Test_TC_DRLK_2_6.yaml | 19 +- .../suites/certification/Test_TC_IDM_2_2.yaml | 5 +- .../suites/certification/Test_TC_IDM_3_1.yaml | 118 +++++----- .../suites/certification/Test_TC_IDM_4_1.yaml | 68 +++++- .../suites/certification/Test_TC_MOD_2_1.yaml | 4 +- .../suites/certification/Test_TC_MOD_3_1.yaml | 2 +- .../suites/certification/Test_TC_MOD_3_3.yaml | 23 ++ .../suites/certification/Test_TC_MOD_3_4.yaml | 19 ++ .../suites/certification/Test_TC_OCC_3_2.yaml | 88 -------- .../suites/certification/Test_TC_OO_3_1.yaml | 2 +- .../suites/certification/Test_TC_PCC_3_1.yaml | 137 ++++++----- .../suites/certification/Test_TC_SC_4_1.yaml | 24 +- .../suites/certification/Test_TC_SC_4_10.yaml | 212 +----------------- .../suites/certification/Test_TC_SC_4_3.yaml | 58 +---- .../suites/certification/Test_TC_SC_4_4.yaml | 87 +++++-- .../suites/certification/Test_TC_SC_4_7.yaml | 69 +++--- .../certification/Test_TC_SWTCH_2_2.yaml | 37 ++- .../certification/Test_TC_SWTCH_3_2.yaml | 26 +-- .../tests/suites/certification/ci-pics-values | 12 + src/app/tests/suites/manualTests.json | 3 +- .../chip-tool/zap-generated/test/Commands.h | 58 ----- 51 files changed, 1178 insertions(+), 938 deletions(-) delete mode 100644 src/app/tests/suites/certification/Test_TC_OCC_3_2.yaml diff --git a/src/app/tests/suites/certification/PICS.yaml b/src/app/tests/suites/certification/PICS.yaml index 1a05e449616317..a953e5b9568b2a 100644 --- a/src/app/tests/suites/certification/PICS.yaml +++ b/src/app/tests/suites/certification/PICS.yaml @@ -5490,3 +5490,68 @@ PICS: "Is the device a Server and capable of generating large data which is greater than 1 MTU(1280 bytes)" id: MCORE.IDM.S.LargeData + + - label: + "Is the device a Client and supports writing an attribute of DataType + Bool" + id: MCORE.IDM.C.WriteRequest.Attribute.DataType_Bool + + - label: + "Is the device a Client and supports writing an attribute of DataType + String" + id: MCORE.IDM.C.WriteRequest.Attribute.DataType_String + + - label: + "Is the device a Client and supports writing an attribute of DataType + Unsigned Integer" + id: MCORE.IDM.C.WriteRequest.Attribute.DataType_UnsignedInteger + + - label: + "Is the device a Client and supports writing an attribute of DataType + Signed Integer" + id: MCORE.IDM.C.WriteRequest.Attribute.DataType_SignedInteger + + - label: + "Is the device a Client and supports writing an attribute of DataType + Struct" + id: MCORE.IDM.C.WriteRequest.Attribute.DataType_Struct + + - label: + "Is the device a Client and supports writing an attribute of DataType + Floating Point" + id: MCORE.IDM.C.WriteRequest.Attribute.DataType_FloatingPoint + + - label: + "Is the device a Client and supports writing an attribute of DataType + List" + id: MCORE.IDM.C.WriteRequest.Attribute.DataType_List + + - label: + "Is the device a Client and supports writing an attribute of DataType + Octet String" + id: MCORE.IDM.C.WriteRequest.Attribute.DataType_OctetString + + - label: + "Is the device a Client and supports writing an attribute of DataType + Enum" + id: MCORE.IDM.C.WriteRequest.Attribute.DataType_Enum + + - label: + "Is the device a Client and supports writing an attribute of DataType + Bitmap" + id: MCORE.IDM.C.WriteRequest.Attribute.DataType_Bitmap + + - label: + "Is the device a Client and supports subscribing to an attribute of + DataType Bool" + id: MCORE.IDM.C.SubscribeRequest.Attribute.DataType_Bool + + - label: + "Is the device a Client and supports subscribing to an attribute of + DataType String" + id: MCORE.IDM.C.SubscribeRequest.Attribute.DataType_String + + - label: + "Is the device a Client and supports subscribing for multiple + attribute" + id: MCORE.IDM.C.SubscribeRequest.MultipleAttributes diff --git a/src/app/tests/suites/certification/Test_TC_ACL_2_3.yaml b/src/app/tests/suites/certification/Test_TC_ACL_2_3.yaml index 57e02159a3319b..075cf0de51a9f1 100644 --- a/src/app/tests/suites/certification/Test_TC_ACL_2_3.yaml +++ b/src/app/tests/suites/certification/Test_TC_ACL_2_3.yaml @@ -24,9 +24,58 @@ config: endpoint: 0 tests: + - label: "Pre-Conditions" + verification: | + Notes + + 1.N1 is the node ID of TH1 + + 2.D_OK_EMPTY:"1718" which is an octstr of length 2 containing valid TLV: + + - top-level anonymous list (empty) + + 3.D_OK_SINGLE:"17D00000F1FF01003D48656C6C6F20576F726C642E205468697320697320612073696E676C6520656C656D656E74206C6976696E6720617320612063686172737472696E670018" which is an octstr of length 50-100 containing valid TLV: + + - top-level anonymous list, containing - one element with profile-specific tag in fully-qualified form + + 4.D_OK_FULL:"17D00000F1FF01003D48656C6C6F20576F726C642E205468697320697320612073696E676C6520656C656D656E74206C6976696E6720617320612063686172737472696E6700D00000F1FF02003148656C6C6F20576F726C642E205468697320697320612073696E676C6520656C656D656E7420616761696E2E2E2E2E2E0018" which is an octstr of length 128 containing valid TLV: + + - top-level anonymous list, containing - two elements with profile-specific tag in fully-qualified form + + 5.D_BAD_LENGTH:"17D00000F1FF01003D48656C6C6F20576F726C642E205468697320697320612073696E676C6520656C656D656E74206C6976696E6720617320612063686172737472696E6700D00000F1FF02003248656C6C6F20576F726C642E205468697320697320612073696E676C6520656C656D656E7420616761696E2E2E2E2E2E2E0018" which is an octstr of length 129 containing valid TLV: + + - top-level anonymous list, containing - one element with profile-specific tag in fully-qualified form + + 6 .D_BAD_STRUCT: "1518" which is an octstr of length 2 containing valid TLV: + + - top-level anonymous struct, empty + + 7.D_BAD_LIST:"3701D00000F1FF01003D48656C6C6F20576F726C642E205468697320697320612073696E676C6520656C656D656E74206C6976696E6720617320612063686172737472696E670018" which is an octstr of length 50-100 containing valid TLV: + + - top-level list with context-specific tag, containing - one element with profile-specific tag in fully-qualified form + + 8.D_BAD_ELEM:"17103D48656C6C6F20576F726C642E205468697320697320612073696E676C6520656C656D656E74206C6976696E6720617320612063686172737472696E670018" which is an octstr of length 50-100 containing valid TLV: + + - top-level anonymous list, containing - one element with anonymous tag + + 9 .D_BAD_OVERFLOW: "17D00000F1FF01003D48656C6C6F20576F726C642E205468697320697320612073696E676C6520656C656D656E74206C6976696E6720617320612063686172737472696E670018FF" which is an octstr of length 50-100 containing valid TLV: + + - top-level anonymous list, containing - one element with profile-specific tag in fully-qualified form - but having extra bytes after the top level list end-of-container + + 10.D_BAD_UNDERFLOW:"17D00000F1FF01003D48656C6C6F20576F726C642E205468697320697320612073696E676C6520656C656D656E74206C6976696E6720617320612063686172737472696E6700" which is an octstr of length 50-100 containing invalid TLV: + + - top-level anonymous list, containing - one element with profile-specific tag in fully-qualified form - but lacking the top-level list end-of-container + + 11.D_BAD_NONE: "" which is an octstr of length 0 + disabled: true + - label: "TH1 commissions DUT using admin node ID N1" verification: | - verification step to be updated. + DUT + sudo ./chip-all-clusters-app + + TH1 + ./chip-tool pairing ble-wifi 1 zigbee-thread matter123 20202021 3841 disabled: true - label: diff --git a/src/app/tests/suites/certification/Test_TC_BIND_2_1.yaml b/src/app/tests/suites/certification/Test_TC_BIND_2_1.yaml index 6f5ddedb6cbbef..497fdbd19eff2f 100644 --- a/src/app/tests/suites/certification/Test_TC_BIND_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_BIND_2_1.yaml @@ -24,6 +24,28 @@ config: endpoint: 0 tests: + - label: "Pre-Conditions" + verification: | + TH2 supports On/Off server on Endpoint 1. + + TH3 supports On/Off server on Endpoint 2. + + DUT supports On/Off client. + disabled: true + + - label: "Note" + verification: | + 1.Need 4 raspi for this test case and use 3 raspi as dut[all-cluster-app] and 1 raspi as chip-tool. + + 2.1st raspi which is used as DUT , which you are going to pair with onnetwork, you need to build shell command on that all clusters app.[build shell on DUT 1 Use - [scripts/examples/gn_build_example.sh examples/all-clusters-app/linux/ out/all-clusters-app chip_inet_config_enable_ipv4=false chip_build_libshell=true ] + + 3.Pair TH2 , TH3 with ble-wifi with different discriminator as mentioned below, using the chip-tool running on 4th raspi. + + 4.using chip-tool (on the 4th raspi) write the ACL entries in both TH2 and TH3 allowing to receive commands for onoff cluster from DUT + + 5.Hit Enter on raspi , you will see shell prompt (>) , enter help, you will command for switch . At the prompt enter switch on ,the on command is sent to both TH2 and TH3. you can see that in the log. to test if the TH2/TH3 are turned on or not, you can read the on-off attribute status. Read the status before sending the switch on command and read after sending the command. you should see the value changing. + disabled: true + - label: "Factory Reset DUT" verification: | Vendor specific action, for chip-tool run @@ -53,7 +75,7 @@ tests: verification: | ./chip-tool binding write binding "[{"node" : 2 , "cluster" : "0x0006" , "endpoint" : 1 }, { "node" : 3 , "cluster" : "0x0006" , "endpoint" : 2 }]" 1 1 - + On TH(Chip-tool), Verify the success response for binding entries [1657797710.456056][3796:3801] CHIP:DMG: status = 0x00 (SUCCESS), @@ -81,19 +103,26 @@ tests: verification: | ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null}, {"fabricIndex": 1, "privilege": 3, "authMode": 2, "subjects": [1], "targets": [{"cluster": 6, "endpoint": 1, "deviceType": null}]}]" 2 0 + on TH (Chip-tool), Verify the on command receives success response + [1652330385.328196][3240:3245] CHIP:DMG: StatusIB = [1652330385.328229][3240:3245] CHIP:DMG: { [1652330385.328264][3240:3245] CHIP:DMG: status = 0x00 (SUCCESS), [1652330385.328298][3240:3245] CHIP:DMG: }, - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null}, {"fabricIndex": 1, "privilege": 3, "authMode": 2, "subjects": [1], "targets": [{"cluster": 6, "endpoint": 1, "deviceType": null}]}]" 3 0 + ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null}, {"fabricIndex": 1, "privilege": 3, "authMode": 2, "subjects": [1], "targets": [{"cluster": 6, "endpoint": 2, "deviceType": null}]}]" 3 0 + + on TH(Chip-tool), Verify the on command receives success response [1650610345.847274][2626:2631] CHIP:DMG: StatusIB = [1650610345.847317][2626:2631] CHIP:DMG: { [1650610345.847383][2626:2631] CHIP:DMG: status = 0x00 (SUCCESS), [1650610345.847429][2626:2631] CHIP:DMG: }, + NOTE: + Every DUT should have their own mechanism to trigger on/off mechanism ,this for raspi platform + DUT sends on command in the shell > switch on @@ -197,11 +226,15 @@ tests: verification: | ./chip-tool onoff read on-off 2 1 + Verify on TH (Chip-tool),the onoff value is set to ON + [1657798291.396477][3835:3841] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0006 Attribute 0x0000_0000 DataVersion: 4260513117 [1657798291.396514][3835:3841] CHIP:TOO: OnOff: TRUE ./chip-tool onoff read on-off 3 2 + Verify on TH(Chip-tool) ,the onoff value is set to ON + [1657798691.194894][3869:3874] CHIP:TOO: Endpoint: 2 Cluster: 0x0000_0006 Attribute 0x0000_0000 DataVersion: 470320746 [1657798691.194948][3869:3874] CHIP:TOO: OnOff: TRUE disabled: true @@ -210,6 +243,8 @@ tests: verification: | ./chip-tool binding write binding "[{"node" : 2 , "cluster" : "0x0006" , "endpoint" : 1 }]" 1 1 + Verify on TH(Chip-tool) ,binding entry receives success response + [1657800844.739833][4000:4006] CHIP:EM: Removed CHIP MessageCounter:244702117 from RetransTable on exchange 12653i [1657800844.739867][4000:4006] CHIP:DMG: WriteClient moving to [ResponseRe] [1657800844.739922][4000:4006] CHIP:DMG: WriteResponseMessage = @@ -312,6 +347,7 @@ tests: verification: | ./chip-tool onoff read on-off 2 1 + Verify on TH (Chip-tool),the onoff value is set to OFF [1657803168.769564][4272:4277] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0006 Attribute 0x0000_0000 DataVersion: 1968648540 @@ -323,6 +359,8 @@ tests: verification: | ./chip-tool onoff read on-off 3 2 + Verify on TH(Chip-tool) ,the onoff value is set to ON + [1657803609.731464][4333:4339] CHIP:TOO: Endpoint: 2 Cluster: 0x0000_0006 Attribute 0x0000_0000 DataVersion: 3914456390 [1657803609.731521][4333:4339] CHIP:TOO: OnOff: TRUE diff --git a/src/app/tests/suites/certification/Test_TC_BIND_2_2.yaml b/src/app/tests/suites/certification/Test_TC_BIND_2_2.yaml index 370adaa9174646..a1be718287b73c 100644 --- a/src/app/tests/suites/certification/Test_TC_BIND_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_BIND_2_2.yaml @@ -26,6 +26,25 @@ config: endpoint: 0 tests: + - label: "Note" + verification: | + Chip-tool command used below are an example to verify the DUT as controller test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + disabled: true + + - label: "Pre-Conditions" + verification: | + TH2 supports On/Off server on Endpoint 1. + TH2 supports Groups server on Endpoint 1. + DUT behaves as Group Admin + TH2 should have an ACL entry with the AuthMode as Group by DUT + DUT supports On/Off client + disabled: true + + - label: "Note" + verification: | + Take 2 raspi, 1 as Lighting app and another one as chip-tool. and use [ nRF52840-DK ]Thread device as light-switch-app. + disabled: true + - label: "Factory Reset DUT" verification: | Vendor specific action, for chip-tool run @@ -34,9 +53,9 @@ tests: - label: "Commission DUT to TH1s fabric" verification: | - Run this cmmd in Thread device terminal: + Advertise the [ light-switch-app ] on [ nRF52840-DK ]Thread device and pair the TH using below cmmd. - ./chip-tool pairing ble-thread 73 hex:0e080000000000010000000300000f35060004001fffe0020810101191022022920708fd6587bfe9821353051000112237945966880899aabbccddeeff030f7070656e5468726561644465696f6c010212340410f23d85dd55d9748cc6a1fd5fccbb1da20c0402a0fff8 20202021 3840 + ./chip-tool pairing ble-thread 74 hex:0e080000000000010000000300000f35060004001fffe0020810101191022022920708fd6587bfe9821353051000112237945966880899aabbccddeeff030f7070656e5468726561644465696f6c010212340410f23d85dd55d9748cc6a1fd5fccbb1da20c0402a0fff8 20202021 3840 disabled: true - label: "TH1 enables DUT as Controller" @@ -46,7 +65,9 @@ tests: - label: "Commission TH2 to TH1s fabric (Node ID = 2)" verification: | - ./chip-tool pairing onnetwork 1 20202021 + Advertise the [Lighting-app] on Raspi and pair the TH using below cmmd. + + ./chip-tool pairing onnetwork 2 20202021 On TH(Chip-tool), Verify the success response @@ -68,6 +89,8 @@ tests: Endpoint 0." PICS: GRPKEY.C.C00.Tx verification: | + Run this cmmd for lighting app in chip-tool: + ./chip-tool groupkeymanagement key-set-write "{"groupKeySetID": 42, "groupKeySecurityPolicy": 0, "epochKey0": "d0d1d2d3d4d5d6d7d8d9dadbdcdddedf", "epochStartTime0": 2220000,"epochKey1": @@ -115,6 +138,8 @@ tests: list on GroupKeyManagement cluster to TH2 on Endpoint 0" PICS: GRPKEY.C.A0000 verification: | + Run this cmmd for lighting app in chip-tool: + ./chip-tool groupkeymanagement write group-key-map "[{"groupId": 1, "groupKeySetID": 42, "fabricIndex": 1}]" 2 0 On DUT, Verify the success response for GroupKeySetID @@ -130,6 +155,8 @@ tests: Endpoint 1." PICS: G.C.C00.Tx verification: | + Run this cmmd for lighting app in chip-tool: + ./chip-tool groups add-group 0x0001 grp1 2 1 On DUT, Verify the success response for AddGroup @@ -163,7 +190,9 @@ tests: "TH1 writes Binding entry into DUT with Entry 1: Group = The Group ID in the AddGroup command sent from DUT to TH2" verification: | - ./chip-tool binding write binding "[{"group" : "0x0001"}]" 73 1 + Run this cmmd for [ nRF52840-DK ]Thread device in chip-tool: + + ./chip-tool binding write binding "[{"group" : "0x0001"}]" 74 1 On TH, Verify the success response for binding entry @@ -179,6 +208,8 @@ tests: entries" PICS: OO.C.C01.Tx verification: | + Run this cmmd for [ nRF52840-DK ]Thread device in chip-tool: + ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null },{"fabricIndex": 1, "privilege": 4, "authMode": 3, "subjects": [1], "targets": null }]" 74 0 On TH(Chip-tool), Verify the success response for Acl: @@ -187,7 +218,9 @@ tests: [1659075680.944052][2687:2692] CHIP:DMG: { [1659075680.944116][2687:2692] CHIP:DMG: status = 0x00 (SUCCESS), - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null },{"fabricIndex": 1, "privilege": 4, "authMode": 3, "subjects": [1], "targets": null }]" 1 0 + Run this cmmd for lighting app in chip-tool: + + ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null },{"fabricIndex": 1, "privilege": 4, "authMode": 3, "subjects": [1], "targets": null }]" 2 0 On TH(Chip-tool), Verify the success response for Acl: @@ -195,13 +228,15 @@ tests: [1659075680.944052][2687:2692] CHIP:DMG: { [1659075680.944116][2687:2692] CHIP:DMG: status = 0x00 (SUCCESS), - Press button no.2 on thread board + Press button no.2 on [ nRF52840-DK ]thread board disabled: true - label: "TH1 reads OnOff attribute from TH2 (Endpoint 1)" PICS: OO.C.C01.Tx verification: | - ./chip-tool onoff read on-off 1 1 + Run this cmmd for lighting app in chip-tool: + + ./chip-tool onoff read on-off 2 1 On TH (Chip-tool), Verify the value is set to ON @@ -211,7 +246,9 @@ tests: - label: "TH1 removes all the binding entries from DUT" verification: | - ./chip-tool binding write binding "[]" 73 1 + Run this cmmd for [ nRF52840-DK ]Thread device in chip-tool: + + ./chip-tool binding write binding "[]" 74 1 On TH(Chip-tool), Verify the success response for removing binding entry @@ -226,13 +263,15 @@ tests: entries" PICS: OO.C.C00.Tx verification: | - Press button no.2 on thread board + Press button no.2 on [ nRF52840-DK ] thread board disabled: true - label: "TH1 reads OnOff attribute from TH2 (Endpoint 1)" PICS: OO.C.C01.Tx verification: | - ./chip-tool onoff read on-off 1 1 + Run this cmmd for lighting app in chip-tool: + + ./chip-tool onoff read on-off 2 1 On TH(Chip-tool), Verify the value is set to ON diff --git a/src/app/tests/suites/certification/Test_TC_BIND_2_3.yaml b/src/app/tests/suites/certification/Test_TC_BIND_2_3.yaml index 5422042e31e77c..ead8ff52038077 100644 --- a/src/app/tests/suites/certification/Test_TC_BIND_2_3.yaml +++ b/src/app/tests/suites/certification/Test_TC_BIND_2_3.yaml @@ -26,6 +26,25 @@ config: endpoint: 0 tests: + - label: "Note" + verification: | + Chip-tool command used below are an example to verify the DUT as controller test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + disabled: true + + - label: "Pre-Conditions" + verification: | + TH1 enables DUT to handle group communication + TH2 supports On/Off server on Endpoint 1 + TH2 supports Groups server on Endpoint 1 + TH2 should have an ACL entry with the AuthMode as Group by TH1 + DUT supports On/Off client + disabled: true + + - label: "Note" + verification: | + Take 2 raspi, 1 as Lighting app and another one as chip-tool. and use [ nRF52840-DK ]Thread device as light-switch-app. + disabled: true + - label: "Factory Reset DUT" verification: | Vendor specific action, for chip-tool run @@ -34,7 +53,7 @@ tests: - label: "Commission DUT to TH1s fabric" verification: | - Run this cmmd in Thread device terminal: + Advertise the [ light-switch-app ] on [ nRF52840-DK ]Thread device and pair the TH using below cmmd. ./chip-tool pairing ble-thread 74 hex:0e080000000000010000000300000f35060004001fffe0020810101191022022920708fd6587bfe9821353051000112237945966880899aabbccddeeff030f7070656e5468726561644465696f6c010212340410f23d85dd55d9748cc6a1fd5fccbb1da20c0402a0fff8 20202021 3840 disabled: true @@ -46,7 +65,9 @@ tests: - label: "Commission TH2 to TH1s fabric (Node ID = 2)" verification: | - ./chip-tool pairing onnetwork 1 20202021 + Advertise the [Lighting-app] on Raspi and pair the TH using below cmmd. + + ./chip-tool pairing onnetwork 2 20202021 On TH(Chip-tool), Verify the success response @@ -67,6 +88,9 @@ tests: "TH1 sends KeySetWrite command to GroupKeyManagement cluster to TH2 on Endpoint 0." verification: | + Run this cmmd for [ nRF52840-DK ]Thread device in chip-tool: + + ./chip-tool groupkeymanagement key-set-write "{"groupKeySetID": 42, "groupKeySecurityPolicy": 0, "epochKey0": "d0d1d2d3d4d5d6d7d8d9dadbdcdddedf", "epochStartTime0": 2220000,"epochKey1": @@ -105,13 +129,13 @@ tests: [1657719041.075988][4541:4546] CHIP:DMG: [1657719041.076012][4541:4546] CHIP:DMG: InteractionModelRevision = 1 - + Run this cmmd for lighting app in chip-tool: ./chip-tool groupkeymanagement key-set-write "{"groupKeySetID": 42, "groupKeySecurityPolicy": 0, "epochKey0": "d0d1d2d3d4d5d6d7d8d9dadbdcdddedf", "epochStartTime0": 2220000,"epochKey1": "d1d1d2d3d4d5d6d7d8d9dadbdcdddedf", "epochStartTime1": 2220001,"epochKey2": - "d2d1d2d3d4d5d6d7d8d9dadbdcdddedf", "epochStartTime2": 2220002 }" 1 0 + "d2d1d2d3d4d5d6d7d8d9dadbdcdddedf", "epochStartTime2": 2220002 }" 2 0 [1657719041.076036][4541:4546] CHIP:DMG: } On TH, Verify the success response for KeySetWrite @@ -123,6 +147,8 @@ tests: "TH1 binds GroupId with GroupKeySetID in the GroupKeyMap attribute list on GroupKeyManagement cluster to TH2 on Endpoint 0" verification: | + Run this cmmd for [ nRF52840-DK ]Thread device in chip-tool: + ./chip-tool groupkeymanagement write group-key-map "[{"groupId": 1, "groupKeySetID": 42, "fabricIndex": 1}]" 74 0 On TH(Chip-tool), Verify the success response for GroupKeySetID @@ -133,8 +159,8 @@ tests: [1657719130.464298][4557:4562] CHIP:DMG: }, [1657719130.464342][4557:4562] CHIP:DMG: - - ./chip-tool groupkeymanagement write group-key-map "[{"groupId": 1, "groupKeySetID": 42, "fabricIndex": 1}]" 1 0 + Run this cmmd for lighting app in chip-tool: + ./chip-tool groupkeymanagement write group-key-map "[{"groupId": 1, "groupKeySetID": 42, "fabricIndex": 1}]" 2 0 On TH(Chip-tool), Verify the success response for GroupKeySetID @@ -150,6 +176,8 @@ tests: "TH1 sends AddGroup( Group Name and Group-ID) Command to TH2 on Endpoint 1." verification: | + Run this cmmd for [ nRF52840-DK ]Thread device in chip-tool: + ./chip-tool groups add-group 0x0001 grp1 74 1 On TH(Chip-tool), Verify the success response for AddGroup @@ -161,8 +189,9 @@ tests: [1657719097.788418][4548:4554] CHIP:TOO: } + Run this cmmd for lighting app in chip-tool: - ./chip-tool groups add-group 0x0001 grp1 1 1 + ./chip-tool groups add-group 0x0001 grp1 2 1 On TH(Chip-tool), Verify the success response for AddGroup @@ -195,6 +224,8 @@ tests: "TH1 writes Binding entry into DUT with Entry 1: Group = The Group ID in the AddGroup command sent from TH1 to TH2" verification: | + Run this cmmd for [ nRF52840-DK ]Thread device in chip-tool: + ./chip-tool binding write binding "[{"group" : "0x0001"}]" 74 1 On TH(Chip-tool), Verify the success response for binding entry @@ -215,7 +246,9 @@ tests: entries" PICS: OO.C.C01.Tx verification: | - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null },{"fabricIndex": 1, "privilege": 4, "authMode": 3, "subjects": [1], "targets": null }]" 74 0 + Run this cmmd for [ nRF52840-DK ]Thread device in chip-tool: + + ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null },{"fabricIndex": 1, "privilege": 4, "authMode": 3, "subjects": [1], "targets": null }]" 74 0 On TH(Chip-tool), Verify the success response for Acl: @@ -223,7 +256,9 @@ tests: [1659075680.944052][2687:2692] CHIP:DMG: { [1659075680.944116][2687:2692] CHIP:DMG: status = 0x00 (SUCCESS), - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null },{"fabricIndex": 1, "privilege": 4, "authMode": 3, "subjects": [1], "targets": null }]" 1 0 + Run this cmmd for lighting app in chip-tool: + + ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null },{"fabricIndex": 1, "privilege": 4, "authMode": 3, "subjects": [1], "targets": null }]" 2 0 On TH(Chip-tool), Verify the success response for Acl: @@ -231,13 +266,15 @@ tests: [1659075680.944052][2687:2692] CHIP:DMG: { [1659075680.944116][2687:2692] CHIP:DMG: status = 0x00 (SUCCESS), - Press button no.2 on thread board + Press button no.2 on nrf52840 DK thread board disabled: true - label: "TH1 reads OnOff attribute from TH2 (Endpoint 1)" PICS: OO.C.C01.Tx verification: | - ./chip-tool onoff read on-off 1 1 + Run this cmmd for lighting app in chip-tool: + + ./chip-tool onoff read on-off 2 1 On TH(Chip-tool), Verify the onoff value is set to ON @@ -247,6 +284,8 @@ tests: - label: "TH1 removes all the binding entries from DUT" verification: | + Run this cmmd for [ nRF52840-DK ]Thread device in chip-tool: + ./chip-tool binding write binding "[]" 74 1 On TH(Chip-tool), Verify the success response for removing binding entry @@ -262,13 +301,15 @@ tests: entries" PICS: OO.C.C00.Tx verification: | - Press button no.2 on thread board + Press button no.2 on nrf52840 DK thread board disabled: true - label: "TH1 reads OnOff attribute from TH2 (Endpoint 1)" PICS: OO.C.C01.Tx verification: | - ./chip-tool onoff read on-off 1 1 + Run this cmmd for lighting app in chip-tool: + + ./chip-tool onoff read on-off 2 1 On TH(Chip-tool), Verify the onoff value is set to ON diff --git a/src/app/tests/suites/certification/Test_TC_BINFO_2_2.yaml b/src/app/tests/suites/certification/Test_TC_BINFO_2_2.yaml index 0ad5188ed749a4..e41fe1c356098f 100644 --- a/src/app/tests/suites/certification/Test_TC_BINFO_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_BINFO_2_2.yaml @@ -24,6 +24,19 @@ config: endpoint: 0 tests: + - label: "Precondition" + verification: | + 1. DUT and TH can interact with each other. DUT is commissioned. + + 2. BINFO.S.A0009(SoftwareVersion) - TH reads SoftwareVersion attribute from DUT and saves for future use + + 3. BINFO.S.A0011(Reachable) - TH reads Reachable attribute from DUT and saves for future use(should be true) + + 4. BINFO.S.E00(StartUp) && BINFO.S.E01(ShutDown) && BINFO.S.E02(Leave) - TH subscribes to StartUp, ShutDown, Leave and ReachableChanged events on the Basic Information cluster of the DUT + + 5. TH saves the FabricIndex during commissioning + disabled: true + - label: "Reboot the DUT TH reads the StartUp event from DUT" PICS: BINFO.S.E00 verification: | @@ -63,7 +76,7 @@ tests: 2. run below command in interactive mode shell and Turn down the DUT - verify that ShutDown event as priority set has CRITICAL on TH(chip-tool) + verify that ShutDown event as priority set has CRITICAL on TH(Chip-tool) CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Event 0x0000_0001 [1653050528.900202][119367:119372] CHIP:TOO: Event number: 5 diff --git a/src/app/tests/suites/certification/Test_TC_BOOL_2_2.yaml b/src/app/tests/suites/certification/Test_TC_BOOL_2_2.yaml index a9958cd5eed5cb..72b45884c4f604 100644 --- a/src/app/tests/suites/certification/Test_TC_BOOL_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_BOOL_2_2.yaml @@ -24,9 +24,14 @@ config: endpoint: 0 tests: + - label: "Pre-Conditions" + verification: | + This test case is verified after the device is provisioned. Pls provision device first, Pass appropriate nodeID in the below command + disabled: true + - label: "Commission DUT to TH" verification: | - verification step to be updated. + disabled: true - label: "Bring the DUT into a state so StateValue is FALSE" 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 index 3e19e783a71e9b..f4eebc4d1089df 100644 --- a/src/app/tests/suites/certification/Test_TC_BRBINFO_1_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_BRBINFO_1_1.yaml @@ -23,9 +23,24 @@ config: endpoint: 0 tests: + - label: "" + verification: | + Validate these PICS items of attributes which are not allowed in this server cluster implementation - these PICS items should all be FALSE, if any of them is TRUE then FAIL the test + + BRBINFO.S.A0000(DataModelRevision) + + BRBINFO.S.A0004(ProductID) + + BRBINFO.S.A0006(Location) + + BRBINFO.S.A0010(LocalConfigDisabled) + + BRBINFO.S.A0013(CapabilityMinima) + disabled: true + - label: "Commission DUT to TH (if not already done)" verification: | - verification step to be updated. + disabled: true - label: "TH reads the ClusterRevision from DUT" 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 index 8ec428966a1037..9f1e1b56fea93e 100644 --- a/src/app/tests/suites/certification/Test_TC_BRBINFO_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_BRBINFO_2_1.yaml @@ -26,8 +26,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read vendor-name 1 3 - Verify VendorName is of type string and is less than or equal to 32 bytes on TH(chip-tool) Log: + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656495199.434300][2158:2163] CHIP:TOO: VendorName: TEST_VENDOR disabled: true @@ -46,8 +47,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read vendor-name 1 3 - Verify VendorName is not chnged when compared to step 1 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656495199.434300][2158:2163] CHIP:TOO: VendorName: TEST_VENDOR disabled: true @@ -56,8 +58,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read vendor-id 1 3 - Veify VendorID value is in range of 0x0001 to 0xFFF0 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656495322.252171][2177:2182] CHIP:TOO: VendorID: 65521 disabled: true @@ -76,8 +79,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read vendor-id 1 3 - Verify VendorID is not chnged when compared to step 8 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656495322.252171][2177:2182] CHIP:TOO: VendorID: 65521 disabled: true @@ -86,8 +90,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read product-name 1 3 - Verify ProductName has human readable string and is less or equal to 32 bytes on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656495708.412745][2200:2205] CHIP:TOO: ProductName: TEST_PRODUCT disabled: true @@ -107,8 +112,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read product-name 1 3 - Verify ProductName is not chnged when compared to step 11 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656495708.412745][2200:2205] CHIP:TOO: ProductName: TEST_PRODUCT disabled: true @@ -117,8 +123,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read node-label 1 3 - Verify the value of node-label is type of string and contains length between 0 and 32 in TH(chip-tool) Log: + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1657696463.081741][15476:15481] CHIP:TOO: Endpoint: 3 Cluster: 0x0000_0039 Attribute 0x0000_0005 DataVersion: 2577979325 [1657696463.081791][15476:15481] CHIP:TOO: NodeLabel: Light 1 disabled: true @@ -159,8 +166,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read hardware-version 1 3 - Verify HardwareVersion is in range of 0 to 65534 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656496175.564718][2302:2307] CHIP:TOO: HardwareVersion: 0 disabled: true @@ -179,8 +187,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read hardware-version 1 3 - Verify HardwareVersion is not chnged when compared to step 21 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656496175.564718][2302:2307] CHIP:TOO: HardwareVersion: 0 disabled: true @@ -189,8 +198,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read hardware-version-string 1 3 - Verify HardwareVersionString value is type of string and in range of 1 to 64 bytes + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656496257.298675][2315:2320] CHIP:TOO: HardwareVersionString: TEST_VERSION disabled: true @@ -209,8 +219,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read hardware-version-string 1 3 - Verify HardwareVersionString is not chnged when compared to step 24 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656496257.298675][2315:2320] CHIP:TOO: HardwareVersionString: TEST_VERSION disabled: true @@ -219,8 +230,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read software-version 1 3 - Verify SoftwareVersion value is in range of 0 to 4294967294 on TH(chip-tol) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656496411.609866][2348:2353] CHIP:TOO: SoftwareVersion: 1 disabled: true @@ -239,8 +251,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read software-version 1 3 - Verify SoftwareVersion is not chnged when compared to step 27 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656496411.609866][2348:2353] CHIP:TOO: SoftwareVersion: 1 disabled: true @@ -249,8 +262,9 @@ 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 + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656496498.568951][2362:2367] CHIP:TOO: SoftwareVersionString: 1.0 disabled: true @@ -270,8 +284,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read software-version-string 1 3 - Verify SoftwareVersionString is not chnged when compared to step 1 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656496498.568951][2362:2367] CHIP:TOO: SoftwareVersionString: 1.0 disabled: true @@ -280,8 +295,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read manufacturing-date 1 3 - Verify manufacturing date is of type string and has length of range 8 to 16 bytes on TH() + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656496661.777852][2388:2393] CHIP:TOO: ManufacturingDate: 20200101 disabled: true @@ -300,8 +316,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read manufacturing-date 1 3 - Verify VendorName is not chnged when compared to step 1 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656496661.777852][2388:2393] CHIP:TOO: ManufacturingDate: 20200101 disabled: true @@ -310,6 +327,10 @@ tests: verification: | ./chip-tool bridgeddevicebasic read part-number 1 3 + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + + Example Log: + [1656496800.941788][2405:2410] CHIP:TOO: PartNumber: 1234 disabled: true @@ -328,8 +349,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read part-number 1 3 - Verify VendorName is not chnged when compared to step 1 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656496800.941788][2405:2410] CHIP:TOO: PartNumber: 1234 disabled: true @@ -338,6 +360,10 @@ tests: verification: | ./chip-tool bridgeddevicebasic read product-url 1 3 + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + + Example Log: + [1656497181.118653][2436:2441] CHIP:TOO: ProductURL: https://example.com/myproduct disabled: true @@ -356,8 +382,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read product-url 1 3 - Verify VendorName is not chnged when compared to step 1 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656497181.118653][2436:2441] CHIP:TOO: ProductURL: https://example.com/myproduct disabled: true @@ -366,6 +393,10 @@ tests: verification: | ./chip-tool bridgeddevicebasic read product-label 1 3 + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + + Example Log: + [1656501313.811305][2602:2607] CHIP:TOO: ProductLabel: ABCD disabled: true @@ -374,8 +405,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic write product-label newproductlabel 1 3 - Verify response has unsupported write on TH(chip-tool) Log: + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656495259.991989][2164:2169] CHIP:TOO: Response Failure: IM Error 0x00000588: General error: 0x88 (UNSUPPORTED_WRITE) disabled: true @@ -384,8 +416,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read product-label 1 3 - Verify VendorName is not chnged when compared to step 1 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656501313.811305][2602:2607] CHIP:TOO: ProductLabel: ABCD disabled: true @@ -394,6 +427,10 @@ tests: verification: | ./chip-tool bridgeddevicebasic read serial-number 1 3 + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + + Example Log: + [1656501452.183890][2624:2630] CHIP:TOO: SerialNumber: 5678 disabled: true @@ -412,8 +449,9 @@ tests: verification: | ./chip-tool bridgeddevicebasic read serial-number 1 3 - Verify VendorName is not chnged when compared to step 1 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656501452.183890][2624:2630] CHIP:TOO: SerialNumber: 5678 disabled: true @@ -436,7 +474,7 @@ tests: verification: | ./chip-tool bridgeddevicebasic write-by-id 0x0005 ‘“false”’ 1 0 - Verify response has unsupported write on TH(chip-tool) Log: + On TH verify that, TH receives UNSUPPORTED_WRITE response as status [1656496372.884955][2340:2345] CHIP:DMG: } @@ -461,6 +499,10 @@ tests: verification: | ./chip-tool bridgeddevicebasic read unique-id 1 3 + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + + Example Log: + [1656501734.253827][2673:2679] CHIP:TOO: UniqueID: 30789FE4FCF832C9 disabled: true @@ -479,7 +521,8 @@ tests: verification: | ./chip-tool bridgeddevicebasic read unique-id 1 3 - Verify VendorName is not chnged when compared to step 1 on TH(chip-tool) Log + Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE + Example Log: [1656501734.253827][2673:2679] CHIP:TOO: UniqueID: 30789FE4FCF832C9 disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_1.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_1.yaml index b2b7678d366c50..571518d23f43b7 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_1.yaml @@ -51,9 +51,11 @@ tests: verification: | On 1st controller using chip tool, open commissioning window using ECM + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool pairing open-commissioning-window 1 1 400 2000 3841 - On TH1(chip-tool) Log + Verify Manual pairing code On TH1(all-clusters-app) Log CHIP:IN: Sending encrypted msg 0xaaaad3464d10 with MessageCounter:0 to 0x0000000000000001 at monotonic time: 5805157 msec [1635691999.946536][3822:3827] CHIP:DMG: ICR moving to [CommandSen] @@ -81,8 +83,11 @@ tests: verification: | On 1st controller using chip tool read fabricList + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool operationalcredentials read fabrics 1 0 --fabric-filtered 0 + Verify 1 entry in the Fabrics list attributeOn TH1(all-clusters-app) Log CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0001 DataVersion: 3621507058 [1649245801.244173][10091:10096] CHIP:TOO: Fabrics: 1 entries @@ -102,11 +107,12 @@ tests: verification: | On 2nd controller, using chip-tool connect using manual code. - On Raspi platform use commissioner-name parameter to commission different TH as server with DUT as commissioner, Pls use equivalent command on the respective TH as server + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + Below is the example when using chip tool as controller (considering 35998938564 as the manual code generated by 1st controller) ./chip-tool pairing code 2 35998938564 --commissioner-name beta - Verify whether you got below message in the log of TH + Verify whether you got below message in the log of TH2 (all-clusters-app) Device commissioning completed with success disabled: true @@ -115,6 +121,8 @@ tests: verification: | On the raspi , Verify if the DUT is broadcasting using + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ubuntu@ubuntu:~/may10_cntrl2/connectedhomeip/examples/chip-tool/out/debug$ avahi-browse -rt _matter._tcp + eth0 IPv6 E0AF53B23E580769-0000000000000002 _matter._tcp local + eth0 IPv6 7FF84D214A19B581-0000000000000001 _matter._tcp local @@ -137,10 +145,12 @@ tests: verification: | On 2nd controller using chip tool write and read node-label - On Raspi platform use commissioner-name parameter to commission different TH as server with DUT as commissioner, Pls use equivalent command on the respective TH as server - Below is the example when using chip tool as controller + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool basic write node-label te5new 2 0 --commissioner-name beta + Verify success response On TH2(all-clusters-app) Log + CHIP:DMG: WriteClient moving to [ResponseRe] [1649671460.431199][20958:20963] CHIP:DMG: WriteResponseMessage = [1649671460.431217][20958:20963] CHIP:DMG: { @@ -171,39 +181,16 @@ tests: - Verify read attribute returns the updated value written + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + - On Raspi platform use commissioner-name parameter to commission different TH as server with DUT as commissioner, Pls use equivalent command on the respective TH as server ./chip-tool basic read node-label 2 0 --commissioner-name beta - CHIP:DMG: ReportDataMessage = - [1649671466.310233][20969:20974] CHIP:DMG: { - [1649671466.310241][20969:20974] CHIP:DMG: AttributeReportIBs = - [1649671466.310256][20969:20974] CHIP:DMG: [ - [1649671466.310265][20969:20974] CHIP:DMG: AttributeReportIB = - [1649671466.310281][20969:20974] CHIP:DMG: { - [1649671466.310292][20969:20974] CHIP:DMG: AttributeDataIB = - [1649671466.310304][20969:20974] CHIP:DMG: { - [1649671466.310317][20969:20974] CHIP:DMG: DataVersion = 0xd581a5e8, - [1649671466.310328][20969:20974] CHIP:DMG: AttributePathIB = - [1649671466.310342][20969:20974] CHIP:DMG: { - [1649671466.310355][20969:20974] CHIP:DMG: Endpoint = 0x0, - [1649671466.310367][20969:20974] CHIP:DMG: Cluster = 0x28, - [1649671466.310380][20969:20974] CHIP:DMG: Attribute = 0x0000_0005, - [1649671466.310391][20969:20974] CHIP:DMG: } - [1649671466.310405][20969:20974] CHIP:DMG: - [1649671466.310420][20969:20974] CHIP:DMG: Data = "te8", - [1649671466.310432][20969:20974] CHIP:DMG: }, - [1649671466.310446][20969:20974] CHIP:DMG: - [1649671466.310457][20969:20974] CHIP:DMG: }, - [1649671466.310471][20969:20974] CHIP:DMG: - [1649671466.310481][20969:20974] CHIP:DMG: ], - [1649671466.310497][20969:20974] CHIP:DMG: - [1649671466.310508][20969:20974] CHIP:DMG: SuppressResponse = true, - [1649671466.310518][20969:20974] CHIP:DMG: InteractionModelRevision = 1 - [1649671466.310528][20969:20974] CHIP:DMG: } + Verify read attribute returns the updated value written On TH2(all-clusters-app) Log + + [1649671466.310629][20969:20974] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0005 DataVersion: 3582043624 - [1649671466.310646][20969:20974] CHIP:TOO: NodeLabel: te8 + [1649671466.310646][20969:20974] CHIP:TOO: NodeLabel: te5new [1649671466.310704][20969:20974] CHIP:EM: Sending Standalone Ack for MessageCounter:15357338 on exchange 20724i disabled: true @@ -212,12 +199,12 @@ tests: verification: | On 2nd controller using chip tool read fabricList + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. - Below is the example using chip tool as controller ./chip-tool operationalcredentials read fabrics 2 0 --fabric-filtered 0 --commissioner-name beta - + Verify 2 entries in the Fabrics list attribute On TH2(all-clusters-app) Log CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0001 DataVersion: 3621507063 [1649245825.315152][10098:10103] CHIP:TOO: Fabrics: 2 entries @@ -246,8 +233,14 @@ tests: verification: | On first controller using chip tool, write attribute and read attribute + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool basic write node-label te8 1 0 + Verify success response On TH1(all-clusters-app) Log + + CHIP:DMG: WriteResponse = CHIP:DMG: WriteResponseMessage = [1649245940.788522][10110:10115] CHIP:DMG: { @@ -276,9 +269,12 @@ tests: [1649245940.790167][10110:10115] CHIP:DMG: WriteClient moving to [AwaitingDe] - Verify read attribute returns the updated value written + ./chip-tool basic read node-label 1 0 + Verify read attribute returns the updated value written On TH1(all-clusters-app) Log + + CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0005 DataVersion: 3061847068 [1649245950.006849][10116:10121] CHIP:TOO: NodeLabel: te8 [1649245950.007024][10116:10121] CHIP:EM: Sending Standalone Ack for MessageCounter:12495101 on exchange 24816i @@ -291,10 +287,14 @@ tests: verification: | On 2nd controller using chip-tool read, write attribute and then read attribute to and from TH_CE - Below is an example of using chip tool as controller + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool basic write node-label te5new 2 0 --commissioner-name beta + On TH2(all-clusters-app) Log + + CHIP:DMG: WriteResponseMessage = [1649245940.788522][10110:10115] CHIP:DMG: { [1649245940.788577][10110:10115] CHIP:DMG: AttributeStatusIBs = @@ -325,6 +325,9 @@ tests: ./chip-tool basic read node-label 2 0 --commissioner-name beta + Verify read attribute returns the updated value written On TH1(all-clusters-app) Log + + CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0005 DataVersion: 3061847068 [1649245950.006849][10116:10121] CHIP:TOO: NodeLabel: te5new [1649245950.007024][10116:10121] CHIP:EM: Sending Standalone Ack for MessageCounter:12495101 on exchange 24816i @@ -343,9 +346,13 @@ tests: verification: | On 2nd controller open commissioning window using ECM - Below is an example when using chip tool as controller + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool pairing open-commissionig-window 2 1 300 1000 3841 --commissioner-name beta + Verify Manual pairing code On TH2(all-clusters-app) Log + CHIP: [IN] Prepared encrypted message 0x124012e80 to 0x0000000000000001 of type 0x8 and protocolId (0, 1) on exchange 50829i with MessageCounter:0. [1635693418549] [30519:4583024] CHIP: [IN] Sending encrypted msg 0x124012e80 with MessageCounter:0 to 0x0000000000000001 at monotonic time: 5995099243 msec [1635693418549] [30519:4583024] CHIP: [DMG] ICR moving to [CommandSen] @@ -363,10 +370,13 @@ tests: verification: | On 2nd controller, run revoke command - Below is an example when using chip tool as controller + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. ./chip-tool administratorcommissioning revoke-commissioning 2 0 --timedInteractionTimeoutMs 1000 --commissioner-name beta + Verify success response On TH2(all-clusters-app) Log + + CHIP: [DMG] InvokeResponseMessage = [1648115245106] [6681:3894448] CHIP: [DMG] { @@ -407,9 +417,11 @@ tests: verification: | On 3rd controller using chip-tool connect using manual code generated from 1st controller. This attempt should fail, i.e + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool pairing code 3 34995354639 --commissioner-name gamma - verify you got the following message in the TH log + verify you got the following message in the TH 3(all-clusters-app) log CHIP:SC: PASESession timed out while waiting for a response from the peer. Expected message type was 33 CHIP:TOO: Secure Pairing Failed @@ -423,10 +435,13 @@ tests: verification: | On 2nd controller , write attribute and read attribute to and from TH_CE - Below is the example using chip tool as controller + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool basic write node-label te5new 2 0 --commissioner-name beta + Verify success response On TH1(all-clusters-app) Log + CHIP:DMG: WriteResponseMessage = [1649245940.788522][10110:10115] CHIP:DMG: { [1649245940.788577][10110:10115] CHIP:DMG: AttributeStatusIBs = @@ -453,10 +468,12 @@ tests: [1649245940.790033][10110:10115] CHIP:DMG: } [1649245940.790167][10110:10115] CHIP:DMG: WriteClient moving to [AwaitingDe] - Verify read attribute returns the updated value written + ./chip-tool basic read node-label 2 0 --commissioner-name beta + Verify read attribute returns the updated value written On TH1(all-clusters-app) Log + CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0005 DataVersion: 3061847068 [1649245950.006849][10116:10121] CHIP:TOO: NodeLabel: te5new @@ -470,9 +487,14 @@ tests: verification: | On 2nd controller open commissioning window using ECM - Below is an example when using chip tool as controller + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool pairing open-commissioning-window 2 1 180 1000 3840 --commissioner-name beta + Verify Manual pairing code On TH2(all-clusters-app) Log + + CHIP: [IN] Prepared encrypted message 0x124012e80 to 0x0000000000000001 of type 0x8 and protocolId (0, 1) on exchange 50829i with MessageCounter:0. [1635693418549] [30519:4583024] CHIP: [IN] Sending encrypted msg 0x124012e80 with MessageCounter:0 to 0x0000000000000001 at monotonic time: 5995099243 msec [1635693418549] [30519:4583024] CHIP: [DMG] ICR moving to [CommandSen] @@ -496,9 +518,14 @@ tests: verification: | On 2nd controller open commissioning window using ECM - Below is an example when using chip tool as controller + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool pairing open-commissionig-window 2 1 300 1000 3840 --commissioner-name beta + Verify Manual pairing code On TH2(all-clusters-app) Log + + CHIP: [IN] Prepared encrypted message 0x124012e80 to 0x0000000000000001 of type 0x8 and protocolId (0, 1) on exchange 50829i with MessageCounter:0. [1635693418549] [30519:4583024] CHIP: [IN] Sending encrypted msg 0x124012e80 with MessageCounter:0 to 0x0000000000000001 at monotonic time: 5995099243 msec [1635693418549] [30519:4583024] CHIP: [DMG] ICR moving to [CommandSen] @@ -516,9 +543,14 @@ tests: verification: | On 1st controller, using chip-tool connect using manual code. - Below is the example when using chip tool as controller (considering 34995354639 as the manual code generated by DUT) + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + (considering 34995354639 as the manual code generated by DUT) ./chip-tool pairing code 2 34995354639 + Trying to add a NOC for a fabric that already exists On TH1(all-clusters-app) Log + + [1651786200275] [36301:315544] CHIP: [DMG] Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0008 [1651786200275] [36301:315544] CHIP: [CTL] Device returned status 9 on receiving the NOC [1651786200275] [36301:315544] CHIP: [CTL] Add NOC failed with error ../../src/controller/CHIPDeviceController.cpp:1187: CHIP Error 0x0000007E: Trying to add a NOC for a fabric that already exists @@ -526,3 +558,13 @@ tests: Verify that the commissioning process fails as TH_CE was already commissioned by TH_CR1 in step 1 disabled: true + + - label: "" + verification: | + verification step to be updated. + disabled: true + + - label: "" + verification: | + verification step to be updated. + disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_11.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_11.yaml index 54083688e066b7..e13c93fc9faf4a 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_11.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_11.yaml @@ -84,7 +84,7 @@ tests: verification: | On 3rd controller using chip tool connect using manual code - ./chip-tool pairing code 3 35484132896 + ./chip-tool pairing code 3 35484132896 --commissioner-name gamma Verify you got below message Device commissioning completed with success @@ -115,7 +115,7 @@ tests: On 2nd controller using chip tool connect using manual code - ./chip-tool pairing code 1 35484132896 + ./chip-tool pairing code 1 35484132896 --commissioner-name beta Verify you got below message Device commissioning completed with success @@ -292,7 +292,7 @@ tests: verification: | On the 3rd controller using chip tool, open commissioning window using BCM before the timer expiry of the above step - ./chip-tool administratorcommissioning open-basic-commissioning-window 500 3 0 --timedInteractionTimeoutMs 1000 + ./chip-tool administratorcommissioning open-basic-commissioning-window 500 3 0 --timedInteractionTimeoutMs 1000 --commissioner-name gamma CHIP:DMG: InvokeResponseMessage = [1650527565.990404][24618:24623] CHIP:DMG: { @@ -422,7 +422,7 @@ tests: verification: | On 2nd controller using chip tool, open commissioning window using BCM before timer expiry from above step - ./chip-tool administratorcommissioning open-basic-commissioning-window 500 2 0 --timedInteractionTimeoutMs 1000 + ./chip-tool administratorcommissioning open-basic-commissioning-window 500 2 0 --timedInteractionTimeoutMs 1000 --commissioner-name beta CHIP:DMG: InvokeResponseMessage = [1650527622.373450][15824:15829] CHIP:DMG: { diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_12.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_12.yaml index c08854525cad67..c736e2199f821e 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_12.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_12.yaml @@ -71,7 +71,7 @@ tests: On 3rd controller using chip tool connect using manual code - ./chip-tool pairing code 1 35484132896 + ./chip-tool pairing code 1 35484132896 --commissioner-name gamma Verify you got below message Device commissioning completed with success @@ -103,7 +103,7 @@ tests: On 2nd controller using chip tool connect using manual code - ./chip-tool pairing code 1 35484132896 + ./chip-tool pairing code 2 35484132896 --commissioner-name beta Verify you got below message Device commissioning completed with success @@ -321,7 +321,7 @@ tests: verification: | On third controller open commissioning window verify status code 1 - ./chip-tool administratorcommissioning open-basic-commissioning-window 500 3 0 --timedInteractionTimeoutMs 1000 + ./chip-tool administratorcommissioning open-basic-commissioning-window 500 3 0 --timedInteractionTimeoutMs 1000 --commissioner-name gamma [1658838344.191922][9291:9296] CHIP:DMG: InvokeResponseMessage = [1658838344.191947][9291:9296] CHIP:DMG: { @@ -416,7 +416,7 @@ tests: verification: | On the 2nd controller using chip tool, open commissioning window using BCM before the timer expiry from above step - ./chip-tool administratorcommissioning open-basic-commissioning-window 500 2 0 --timedInteractionTimeoutMs 1000 + ./chip-tool administratorcommissioning open-basic-commissioning-window 500 2 0 --timedInteractionTimeoutMs 1000 --commissioner-name beta diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_14.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_14.yaml index 7622ff87597173..532bdb8ff32e11 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_14.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_14.yaml @@ -90,7 +90,7 @@ tests: On 3rd controller, using chip tool connect to the accessory - ./chip-tool pairing onnetwork 1 20202021 + ./chip-tool pairing onnetwork 1 20202021 --commissioner-name gamma Verify you got below message Device commissioning completed with success @@ -141,7 +141,7 @@ tests: On 2nd controller, using chip tool connect to the accessory - ./chip-tool pairing onnetwork 1 20202021 + ./chip-tool pairing onnetwork 1 20202021 --commissioner-name beta Verify you got below message Device commissioning completed with success @@ -264,7 +264,7 @@ tests: verification: | On 3rd controller chip tool, open commissioning window using ECM - ./chip-tool pairing open-commissioning-window 1 1 180 1000 3840 + ./chip-tool pairing open-commissioning-window 3 1 180 1000 3840 --commissioner-name gamma [1635925713.966786][9695:9700] CHIP:SC: Success status report received. Session was established [1635925713.966839][9695:9700] CHIP:IN: New secure session created for device 0x0000000000000001, key 33!! @@ -318,7 +318,7 @@ tests: On 2nd controller using chip tool connect to the accessory using ECM - ./chip-tool pairing open-commissioning-window 1 1 180 1000 3840 + ./chip-tool pairing open-commissioning-window 1 1 180 1000 3840 --commissioner-name beta disabled: true - label: diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_15.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_15.yaml index e8b060d2034eb3..f35cffd5ed79ca 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_15.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_15.yaml @@ -66,7 +66,7 @@ tests: On 2nd controller using chip tool connect to the accessory - ./chip-tool pairing code 2 36217551633 + ./chip-tool pairing code 2 36217551633 --commissioner-name beta Verify you got below message Device commissioning completed with success @@ -101,7 +101,7 @@ tests: - ./chip-tool pairing code 3 36217551633 + ./chip-tool pairing code 3 36217551633 --commissioner-name gamma Verify you got below message Device commissioning completed with success @@ -112,7 +112,7 @@ tests: verification: | On 2nd controller using chip tool, read fabrics list - ./chip-tool operationalcredentials read fabrics 2 0 --fabric-filtered 0 + ./chip-tool operationalcredentials read fabrics 2 0 --fabric-filtered 0 --commissioner-name beta CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0001 DataVersion: 2455995193 CHIP:TOO: Fabrics: 3 entries @@ -148,7 +148,7 @@ tests: verification: | on 2nd controller using chip tool, remove fabric with FabricIndex=2 - ./chip-tool operationalcredentials remove-fabric 2 2 0 + ./chip-tool operationalcredentials remove-fabric 2 2 0 --commissioner-name beta CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0008 CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Command 0x0000_0008 @@ -167,13 +167,13 @@ tests: Using your 2nd controller, write attribute and read attribute Below is the example while using chip tool on second controller, - ./chip-tool basic write node-label te5new 2 0 + ./chip-tool basic write node-label te5new 2 0 --commissioner-name beta Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2 [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53 - ./chip-tool basic read node-label 2 0 + ./chip-tool basic read node-label 2 0 --commissioner-name beta Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2 @@ -258,7 +258,7 @@ tests: On 2nd controller using chip tool connect to the accessory - ./chip-tool pairing code 2 36217551633 + ./chip-tool pairing code 2 36217551633 --commissioner-name beta Verify you got below message Device commissioning completed with success diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_16.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_16.yaml index 8d80ea0b08a370..28492fc2debf5d 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_16.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_16.yaml @@ -86,7 +86,7 @@ tests: On 2nd controller using chip tool connect to the accessory - ./chip-tool pairing onnetwork 2 20202021 + ./chip-tool pairing onnetwork 2 20202021 --commissioner-name beta Verify you got below message Device commissioning completed with success @@ -140,7 +140,7 @@ tests: - ./chip-tool pairing onnetwork 3 20202021 + ./chip-tool pairing onnetwork 3 20202021 --commissioner-name gamma Verify you got below message Device commissioning completed with success @@ -151,7 +151,7 @@ tests: verification: | On 2nd controller using chip tool, read fabrics list - ./chip-tool operationalcredentials read fabrics 2 0 --fabric-filtered 0 + ./chip-tool operationalcredentials read fabrics 2 0 --fabric-filtered 0 --commissioner-name beta CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0001 DataVersion: 2455995193 CHIP:TOO: Fabrics: 3 entries @@ -187,7 +187,7 @@ tests: verification: | on 2nd controller using chip tool, remove fabric with FabricIndex=2 - ./chip-tool operationalcredentials remove-fabric 2 2 0 + ./chip-tool operationalcredentials remove-fabric 2 2 0 --commissioner-name beta CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0008 CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Command 0x0000_0008 @@ -206,13 +206,13 @@ tests: Using your 2nd controller, write attribute and read attribute Below is the example while using chip tool on second controller, - ./chip-tool basic write node-label te5new 2 0 + ./chip-tool basic write node-label te5new 2 0 --commissioner-name beta Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2 [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53 - ./chip-tool basic read node-label 2 0 + ./chip-tool basic read node-label 2 0 --commissioner-name beta Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2 @@ -319,7 +319,7 @@ tests: On 2nd controller using chip tool connect to the accessory - ./chip-tool pairing onnetwork 2 20202021 + ./chip-tool pairing onnetwork 2 20202021 --commissioner-name beta Verify you got below message Device commissioning completed with success diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_17.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_17.yaml index 6ca89bc6035b65..a6d2ae56fa9342 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_17.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_17.yaml @@ -89,7 +89,7 @@ tests: On 2nd controller using chip tool connect to the accessory - ./chip-tool pairing code 1 35484132896 + ./chip-tool pairing code 1 35484132896 --commissioner-name beta Verify you got below message Device commissioning completed with success @@ -140,7 +140,7 @@ tests: On 3rd controller using chip tool connect to the accessory - ./chip-tool pairing code 1 35484132896 + ./chip-tool pairing code 1 35484132896 --commissioner-name gamma Verify you got below message Device commissioning completed with success @@ -151,7 +151,7 @@ tests: verification: | On 2nd controller using chip tool, read fabrics list - ./chip-tool operationalcredentials read fabrics 1234 0 --fabric-filtered 0 + ./chip-tool operationalcredentials read fabrics 1234 0 --fabric-filtered 0 --commissioner-name beta CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0001 DataVersion: 2455995193 CHIP:TOO: Fabrics: 3 entries @@ -187,7 +187,7 @@ tests: verification: | on 2nd controller using chip tool, remove fabric with FabricIndex=2 - ./chip-tool operationalcredentials remove-fabric 2 1 0 + ./chip-tool operationalcredentials remove-fabric 2 1 0 --commissioner-name beta CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0008 CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Command 0x0000_0008 @@ -206,13 +206,13 @@ tests: Using your 2nd controller, write attribute and read attribute to and from TH_CE Below is the example while using chip tool on second controller, - ./chip-tool basic write node-label te5new 2 0 + ./chip-tool basic write node-label te5new 2 0 --commissioner-name beta Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2 [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53 - ./chip-tool basic read node-label 2 0 + ./chip-tool basic read node-label 2 0 --commissioner-name beta Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2 @@ -300,7 +300,7 @@ tests: On 2nd controller using chip tool connect to the accessory - ./chip-tool pairing code 1 36217551633 + ./chip-tool pairing code 1 36217551633 --commissioner-name beta Verify you got below message Device commissioning completed with success @@ -314,7 +314,7 @@ tests: Below is the command using chip tool controller - ./chip-tool operationalcredentials read fabrics 1234 0 --fabric-filtered 0 + ./chip-tool operationalcredentials read fabrics 1234 0 --fabric-filtered 0 --commissioner-name beta CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0001 DataVersion: 2455995246 [1647863342.980899][9309:9314] CHIP:TOO: Fabrics: 3 entries diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_18.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_18.yaml index cbc714bc930b67..dce6d020f8c141 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_18.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_18.yaml @@ -14,8 +14,8 @@ # Auto-generated scripts for harness use only, please review before automation. The endpoints and cluster names are currently set to default name: - 4.1.18. [TC-CADMIN-1.18] Removing Fabrics from DUT and Fabric index - enumeration using BCM [DUT - Commissioner] + 30.1.18. [TC-CADMIN-1.18] Removing Fabrics from DUT and Fabric index + enumeration using BCM [DUT - Commissioner] PICS: - CADMIN.C @@ -52,7 +52,7 @@ tests: On your first controller chip tool, open commissioning window using BCM Below is the example when using chip tool as controller - ./chip-tool administratorcommissioning open-basic-commissioning-window 500 2 0 --timedInteractionTimeoutMs 1000 + ./chip-tool administratorcommissioning open-basic-commissioning-window 500 1 0 --timedInteractionTimeoutMs 1000 CHIP: [DMG] InvokeResponseMessage = @@ -93,7 +93,7 @@ tests: On 2nd controller using chip tool connect to the accessory - ./chip-tool pairing onnetwork 1 20202021 + ./chip-tool pairing onnetwork 2 20202021 --commissioner-name beta Verify you got below message Device commissioning completed with success @@ -148,7 +148,7 @@ tests: On 3rd controller using chip tool connect to the accessory - ./chip-tool pairing onnetwork 1 20202021 + ./chip-tool pairing onnetwork 3 20202021 --commissioner-name gamma Verify you got below message Device commissioning completed with success @@ -194,12 +194,12 @@ tests: " disabled: true - - label: "DUT_CR1 sends RemoveFabric with FabricIndex = 2 command to TH_CE" + - label: "DUT_CR1 sends RemoveFabric with FabricIndex = 2command to TH_CE" PICS: OPCREDS.C.C0a.Tx verification: | on 2nd controller using chip tool, remove fabric with FabricIndex=2 - ./chip-tool operationalcredentials remove-fabric 2 1 0 + ./chip-tool operationalcredentials remove-fabric 2 1 0 --commissioner-name beta CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0008 CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Command 0x0000_0008 @@ -218,13 +218,13 @@ tests: Using your 2nd controller, write attribute and read attribute to and from TH_CE Below is the example while using chip tool on second controller, - ./chip-tool basic write node-label te5new 2 0 + ./chip-tool basic write node-label te5new 2 0 --commissioner-name beta Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2 [1651819620.929700][4359:4364] CHIP:-: ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter at ../../commands/clusters/ModelCommand.cpp:53 - ./chip-tool basic read node-label 2 0 + ./chip-tool basic read node-label 2 0 --commissioner-name beta Received error (protocol code 2) during pairing process. ../../third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:1551: CHIP Error 0x00000054: Invalid CASE parameter [1651819620.929567][4359:4364] CHIP:CTL: OperationalDeviceProxy[B8070CD13C99D367:0000000000000002]: State change 3 --> 2 @@ -261,9 +261,7 @@ tests: [1647863260.287515][9294:9299] CHIP:EM: Sending Standalone Ack for MessageCounter:11301761 on exchange 13180i disabled: true - - label: - "Verify TH_CE is now discoverable over DNS-SD with 2 Operational - service records (_matter._tcp SRV records)." + - label: "" verification: | 1. Verify if the DUT is broadcasting using grl@grl-ThinkPad-L480:~/may16_cntrl03/connectedhomeip/examples/chip-tool/out/debug$ avahi-browse -rt _matter._tcp @@ -333,7 +331,7 @@ tests: On 2nd controller using chip tool connect to the accessory - ./chip-tool pairing onnetwork 1 20202021 + ./chip-tool pairing onnetwork 2 20202021 --commissioner-name beta Verify you got below message Device commissioning completed with success @@ -346,7 +344,7 @@ tests: Below is the command using chip tool controller - ./chip-tool operationalcredentials read fabrics 1234 0 --fabric-filtered 0 + ./chip-tool operationalcredentials read fabrics 1234 0 --fabric-filtered 0 --commissioner-name beta CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0001 DataVersion: 2455995246 [1647863342.980899][9309:9314] CHIP:TOO: Fabrics: 3 entries diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_19.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_19.yaml index 269f9e66c9f9b2..a59932b593d21c 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_19.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_19.yaml @@ -90,7 +90,7 @@ tests: On nth controller using chip tool connect to the accessory - ./chip-tool pairing code 6 36217551633 + ./chip-tool pairing code 6 36217551633 --commissioner-name beta CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0008 [1649756670.402192][10794:10799] CHIP:CTL: Device returned status 5 on receiving the NOC diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_2.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_2.yaml index 844c50fc29f807..2449a35f43ea41 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_2.yaml @@ -50,8 +50,11 @@ tests: verification: | On first controller, usinadministratorcommissioningg chip tool open commissioning window. + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool administratorcommissioning open-basic-commissioning-window 500 1 0 --timedInteractionTimeoutMs 1000 + On TH1(all-clusters-app) Log CHIP:DMG: InvokeResponseMessage = @@ -92,8 +95,12 @@ tests: verification: | On first controller, using chip tool read fabricList + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool operationalcredentials read fabrics 1 0 --fabric-filtered 0 + On TH1(all-clusters-app) Log + CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0001 DataVersion: 3621507058 [1649245801.244173][10091:10096] CHIP:TOO: Fabrics: 1 entries @@ -113,10 +120,12 @@ tests: verification: | On second Controller connect to the accessory. - Below is the example when using chip tool as controller + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool pairing onnetwork 2 20202021 --commissioner-name beta - Verify you got below message + Verify you got below message On TH2(all-clusters-app) Log Device commissioning completed with success disabled: true @@ -124,6 +133,10 @@ tests: verification: | On the raspi , Verify if the DUT is broadcasting using + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + + ubuntu@ubuntu:~/may10_cntrl2/connectedhomeip/examples/chip-tool/out/debug$ avahi-browse -rt _matter._tcp + eth0 IPv6 E0AF53B23E580769-0000000000000002 _matter._tcp local + eth0 IPv6 7FF84D214A19B581-0000000000000001 _matter._tcp local @@ -146,9 +159,14 @@ tests: verification: | On the 2nd controller write attribute and read attribute to and from TH_CE - Below is the example while using chip tool on second controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool basic write node-label te5new 2 0 --commissioner-name beta + On TH2(all-clusters-app) Log + + CHIP:DMG: WriteResponseMessage = [1649245940.788522][10110:10115] CHIP:DMG: { [1649245940.788577][10110:10115] CHIP:DMG: AttributeStatusIBs = @@ -177,7 +195,12 @@ tests: Verify read attribute returns the updated value written + ./chip-tool basic read node-label 1 0 --commissioner-name beta + + On TH2(all-clusters-app) Log + + CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0005 DataVersion: 3061847068 [1649245950.006849][10116:10121] CHIP:TOO: NodeLabel: te5new [1649245950.007024][10116:10121] CHIP:EM: Sending Standalone Ack for MessageCounter:12495101 on exchange 24816i @@ -189,9 +212,14 @@ tests: verification: | On second controller controller read fabricList - Below is the example while using chip tool on second controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool operationalcredentials read fabrics 2 0 --fabric-filtered 0 --commissioner-name beta + On TH2(all-clusters-app) Log + + CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0001 DataVersion: 3229397217 [1650277071.834099][40790:40795] CHIP:TOO: Fabrics: 2 entries [1650277071.834120][40790:40795] CHIP:TOO: [1]: { @@ -220,8 +248,14 @@ tests: verification: | On first controller, using chip-tool write attribute, Verify read attribute returns the updated value written. + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool basic write node-label te8 1 0 + On TH1(all-clusters-app) Log + + CHIP:DMG: WriteResponseMessage = [1649245940.788522][10110:10115] CHIP:DMG: { [1649245940.788577][10110:10115] CHIP:DMG: AttributeStatusIBs = @@ -249,7 +283,12 @@ tests: [1649245940.790167][10110:10115] CHIP:DMG: WriteClient moving to [AwaitingDe] Verify read attribute returns the updated value written + ./chip-tool basic read node-label 1 0 + + On TH1(all-clusters-app) Log + + CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0005 DataVersion: 3061847068 [1649245950.006849][10116:10121] CHIP:TOO: NodeLabel: te8 [1649245950.007024][10116:10121] CHIP:EM: Sending Standalone Ack for MessageCounter:12495101 on exchange 24816i @@ -262,11 +301,14 @@ tests: verification: | On second controller read, write attribute and then read attribute to and from TH_CE + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. - Below is the example while using chip tool on second controller, ./chip-tool basic write node-label te5new 2 0 --commissioner-name beta + On TH2(all-clusters-app) Log + + CHIP:DMG: WriteResponseMessage = [1649245940.788522][10110:10115] CHIP:DMG: { [1649245940.788577][10110:10115] CHIP:DMG: AttributeStatusIBs = @@ -296,6 +338,10 @@ tests: Verify read attribute returns the updated value written ./chip-tool basic read node-label 2 0 --commissioner-name beta + + On TH2(all-clusters-app) Log + + CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0005 DataVersion: 3061847068 [1649245950.006849][10116:10121] CHIP:TOO: NodeLabel: te5new [1649245950.007024][10116:10121] CHIP:EM: Sending Standalone Ack for MessageCounter:12495101 on exchange 24816i @@ -314,9 +360,13 @@ tests: verification: | On second controller using chip-tool open commissioning widow using BCM. - Below is the example while using chip tool on second controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool administratorcommissioning open-basic-commissioning-window 500 2 0 --timedInteractionTimeoutMs 1000 --commissioner-name beta + On TH2(all-clusters-app) Log + CHIP:DMG: InvokeResponseMessage = [1650278416.248379][11064:11069] CHIP:DMG: { @@ -358,9 +408,13 @@ tests: verification: | On second controller using chip-tool run revoke command - Below is the example while using chip tool on second controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool administratorcommissioning revoke-commissioning 2 0 --timedInteractionTimeoutMs 1000 --commissioner-name beta + On TH2(all-clusters-app) Log + CHIP:DMG: InvokeResponseMessage = [1650278416.248379][11064:11069] CHIP:DMG: { @@ -401,9 +455,13 @@ tests: PICS: CADMIN.C verification: | 1. On third controller, using chip-tool connect to the accessory. Connect attempt should fail, i.e + + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool pairing onnetwork 3 20202021 --commissioner-name gamma - verify you got the following message in the TH log + verify you got the following message in the TH3 (all-clusters-app) log CHIP:SC: PASESession timed out while waiting for a response from the peer. Expected message type was 33 CHIP:TOO: Secure Pairing Failed @@ -417,9 +475,14 @@ tests: verification: | On second controller, write attribute and read attribute to and from TH_CE - Below is the example while using chip tool on second controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool basic write node-label te5new 2 0 --commissioner-name beta + On TH2(all-clusters-app) Log + + CHIP:DMG: WriteResponseMessage = [1649245940.788522][10110:10115] CHIP:DMG: { [1649245940.788577][10110:10115] CHIP:DMG: AttributeStatusIBs = @@ -447,6 +510,9 @@ tests: [1649245940.790167][10110:10115] CHIP:DMG: WriteClient moving to [AwaitingDe] Verify read attribute returns the updated value written + + On TH2(all-clusters-app) Log + ./chip-tool basic read node-label 2 0 --commissioner-name beta CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0005 DataVersion: 3061847068 [1649245950.006849][10116:10121] CHIP:TOO: NodeLabel: te5new @@ -460,9 +526,13 @@ tests: verification: | On second controller using chip-tool open commissioning widow using BCM. - Below is the example while using chip tool on second controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool administratorcommissioning open-basic-commissioning-window 180 2 0 --timedInteractionTimeoutMs 1000 --commissioner-name beta + On TH2(all-clusters-app) Log + CHIP:DMG: InvokeResponseMessage = [1650278416.248379][11064:11069] CHIP:DMG: { @@ -510,9 +580,12 @@ tests: verification: | On second controller using chip-tool open commissioning widow using BCM. - Below is the example while using chip tool on second controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + + ./chip-tool administratorcommissioning open-basic-commissioning-window 500 2 0 --timedInteractionTimeoutMs 1000 --commissioner-name beta + On TH2(all-clusters-app) Log CHIP:DMG: InvokeResponseMessage = [1650278416.248379][11064:11069] CHIP:DMG: { @@ -554,9 +627,13 @@ tests: verification: | Using your 1st Controller connect to the accessory. - Below is the example when using chip tool as controller + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool pairing onnetwork 1 20202021 + On TH1(all-clusters-app) Log + + [1651786200275] [36301:315544] CHIP: [DMG] Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0008 [1651786200275] [36301:315544] CHIP: [CTL] Device returned status 9 on receiving the NOC [1651786200275] [36301:315544] CHIP: [CTL] Add NOC failed with error ../../src/controller/CHIPDeviceController.cpp:1187: CHIP Error 0x0000007E: Trying to add a NOC for a fabric that already exists diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_20.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_20.yaml index 50e30a8e4ef88f..0c279f676577c5 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_20.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_20.yaml @@ -111,7 +111,7 @@ tests: On nth controller using chip tool connect to the accessory - ./chip-tool pairing onnetwork 6 20202021 + ./chip-tool pairing onnetwork 6 20202021 --commissioner-name beta CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0008 [1649756670.402192][10794:10799] CHIP:CTL: Device returned status 5 on receiving the NOC diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_21.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_21.yaml index 4119e0fbebea8b..e7bf90a0f87fa8 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_21.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_21.yaml @@ -32,7 +32,7 @@ tests: Reset Devices to factory defaults disabled: true - - label: "TH_CR1 starts a commissioning process with DUT_CE using BCM" + - label: "TH_CR1 starts a commissioning process with DUT_CE" PICS: CADMIN.S.C01.Rsp verification: | "1. Provision the device using 1st controller chip tool(use above instructions) , @@ -40,8 +40,8 @@ tests: disabled: true - label: - "TH_CR1 opens a commissioning window on DUT_CE with a value of 900 - seconds" + "TH_CR1 opens a commissioning window on DUT_CE using BCM with a value + of 900 seconds" PICS: CADMIN.S.C01.Rsp verification: | On 1st controller chip tool, open commissioning window @@ -85,7 +85,7 @@ tests: [1650278416.250634][11064:11069] CHIP:DMG: ICR moving to [AwaitingDe] disabled: true - - label: "Wait for commissioning Window to 901 seconds" + - label: "Wait 901 seconds for commissioning Window to be closed" verification: | Wait for commissioning Window to Timeout disabled: true @@ -102,8 +102,8 @@ tests: disabled: true - label: - "TH_CR1 opens a commissioning window on DUT_CE with a value of 901 - seconds" + "TH_CR1 opens a commissioning window on DUT_CE using BCM with a value + of 901 seconds" PICS: CADMIN.S.C01.Rsp verification: | On 1st controller chip tool, open commissioning window diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_22.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_22.yaml index 261b804cfc05e6..7b650575ae706f 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_22.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_22.yaml @@ -31,7 +31,7 @@ tests: Reset Devices to factory defaults disabled: true - - label: "TH_CR1 starts a commissioning process with DUT_CE using ECM" + - label: "TH_CR1 starts a commissioning process with DUT_CE" PICS: CADMIN.S.C00.Rsp verification: | "1. Provision the device using 1st controller chip tool(use above instructions) , @@ -39,8 +39,8 @@ tests: disabled: true - label: - "TH_CR1 opens a commissioning window on DUT_CE with a value of 900 - seconds" + "TH_CR1 opens a commissioning window on DUT_CE using ECM with a value + of 900 seconds" PICS: CADMIN.S.C00.Rsp verification: | On 1st controller chip tool, open commissioning window @@ -64,35 +64,15 @@ tests: [1635925713.973178][9695:9700] CHIP:EM: Sending Standalone Ack for MessageCounter:1964916542 on exchange 31055i disabled: true - - label: "Wait for commissioning Window to 901 seconds" + - label: "Wait 901 seconds for commissioning Window to be closed" verification: | - On 1st controller chip tool, open commissioning window - - Below is the example when using chip tool as controller - - - For ECM, - ./chip-tool pairing open-commissioning-window 1 1 900 1000 3840 - - [1635925713.966786][9695:9700] CHIP:SC: Success status report received. Session was established - [1635925713.966839][9695:9700] CHIP:IN: New secure session created for device 0x0000000000000001, key 33!! - [1635925713.966938][9695:9700] CHIP:CTL: OpenCommissioningWindow for device ID 1 - [1635925713.972601][9695:9700] CHIP:DMG: ICR moving to [AddingComm] - [1635925713.972705][9695:9700] CHIP:DMG: ICR moving to [AddedComma] - [1635925713.972815][9695:9700] CHIP:IN: Prepared encrypted message 0xaaaad9b57d10 to 0x0000000000000001 of type 0x8 and protocolId (0, 1) on exchange 31056i with MessageCounter:0. - [1635925713.972876][9695:9700] CHIP:IN: Sending encrypted msg 0xaaaad9b57d10 with MessageCounter:0 to 0x0000000000000001 at monotonic time: 13449459 msec - [1635925713.973006][9695:9700] CHIP:DMG: ICR moving to [CommandSen] - [1635925713.973061][9695:9700] CHIP:CTL: Manual pairing code: [35484132896] - [1635925713.973120][9695:9700] CHIP:CTL: SetupQRCode: [MT:00000CQM00A7F87ZT10] - [1635925713.973178][9695:9700] CHIP:EM: Sending Standalone Ack for MessageCounter:1964916542 on exchange 31055i + Wait for commissioning Window to Timeout disabled: true - label: "TH_CR1 reads the window status to verify the DUT_CE window is closed" PICS: CADMIN.S.A0000 verification: | - On 1st controller read window status - ./chip-tool administratorcommissioning read window-status 1 0 CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003C Attribute 0x0000_0000 DataVersion: 2849200592 @@ -101,17 +81,14 @@ tests: disabled: true - label: - "TH_CR1 opens a commissioning window on DUT_CE with a value of 901 - seconds" + "TH_CR1 opens a commissioning window on DUT_CE using ECM with a value + of 901 seconds" PICS: CADMIN.S.C00.Rsp verification: | On 1st controller chip tool, open commissioning window - Below is the example when using chip tool as controller - - - For ECM, - ./chip-tool pairing open-commissioning-window 1 1 901 1000 3840 + For BCM, + ./chip-tool administratorcommissioning open-basic-commissioning-window 901 2 0 --timedInteractionTimeoutMs 1000 CHIP:DMG: Received Command Response Status for Endpoint=0 Cluster=0x0000_003C Command=0x0000_0001 Status=0x85 [1652860801.225084][9512:9517] CHIP:TOO: Error: IM Error 0x00000585: General error: 0x85 (INVALID_COMMAND) @@ -123,7 +100,7 @@ tests: "TH_CR1 reads the window status to verify the DUT_CE window is closed" PICS: CADMIN.S.A0000 verification: | - On first controller, read window status + On 1st controller read window status ./chip-tool administratorcommissioning read window-status 1 0 diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_7.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_7.yaml index c8371b511790e7..c71b2bbee02a5d 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_7.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_7.yaml @@ -326,3 +326,18 @@ tests: CHIP:TOO: Secure Pairing Failed CHIP:TOO: Pairing Failure: ../../third_party/connectedhomeip/src/protocols/secure_channel/PASESession.cpp:324: CHIP Error 0x00000032: Timeout disabled: true + + - label: "" + verification: | + verification step to be updated. + disabled: true + + - label: "" + verification: | + verification step to be updated. + disabled: true + + - label: "" + verification: | + verification step to be updated. + disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_CADMIN_1_8.yaml b/src/app/tests/suites/certification/Test_TC_CADMIN_1_8.yaml index eea76fb7b1cb0f..963add49c1e061 100644 --- a/src/app/tests/suites/certification/Test_TC_CADMIN_1_8.yaml +++ b/src/app/tests/suites/certification/Test_TC_CADMIN_1_8.yaml @@ -50,10 +50,12 @@ tests: verification: | On your 1st controller open commissioning widow using BCM. - Below is the example while using chip tool as controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. ./chip-tool administratorcommissioning open-basic-commissioning-window 500 2 0 --timedInteractionTimeoutMs 1000 + Verify success response On TH1(all-clusters-app) Log + CHIP:DMG: InvokeResponseMessage = [1650278416.248379][11064:11069] CHIP:DMG: { [1650278416.248436][11064:11069] CHIP:DMG: suppressResponse = false, @@ -116,9 +118,12 @@ tests: verification: | On the 2nd controller using chip-tool , connect to the accessory + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool pairing onnetwork 2 20202021 --commissioner-name beta - verify you got the following message in the TH log + verify you got the following message in the TH2 (all-clusters-app) log + CHIP:SC: PASESession timed out while waiting for a response from the peer. Expected message type was 33 CHIP:TOO: Secure Pairing Failed CHIP:TOO: Pairing Failure: ../../third_party/connectedhomeip/src/protocols/secure_channel/PASESession.cpp:324: CHIP Error 0x00000032: Timeout @@ -132,10 +137,11 @@ tests: verification: | On your first controller open commissioning widow using BCM. - Below is the example while using chip tool as controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. ./chip-tool administratorcommissioning open-basic-commissioning-window 500 1 0 --timedInteractionTimeoutMs 1000 + Verify success response On TH1(all-clusters-app) Log CHIP:DMG: InvokeResponseMessage = [1650278416.248379][11064:11069] CHIP:DMG: { @@ -175,9 +181,12 @@ tests: verification: | On your DUT controller revoke commissioning - Below is the example while using chip tool as controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + /chip-tool administratorcommissioning revoke-commissioning 1 0 --timedInteractionTimeoutMs 1000 + Verify success response On TH1(all-clusters-app) Log + CHIP:DMG: InvokeResponseMessage = [1650278416.248379][11064:11069] CHIP:DMG: { [1650278416.248436][11064:11069] CHIP:DMG: suppressResponse = false, @@ -216,9 +225,12 @@ tests: verification: | On the 2nd controller using chip-tool , connect to the accessory + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool pairing onnetwork 2 20202021 --commissioner-name beta - verify you got the following message in the TH log + verify you got the following message in the TH2(all-clusters-app) log + CHIP:SC: PASESession timed out while waiting for a response from the peer. Expected message type was 33 CHIP:TOO: Secure Pairing Failed CHIP:TOO: Pairing Failure: ../../third_party/connectedhomeip/src/protocols/secure_channel/PASESession.cpp:324: CHIP Error 0x00000032: Timeout @@ -229,10 +241,12 @@ tests: verification: | On your 1st controller revoke commissioning - Below is the example while using chip tool as controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. /chip-tool administratorcommissioning revoke-commissioning 1 0 --timedInteractionTimeoutMs 1000 + Verify success response On TH1(all-clusters-app) Log + CHIP:DMG: InvokeResponseMessage = [1650524034.111241][15422:15427] CHIP:DMG: { [1650524034.111316][15422:15427] CHIP:DMG: suppressResponse = false, @@ -274,9 +288,12 @@ tests: verification: | Using 1st controller, write attribute and read attribute to and from TH_CE - Below is the example while using chip tool on second controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool basic write node-label te5new 2 0 + Verify success response On TH1(all-clusters-app) Log + CHIP:DMG: WriteResponseMessage = [1649245940.788522][10110:10115] CHIP:DMG: { [1649245940.788577][10110:10115] CHIP:DMG: AttributeStatusIBs = @@ -303,8 +320,11 @@ tests: [1649245940.790033][10110:10115] CHIP:DMG: } [1649245940.790167][10110:10115] CHIP:DMG: WriteClient moving to [AwaitingDe] - Verify read attribute returns the updated value written + ./chip-tool basic read node-label 2 0 + + Verify read attribute returns the updated value written On TH1(all-clusters-app) Log + CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0005 DataVersion: 3061847068 [1649245950.006849][10116:10121] CHIP:TOO: NodeLabel: te5new [1649245950.007024][10116:10121] CHIP:EM: Sending Standalone Ack for MessageCounter:12495101 on exchange 24816i @@ -318,11 +338,11 @@ tests: verification: | On 1st controller open commissioning widow using BCM. - Below is the example while using chip tool as controller, + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. ./chip-tool administratorcommissioning open-basic-commissioning-window 500 2 0 --timedInteractionTimeoutMs 1000 - + Verify success response On TH1(all-clusters-app) Log CHIP:DMG: InvokeResponseMessage = [1650278416.248379][11064:11069] CHIP:DMG: { @@ -362,9 +382,11 @@ tests: verification: | On the 2nd controller using chip-tool , connect to the accessory + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool pairing onnetwork 2 20202021 --commissioner-name beta - Verify you got below message + Verify you got below message on TH2(all-clusters-app) log Device commissioning completed with success disabled: true @@ -373,9 +395,11 @@ tests: verification: | On the 3rd controller using chip-tool , connect to the accessory + Below are the example command using chip-tool with single RPI. Vendor should have the provision to use the equivalent command with their DUT and for the second and third commissioners. + ./chip-tool pairing onnetwork 3 20202021 --commissioner-name gamma - verify you got the following message in the TH log + verify you got the following message in the TH3(all-clusters-app) log CHIP:SC: PASESession timed out while waiting for a response from the peer. Expected message type was 33 CHIP:TOO: Secure Pairing Failed CHIP:TOO: Pairing Failure: ../../third_party/connectedhomeip/src/protocols/secure_channel/PASESession.cpp:324: CHIP Error 0x00000032: Timeout diff --git a/src/app/tests/suites/certification/Test_TC_CGEN_2_2.yaml b/src/app/tests/suites/certification/Test_TC_CGEN_2_2.yaml index 2a051a0531c254..3598f9811bc510 100644 --- a/src/app/tests/suites/certification/Test_TC_CGEN_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_CGEN_2_2.yaml @@ -100,8 +100,9 @@ tests: Once build completes 3. cd out/debug 4. ./chip-cert gen-cert --type r --subject-chip-id CACACACA00000001 --valid-from "2020-10-15 14:23:43" --lifetime 7305 --out-key Chip-Root-Key.txt --out Chip-Root-Cert.txt --out-format chip-hex - 5. cat Chip-Root-Key.txt + 5. cat Chip-Root-Cert.txt + While adding new add-trusted-root-certificate please use the above generated new root key ./chip-tool operationalcredentials add-trusted-root-certificate hex:1530010828c376ebc17f21512402013703271401000000cacacaca182604ef171b2726056eb5b94c3706271401000000cacacaca182407012408013009410452c19fd9d329a738fd65722a8309fa68bcaa9ffe87d8114b802c922e5066d0b2f0573b89b38bf98fc9c424ab8ffdabcb18d42e623d82a02d0ca0c062ccadb4bc370a350129011824026030041457934de5405e9a40eacb86ee647e583141ae78f430051457934de5405e9a40eacb86ee647e583141ae78f418300b40a0b0d57bddbc7bcf44480a8b7bd0231d54ccacd68d90efb67b7aa3206adbd268725092992a0388c8e934504178613c5b932d422eed7463f38fd82aaa429b574a18 1 0 diff --git a/src/app/tests/suites/certification/Test_TC_DA_1_4.yaml b/src/app/tests/suites/certification/Test_TC_DA_1_4.yaml index 056047d867594d..914a15ac8d93f5 100644 --- a/src/app/tests/suites/certification/Test_TC_DA_1_4.yaml +++ b/src/app/tests/suites/certification/Test_TC_DA_1_4.yaml @@ -28,7 +28,14 @@ config: tests: - label: "Note" verification: | - Chip-tool command used below are an example to verify the DUT as client test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + Chip-tool command used below are an example to verify the DUT as commissioner test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + disabled: true + + - label: "Pre-Conditions" + verification: | + 1. PAA, PAI, DAC certificates are obtained and validated + 2. Operations happen within the Fail-Safe Context + 3. TH1 should be known about Commissioner based error condition/warning disabled: true - label: "Start the commissioning process of TH1 on DUT" @@ -207,7 +214,7 @@ tests: Product ID (PID) the DAC is not present in the product_id_array field in the Certification Declaration" verification: | - To Execute ths step for error condition 1 follow the following + To Execute ths step for error condition 1 follow the following steps 1. To generate the CD use the below command ./out/debug/chip-cert gen-cd -I -E dac-origin-vid-present -C credentials/test/certification-declaration/Chip-Test-CD-Signing-Cert.pem -K credentials/test/certification-declaration/Chip-Test-CD-Signing-Key.pem --out cd_vid_present_pid_missing.txt -o 0x8000 -r 0xFFF1 -f 1 -V FFF1 -p 8000 -p 8001 -p 8002 -p 8003 -p 8004 -p 8005 -p 8006 -p 8007 -p 8008 -p 8009 -p 800A -p 800B -p 800C -p 800D -p 800E -p 800F -p 8010 -p 8011 -p 8012 -p 8013 -p 8014 -p 8015 -p 8016 -p 8017 -p 8018 -p 8019 -p 801A -p 801B -p 801C -p 801D -p 801E -p 801F -p 8020 -p 8021 -p 8022 -p 8023 -p 8024 -p 8025 -p 8026 -p 8027 -p 8028 -p 8029 -p 802A -p 802B -p 802C -p 802D -p 802E -p 802F -p 8030 -p 8031 -p 8032 -p 8033 -p 8034 -p 8035 -p 8036 -p 8037 -p 8038 -p 8039 -p 803A -p 803B -p 803C -p 803D -p 803E -p 803F -p 8040 -p 8041 -p 8042 -p 8043 -p 8044 -p 8045 -p 8046 -p 8047 -p 8048 -p 8049 -p 804A -p 804B -p 804C -p 804D -p 804E -p 804F -p 8050 -p 8051 -p 8052 -p 8053 -p 8054 -p 8055 -p 8056 -p 8057 -p 8058 -p 8059 -p 805A -p 805B -p 805C -p 805D -p 805E -p 805F -p 8060 -p 8061 -p 8062 -p 8063 -d 0016 -c "ZIG20142ZB330003-24" -l 0 -i 0 -n 2694 -t 0 @@ -244,4 +251,8 @@ tests: [1658320561.366481][4126:4132] CHIP:CTL: Going from commissioning step "AttestationVerification" with lastErr = "../../third_party/connectedhomeip/src/controller/CHIPDeviceController.cpp:1011: CHIP Error 0x000000AC: Internal error" -> "Cleanup" [1658320561.366524][4126:4132] CHIP:CTL: Performing next commissioning step "Cleanup" with completion status = "../../third_party/connectedhomeip/src/controller/CHIPDeviceController.cpp:1011: CHIP Error 0x000000AC: Internal error" [1658320561.366554][4126:4132] CHIP:CTL: Expiring failsafe on proxy 0xffff84000b60 + + Similary for 2nd error condition follow the below steps + + 1. 1. To generate the CD use the below command disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DA_1_5.yaml b/src/app/tests/suites/certification/Test_TC_DA_1_5.yaml index 1ab2e84c96a65e..717ee8f06dc1d0 100644 --- a/src/app/tests/suites/certification/Test_TC_DA_1_5.yaml +++ b/src/app/tests/suites/certification/Test_TC_DA_1_5.yaml @@ -38,7 +38,7 @@ tests: "TH1 establishes a CASE session to the DUT and saves the attestation challenge as attestation_challenge" verification: | - Verify in TH log: + Verify case session is established on TH(chip-tool) log: [1657081321.112631][2354:2359] CHIP:CTL: Operational credentials provisioned on device 0xffff68000b60 [1657081321.112706][2354:2359] CHIP:TOO: Secure Pairing Success @@ -51,7 +51,7 @@ tests: verification: | ./chip-tool operationalcredentials certificate-chain-request 1 1 0 - Verify CertificateChainResponse in TH log: + Verify CertificateChainResponse on TH(chip-tool) log: [1658393690.991117][3329:3334] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0003 [1658393690.991168][3329:3334] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Command 0x0000_0003 @@ -67,7 +67,7 @@ tests: verification: | ./chip-tool generalcommissioning arm-fail-safe 900 0 1 0 - Verify ArmFailSafeResponse in TH log : + Verify ArmFailSafeResponse on TH(chip-tool) log : [1658393763.804225][3345:3350] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0030 Command=0x0000_0001 [1658393763.804288][3345:3350] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0030 Command 0x0000_0001 [1658393763.804376][3345:3350] CHIP:TOO: ArmFailSafeResponse: { @@ -86,7 +86,7 @@ tests: ./chip-tool operationalcredentials csrrequest hex:AFB3070A828B7A9CABEE888688F867683C084E6E4B3F13CDEDF17EEF05A9F352 1 0 - Verify CSRResponse in TH log: + Verify CSRResponse on TH(chip-tool) log: [1658393935.238621][3359:3364] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003E Command=0x0000_0005 [1658393935.238726][3359:3364] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Command 0x0000_0005 [1658393935.238839][3359:3364] CHIP:TOO: CSRResponse: { @@ -111,13 +111,18 @@ tests: verification step to be updated. disabled: true + - label: "" + verification: | + verification step to be updated. + disabled: true + - label: "TH1 sends an ArmFailSafe command to the General Commissioning cluster with the ExpiryLengthSeconds field set to 0" verification: | ./chip-tool generalcommissioning arm-fail-safe 0 0 1 0 - Verify ArmFailSafeResponse in TH log : + Verify ArmFailSafeResponse on TH(chip-tool) log : [1658394142.961248][3378:3383] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0030 Command=0x0000_0001 [1658394142.961297][3378:3383] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0030 Command 0x0000_0001 @@ -133,7 +138,7 @@ tests: verification: | ./chip-tool generalcommissioning arm-fail-safe 900 0 1 0 - Verify ArmFailSafeResponse in TH log : + Verify ArmFailSafeResponse on TH(chip-tool) log : [1658393763.804225][3345:3350] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0030 Command=0x0000_0001 [1658393763.804288][3345:3350] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0030 Command 0x0000_0001 @@ -149,7 +154,7 @@ tests: verification: | ./chip-tool operationalcredentials csrrequest hex:AFB3070A828B7A9CABEE888688F867683C084E6E4B3F13CDEDF17EEF05A9 1 0 - Verify General error INVALID_COMMAND in TH log: + Verify General error INVALID_COMMAND in TH(chip-tool) log: [1658394196.798739][3387:3392] CHIP:EM: Removed CHIP MessageCounter:192677922 from RetransTable on exchange 13029i [1658394196.798787][3387:3392] CHIP:DMG: ICR moving to [ResponseRe] [1658394196.798859][3387:3392] CHIP:DMG: InvokeResponseMessage = @@ -191,7 +196,7 @@ tests: verification: | ./chip-tool generalcommissioning arm-fail-safe 0 0 1 0 - Verify ArmFailSafeResponse in TH log : + Verify ArmFailSafeResponse in TH(chip-tool) log : [1658394142.961248][3378:3383] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0030 Command=0x0000_0001 [1658394142.961297][3378:3383] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0030 Command 0x0000_0001 @@ -207,7 +212,7 @@ tests: verification: | ./chip-tool pairing open-commissioning-window 1 1 400 2000 3840 - Verify TH1 open commissiong window + Verify manual pairing code on TH(chip-tool) log [1658394279.082812][3401:3407] CHIP:DMG: Received Command Response Status for Endpoint=0 Cluster=0x0000_003C Command=0x0000_0000 Status=0x0 [1658394279.082900][3401:3407] CHIP:CTL: Successfully opened pairing window on the device @@ -217,9 +222,9 @@ tests: - label: "TH2 fully commissions the DUT" verification: | - ./chip-tool pairing code 2 34941319897 --trace_decode 1 + ./chip-tool pairing code 2 34941319897 --trace_decode 1 --commissioner-name beta - Verify in TH2 is commissioned successfully in log: + Verify TH2 is commissioned successfully on TH2(chip-tool) log: [1658394409.242162][2474:2479] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0030 Command=0x0000_0005 [1658394409.242204][2474:2479] CHIP:CTL: Received CommissioningComplete response, errorCode=0 [1658394409.242237][2474:2479] CHIP:CTL: Successfully finished commissioning step "SendComplete" @@ -233,9 +238,9 @@ tests: "TH2 reads the NOCs attribute from the Node Operational Credentials cluster using a non-fabric-scoped read" verification: | - ./chip-tool operationalcredentials read nocs 2 0 + ./chip-tool operationalcredentials read nocs 2 0 --commissioner-name beta - Verify that there are two element in the list in TH2 log: + Verify that there are two element in the list on TH2(chip-tool) log: [1658394451.122862][2491:2496] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003E Attribute 0x0000_0000 DataVersion: 1660110007 [1658394451.126674][2491:2496] CHIP:TOO: NOCs: 1 entries [1658394451.126806][2491:2496] CHIP:TOO: [1]: { @@ -247,13 +252,13 @@ tests: - label: "TH2 extracts the pubic key from noc1 and noc2" verification: | - Verify both public key of noc1 and noc 2 are different + Verify both public key of noc1 and noc 2 are different in TH (all-clusters-app) To extract public key follow the below step 1. Copy the NOCVALUE of TH1 in commissioning log of TH1 2. save it in a file 3. give below command to get public key - ./out/debug/chip-cert print-cert noc_1.txt + ./out/debug/chip-cert print-cert noc_1.txt --commissioner-name beta ---> The extracted public key of noc1 is CHIP Certificate: @@ -280,6 +285,9 @@ tests: BA D5 4F AC 3F F0 81 6E 0B D3 E0 BE C9 7E 8E FE FB 7A 28 67 8E BA 58 8F D9 74 F1 4D C4 82 C5 F4 + + + --->Follow the same steps for noc2 The generated public key for noc2 is CHIP Certificate: diff --git a/src/app/tests/suites/certification/Test_TC_DA_1_6.yaml b/src/app/tests/suites/certification/Test_TC_DA_1_6.yaml index 8881c34f0fba45..16dee77a88b348 100644 --- a/src/app/tests/suites/certification/Test_TC_DA_1_6.yaml +++ b/src/app/tests/suites/certification/Test_TC_DA_1_6.yaml @@ -26,15 +26,14 @@ config: tests: - label: "Note" verification: | - Chip-tool command used below are an example to verify the DUT as client test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + Chip-tool command used below are an example to verify the DUT as commissioner test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. disabled: true - - label: - "Pre-Conditions 1. Device Attestation is completed 2. PAI, DAC - certificates are obtained and validated against externally obtained - PAA certificate 3. Operations happen within the Fail-Safe Context" + - label: "Pre-Conditions" verification: | - verification step to be updated. + 1. Device Attestation is completed + 2. PAI, DAC certificates are obtained and validated against externally obtained PAA certificate + 3. Operations happen within the Fail-Safe Context disabled: true - label: "DUT completes the attestation procedure" diff --git a/src/app/tests/suites/certification/Test_TC_DGGEN_2_2.yaml b/src/app/tests/suites/certification/Test_TC_DGGEN_2_2.yaml index 91486a9f19c52f..e9426841124b86 100644 --- a/src/app/tests/suites/certification/Test_TC_DGGEN_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_DGGEN_2_2.yaml @@ -25,9 +25,23 @@ config: endpoint: 0 tests: + - label: "Note" + verification: | + "NOTE: https://github.com/project-chip/connectedhomeip/tree/master/examples/all-clusters-app/linux#readme + Events to be executed as following + 1. Compile app using below command in connectedhomeip folder + a. ./scripts/run_in_build_env.sh ""./scripts/build/build_examples.py --target linux-arm64-all-clusters-no-ble-asan-clang build"" + b. ./scripts/run_in_build_env.sh ""./scripts/build/build_examples.py --target linux-arm64-all-clusters-no-ble-asan-libfuzzer-clang build"" + 2. Build respective app (all-clusters-app) + 3. Commission DUT to TH + 4. Open 2nd terminal of DUT and provide the below command to obtain PID of DUT + ps -aef|grep all-clusters-app + 5. Follow the Verification step below to generate the event in 2nd terminal of DUT " + disabled: true + - label: "Commission DUT to TH" verification: | - verification step to be updated. + disabled: true - label: @@ -133,52 +147,3 @@ tests: [1659530352.583789][4993:4998] CHIP:TOO: BootReason: 0 [1659530352.583813][4993:4998] CHIP:TOO: } disabled: true - - - label: "TH initiates the subscription of NetworkFault event from DUT." - PICS: DGGEN.S.E02 - verification: | - On Raspi platform the event is triggered with below command, Pls use equivalent command on the respective DUT - - "echo "{"Name":"NetworkFaultChange"}" > /tmp/chip_all_clusters_fifo- (PID of all-clusters-app)" - - - sudo ./chip-tool generaldiagnostics subscribe-event network-fault-change 100 1000 1 0 - On TH(chip-tool) verify that subscription response of NetworkFault event shows subscrition ID - - [1653659901.757441][242605:242610] CHIP:EM: Received message of type 0x4 with protocolId (0, 1) and MessageCounter:11933575 on exchange 20223i - [1653659901.757513][242605:242610] CHIP:EM: Found matching exchange: 20223i, Delegate: 0x7fd058003950 - [1653659901.757544][242605:242610] CHIP:EM: Rxd Ack; Removing MessageCounter:3369789 from Retrans Table on exchange 20223i - [1653659901.757564][242605:242610] CHIP:EM: Removed CHIP MessageCounter:3369789 from RetransTable on exchange 20223i - [1653659901.757618][242605:242610] CHIP:DMG: SubscribeResponseMessage = - [1653659901.757638][242605:242610] CHIP:DMG: { - [1653659901.757658][242605:242610] CHIP:DMG: SubscriptionId = 0x17dc072d1130a3bd, - [1653659901.757676][242605:242610] CHIP:DMG: MinIntervalFloorSeconds = 0x64, - [1653659901.757690][242605:242610] CHIP:DMG: MaxIntervalCeilingSeconds = 0x3e8, - [1653659901.757708][242605:242610] CHIP:DMG: InteractionModelRevision = 1 - [1653659901.757721][242605:242610] CHIP:DMG: } - [1653659901.757746][242605:242610] CHIP:DMG: Subscription established with SubscriptionID = 0x17DC072D1130A3BD MinInterval = 100s MaxInterval = 1000s Peer = 01:0000000000000002 - disabled: true - - - label: - "Reboot DUT with a normal reboot process. Rejoin DUT back to previous - TH fabric." - PICS: DGGEN.S.E03 - verification: | - On Raspi platform the event is triggered with below command, Pls use equivalent command on the respective DUT - - "echo "{"Name":""}" > /tmp/chip_all_clusters_fifo- (PID of all-clusters-app)" - - - 1. Reboot DUT with a normal reboot process - 2. ./chip-tool generaldiagnostics read-event boot-reason 1 0 - On TH(chip-tool) verify that the event data of BootReason specified by Table 103 BootReason ENUM table. - - CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0033 Event 0x0000_0003 - [1651562139.644134][7873:7878] CHIP:TOO: Event number: 1 - [1651562139.644157][7873:7878] CHIP:TOO: Priority: Critical - [1651562139.644179][7873:7878] CHIP:TOO: Timestamp: 8347991 - [1651562139.644273][7873:7878] CHIP:TOO: BootReason: { - [1651562139.644317][7873:7878] CHIP:TOO: BootReason: 0 - [1651562139.644343][7873:7878] CHIP:TOO: } - [1651562139.644431][7873:7878] CHIP:EM: Sending Standalone Ack for MessageCounter:9685408 on exchange 6383i - disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DGSW_3_1.yaml b/src/app/tests/suites/certification/Test_TC_DGSW_3_1.yaml index a30e6eafd57456..9771f051c5759c 100644 --- a/src/app/tests/suites/certification/Test_TC_DGSW_3_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_DGSW_3_1.yaml @@ -26,12 +26,12 @@ config: tests: - label: "Note" verification: | - Chip-tool command used below are an example to verify the DUT as client test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + 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: "Commission TH to DUT" verification: | - verification step to be updated. + disabled: true - label: "DUT reads a list of ThreadMetrics struct attribute from TH." @@ -107,19 +107,19 @@ tests: [1659972063.411625][3458:3458] CHIP:IM: Received Read request [1659972063.411702][3458:3458] CHIP:DMG: ReadRequestMessage = [1659972063.411740][3458:3458] CHIP:DMG: { - [1659972063.411763][3458:3458] CHIP:DMG: AttributePathIBs = - [1659972063.411789][3458:3458] CHIP:DMG: [ - [1659972063.411822][3458:3458] CHIP:DMG: AttributePathIB = - [1659972063.411852][3458:3458] CHIP:DMG: { - [1659972063.411892][3458:3458] CHIP:DMG: Endpoint = 0x0, - [1659972063.411932][3458:3458] CHIP:DMG: Cluster = 0x34, - [1659972063.411964][3458:3458] CHIP:DMG: Attribute = 0x0000_0002, - [1659972063.412003][3458:3458] CHIP:DMG: } + [1659972063.411763][3458:3458] CHIP:DMG: AttributePathIBs = + [1659972063.411789][3458:3458] CHIP:DMG: [ + [1659972063.411822][3458:3458] CHIP:DMG: AttributePathIB = + [1659972063.411852][3458:3458] CHIP:DMG: { + [1659972063.411892][3458:3458] CHIP:DMG: Endpoint = 0x0, + [1659972063.411932][3458:3458] CHIP:DMG: Cluster = 0x34, + [1659972063.411964][3458:3458] CHIP:DMG: Attribute = 0x0000_0002, + [1659972063.412003][3458:3458] CHIP:DMG: } [1659972063.412032][3458:3458] CHIP:DMG: - [1659972063.412069][3458:3458] CHIP:DMG: ], + [1659972063.412069][3458:3458] CHIP:DMG: ], [1659972063.412106][3458:3458] CHIP:DMG: - [1659972063.412133][3458:3458] CHIP:DMG: isFabricFiltered = true, - [1659972063.412165][3458:3458] CHIP:DMG: InteractionModelRevision = 1 + [1659972063.412133][3458:3458] CHIP:DMG: isFabricFiltered = true, + [1659972063.412165][3458:3458] CHIP:DMG: InteractionModelRevision = 1 [1659972063.412191][3458:3458] CHIP:DMG: }, [1659972063.412273][3458:3458] CHIP:DMG: IM RH moving to [GeneratingReports] [1659972063.412375][3458:3458] CHIP:DMG: Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0 @@ -139,19 +139,19 @@ tests: [1659972088.497642][3458:3458] CHIP:IM: Received Read request [1659972088.497747][3458:3458] CHIP:DMG: ReadRequestMessage = [1659972088.497787][3458:3458] CHIP:DMG: { - [1659972088.497816][3458:3458] CHIP:DMG: AttributePathIBs = - [1659972088.497854][3458:3458] CHIP:DMG: [ - [1659972088.497889][3458:3458] CHIP:DMG: AttributePathIB = - [1659972088.497928][3458:3458] CHIP:DMG: { - [1659972088.497970][3458:3458] CHIP:DMG: Endpoint = 0x0, - [1659972088.498016][3458:3458] CHIP:DMG: Cluster = 0x34, - [1659972088.498061][3458:3458] CHIP:DMG: Attribute = 0x0000_0003, - [1659972088.498103][3458:3458] CHIP:DMG: } + [1659972088.497816][3458:3458] CHIP:DMG: AttributePathIBs = + [1659972088.497854][3458:3458] CHIP:DMG: [ + [1659972088.497889][3458:3458] CHIP:DMG: AttributePathIB = + [1659972088.497928][3458:3458] CHIP:DMG: { + [1659972088.497970][3458:3458] CHIP:DMG: Endpoint = 0x0, + [1659972088.498016][3458:3458] CHIP:DMG: Cluster = 0x34, + [1659972088.498061][3458:3458] CHIP:DMG: Attribute = 0x0000_0003, + [1659972088.498103][3458:3458] CHIP:DMG: } [1659972088.498144][3458:3458] CHIP:DMG: - [1659972088.498180][3458:3458] CHIP:DMG: ], + [1659972088.498180][3458:3458] CHIP:DMG: ], [1659972088.498219][3458:3458] CHIP:DMG: - [1659972088.498257][3458:3458] CHIP:DMG: isFabricFiltered = true, - [1659972088.498294][3458:3458] CHIP:DMG: InteractionModelRevision = 1 + [1659972088.498257][3458:3458] CHIP:DMG: isFabricFiltered = true, + [1659972088.498294][3458:3458] CHIP:DMG: InteractionModelRevision = 1 [1659972088.498328][3458:3458] CHIP:DMG: }, [1659972088.498431][3458:3458] CHIP:DMG: IM RH moving to [GeneratingReports] [1659972088.498545][3458:3458] CHIP:DMG: Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0 diff --git a/src/app/tests/suites/certification/Test_TC_DRLK_2_6.yaml b/src/app/tests/suites/certification/Test_TC_DRLK_2_6.yaml index caa3ac7574991a..30977190efa2a7 100644 --- a/src/app/tests/suites/certification/Test_TC_DRLK_2_6.yaml +++ b/src/app/tests/suites/certification/Test_TC_DRLK_2_6.yaml @@ -27,9 +27,14 @@ config: endpoint: 0 tests: + - label: "Pre-Conditions" + verification: | + DUT as server + disabled: true + - label: "TH reads NumberOfHoliday SchedulesSupported and saves for future use." - PICS: DRLK.S.F04 && DRLK.S.A0016 + PICS: DRLK.S.F11 && DRLK.S.A0016 verification: | ./chip-tool doorlock read number-of-holiday-schedules-supported 1 1 Verify " NumberOfHoliDay SchedulesSuppored" on the TH(Chip-tool) Log: @@ -46,7 +51,7 @@ tests: "TH sends Set Holiday Schedule Command to DUT with the following values: HolidayIndex as 1 LocalStartTime as 20 Seconds LocalEndTime as 30 Seconds OperatingMode as 0" - PICS: DRLK.S.F04 && DRLK.S.C11.Rsp + PICS: DRLK.S.F11 && DRLK.S.C11.Rsp verification: | ./chip-tool doorlock set-holiday-schedule 1 20 30 0 1 1 Verify " DUT send SUCCESS response." on the TH(Chip-tool) Log: @@ -68,7 +73,7 @@ tests: - label: "TH sends Get Holiday Schedule Command to DUT with HolidayIndex as 1" - PICS: DRLK.S.F04 && DRLK.S.C12.Rsp && DRLK.S.C12.Tx + PICS: DRLK.S.F11 && DRLK.S.C12.Rsp && DRLK.S.C12.Tx verification: | ./chip-tool doorlock get-holiday-schedule 1 1 1 Verify " DUT responds with Get Holiday Schedule Response" on the TH(Chip-tool) Log: @@ -126,7 +131,7 @@ tests: - label: "TH sends Get Holiday Schedule Command to DUT with Invalid HolidayIndex as 15." - PICS: DRLK.S.F04 && DRLK.S.C12.Rsp && DRLK.S.C12.Tx + PICS: DRLK.S.F11 && DRLK.S.C12.Rsp && DRLK.S.C12.Tx verification: | ./chip-tool doorlock get-holiday-schedule 15 1 1 Verify " DUT sends INVALID_COMMAND response" on the TH(Chip-tool) Log: @@ -148,7 +153,7 @@ tests: "TH sends Get Holiday Schedule Command to DUT with the HolidayIndex as 10 (value is in the the range of step 1 but Holiday Schedule entry not available)" - PICS: DRLK.S.F04 && DRLK.S.C12.Rsp && DRLK.S.C12.Tx + PICS: DRLK.S.F11 && DRLK.S.C12.Rsp && DRLK.S.C12.Tx verification: | ./chip-tool doorlock get-holiday-schedule 10 1 1 Verify " DUT sends a NOT_FOUND status" on the TH(Chip-tool) Log: @@ -164,7 +169,7 @@ tests: - label: "TH send Clear Holiday Schedule Command to DUT with HolidayIndex as 1" - PICS: DRLK.S.F04 && DRLK.S.C13.Rsp + PICS: DRLK.S.F11 && DRLK.S.C13.Rsp verification: | ./chip-tool doorlock clear-holiday-schedule 1 1 1 Verify " DUT sends SUCCESS response" on the TH(Chip-tool) Log: @@ -186,7 +191,7 @@ tests: - label: "TH sends Get Holiday Schedule Command to DUT with HolidayIndex as 1." - PICS: DRLK.S.F04 && DRLK.S.C12.Rsp && DRLK.S.C12.Tx + PICS: DRLK.S.F11 && DRLK.S.C12.Rsp && DRLK.S.C12.Tx verification: | ./chip-tool doorlock get-holiday-schedule 1 1 1 Verify " DUT sends a NOT_FOUND status" on the TH(Chip-tool) Log: diff --git a/src/app/tests/suites/certification/Test_TC_IDM_2_2.yaml b/src/app/tests/suites/certification/Test_TC_IDM_2_2.yaml index f5dedc2c4d6f11..398e1590e5bbaf 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_2_2.yaml @@ -1197,7 +1197,8 @@ tests: from the DUT." verification: | In case of chip tool, here is an example command to use - sudo ./chip-tool any read-all 1 0xFFFF --timeout 50 - Verify on TH , DUT is responds right attributes and events for above command + ./chip-tool any read-all 0xFFFFFFFF,0xFFFFFFFF 0xFFFFFFFF 0xFFFFFFFF 1 0xFFFF,0xFFFF + + on TH verify that DUT sends back data of all attributes and events that the TH has access to disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_IDM_3_1.yaml b/src/app/tests/suites/certification/Test_TC_IDM_3_1.yaml index 8109e78a529115..2252e4fa8d01bb 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_3_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_3_1.yaml @@ -24,11 +24,16 @@ config: endpoint: 0 tests: + - label: "Note" + verification: | + Chip-tool command used below are an example to verify the DUT as client test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + disabled: true + - label: "DUT sends the WriteRequestMessage to the TH to modify one attribute data" verification: | - In case of chip tool, here is an example command to use + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) sudo ./chip-tool levelcontrol write on-level 2 1 1 @@ -62,7 +67,7 @@ tests: [1655795552.552647][7331:7331] CHIP:DMG: InteractionModelRevision = 1 [1655795552.552686][7331:7331] CHIP:DMG: }, - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs,, verify that TH all-clusters-app sent success response [1657883782.721742][2796:2801] CHIP:DMG: WriteResponseMessage = [1657883782.721783][2796:2801] CHIP:DMG: { [1657883782.721819][2796:2801] CHIP:DMG: AttributeStatusIBs = @@ -112,7 +117,7 @@ tests: [1657883808.063295][2457:2457] CHIP:DMG: }, [1657883808.063369][2457:2457] CHIP:DMG: IM RH moving to [GeneratingReports] - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs,, verify that TH all-clusters-app sent success response [1655795604.755214][6880:6885] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0008 Attribute 0x0000_0011 DataVersion: 737039636 [1655795604.755363][6880:6885] CHIP:TOO: on level: 2 [1655795604.755460][6880:6885] CHIP:EM: Sending Standalone Ack for MessageCounter:83198098 on exchange 53763i @@ -127,10 +132,11 @@ tests: disabled: true - label: - "[Optional] DUT sends the WriteRequestMessage to the TH to write an - attribute of data type bool." + "DUT sends the WriteRequestMessage to the TH to write an attribute of + data type bool." + PICS: MCORE.IDM.C.WriteRequest.Attribute.DataType_Bool verification: | - In case of chip tool, here is an example command to use + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) ./chip-tool basic write local-config-disabled 1 1 0 @@ -166,7 +172,7 @@ tests: - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent success response [1657883938.394965][2822:2827] CHIP:DMG: WriteResponseMessage = [1657883938.394995][2822:2827] CHIP:DMG: { @@ -218,23 +224,21 @@ tests: [1657884119.523280][2748:2748] CHIP:DMG: }, - - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent success response [1655795843.336042][6902:6907] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0010 DataVersion: 1263909562 [1655795843.336093][6902:6907] CHIP:TOO: LocalConfigDisabled: TRUE [1655795843.336251][6902:6907] CHIP:EM: Sending Standalone Ack for MessageCounter:108030495 on exchange 43207i disabled: true - label: - "[Optional] DUT sends the WriteRequestMessage to the TH to write an - attribute of data type string." + "DUT sends the WriteRequestMessage to the TH to write an attribute of + data type string." + PICS: MCORE.IDM.C.WriteRequest.Attribute.DataType_String verification: | - In case of chip tool, here is an example command to use - + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) ./chip-tool basic write node-label node 1 0 - verify on TH(reference app) receives the right write Request Message for the data sent in the above command [1655796035.022296][7331:7331] CHIP:EM: Handling via exchange: 64908r, Delegate: 0xaaaad9aed418 @@ -265,8 +269,7 @@ tests: [1655796035.023656][7331:7331] CHIP:DMG: }, [1655796035.023791][7331:7331] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_0028 e=0 p=m [1655796035.023851][7331:7331] CHIP:DMG: AccessControl: allowed - - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent success response [1657884155.221193][2865:2870] CHIP:DMG: WriteResponseMessage = [1657884155.221246][2865:2870] CHIP:DMG: { [1657884155.221292][2865:2870] CHIP:DMG: AttributeStatusIBs = @@ -315,8 +318,7 @@ tests: [1657884173.739288][2748:2748] CHIP:DMG: }, - - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent success response [1655796082.079468][6918:6923] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0005 DataVersion: 1263909563 [1655796082.079509][6918:6923] CHIP:TOO: NodeLabel: node @@ -324,11 +326,11 @@ tests: disabled: true - label: - "[Optional] DUT sends the WriteRequestMessage to the TH to write an - attribute of data type unsigned integer." + "DUT sends the WriteRequestMessage to the TH to write an attribute of + data type unsigned integer." + PICS: MCORE.IDM.C.WriteRequest.Attribute.DataType_UnsignedInteger verification: | - In case of chip tool, here is an example command to use - + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) ./chip-tool any write-by-id 0x0008 0x0010 1 1 1 @@ -362,7 +364,8 @@ tests: [1655796141.168253][7331:7331] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_0008 e=1 p=o [1655796141.168313][7331:7331] CHIP:DMG: AccessControl: allowed - On DUT as a client side, verify that TH all-clusters-app sent success response + + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent success response [1657884204.951658][2878:2883] CHIP:DMG: WriteResponseMessage = [1657884204.951700][2878:2883] CHIP:DMG: { [1657884204.951736][2878:2883] CHIP:DMG: AttributeStatusIBs = @@ -413,53 +416,58 @@ tests: [1657884227.860339][2748:2748] CHIP:DMG: }, [1657884227.860413][2748:2748] CHIP:DMG: IM RH moving to [GeneratingReports] - - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent success response [1655796192.032715][6931:6936] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0008 Attribute 0x0000_0010 DataVersion: 737039637 [1655796192.032807][6931:6936] CHIP:TOO: on off transition time: 1 [1655796192.032908][6931:6936] CHIP:EM: Sending Standalone Ack for MessageCounter:249349258 on exchange 7433i disabled: true - label: - "[Optional] DUT sends the WriteRequestMessage to the TH to write an - attribute of data type signed integer." + "DUT sends the WriteRequestMessage to the TH to write an attribute of + data type signed integer." + PICS: MCORE.IDM.C.WriteRequest.Attribute.DataType_SignedInteger verification: | DUT implementation required to verify write an attribute of data type signed integer. disabled: true - label: - "[Optional] DUT sends the WriteRequestMessage to the TH to write an - attribute of data type floating point." + "DUT sends the WriteRequestMessage to the TH to write an attribute of + data type floating point." + PICS: MCORE.IDM.C.WriteRequest.Attribute.DataType_FloatingPoint verification: | DUT implementation required to verify write an attribute of data type float disabled: true - label: - "[Optional] DUT sends the WriteRequestMessage to the TH to write an - attribute of data type Octet String." + "DUT sends the WriteRequestMessage to the TH to write an attribute of + data type Octet String." + PICS: MCORE.IDM.C.WriteRequest.Attribute.DataType_OctetString verification: | DUT implementation required to verify write an attribute of data type Octet String disabled: true - label: - "[Optional] DUT sends the WriteRequestMessage to the TH to write an - attribute of data type Struct." + "DUT sends the WriteRequestMessage to the TH to write an attribute of + data type Struct." + PICS: MCORE.IDM.C.WriteRequest.Attribute.DataType_Struct verification: | DUT implementation required to verify write an attribute ofdata type Struct disabled: true - label: - "[Optional] DUT sends the WriteRequestMessage to the TH to write an - attribute of data type List." + "DUT sends the WriteRequestMessage to the TH to write an attribute of + data type List." + PICS: MCORE.IDM.C.WriteRequest.Attribute.DataType_List verification: | DUT implementation required to verify write an attribute of data type List disabled: true - label: - "[Optional] DUT sends the WriteRequestMessage to the TH to write an - attribute of data type enum." + "DUT sends the WriteRequestMessage to the TH to write an attribute of + data type enum." + PICS: MCORE.IDM.C.WriteRequest.Attribute.DataType_Enum verification: | - In case of chip tool, here is an example command to use + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) ./chip-tool any write-by-id 0x0204 0 1 1 1 @@ -494,7 +502,7 @@ tests: [1655796297.609342][7331:7331] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_0204 e=1 p=o [1655796297.609403][7331:7331] CHIP:DMG: AccessControl: allowed - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent success response [1657884258.383116][2892:2897] CHIP:DMG: WriteResponseMessage = [1657884258.383157][2892:2897] CHIP:DMG: { [1657884258.383192][2892:2897] CHIP:DMG: AttributeStatusIBs = @@ -530,19 +538,18 @@ tests: [1657884282.303778][2898:2903] CHIP:TOO: temperature display mode: 1 [1657884282.303862][2898:2903] CHIP:EM: Sending Standalone Ack for MessageCounter:147756485 on exchange 42871i - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs,, verify that TH all-clusters-app sent success response [1655796341.132655][6946:6951] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0204 Attribute 0x0000_0000 DataVersion: 3165945391 [1655796341.132864][6946:6951] CHIP:TOO: temperature display mode: 1 [1655796341.132973][6946:6951] CHIP:EM: Sending Standalone Ack for MessageCounter:245498041 on exchange 51992i disabled: true - label: - "[Optional] DUT sends the WriteRequestMessage to the TH to write an - attribute of data type bitmap." + "DUT sends the WriteRequestMessage to the TH to write an attribute of + data type bitmap." + PICS: MCORE.IDM.C.WriteRequest.Attribute.DataType_Bitmap verification: | - In case of chip tool, here is an example command to use - - + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) ./chip-tool colorcontrol write-by-id 0x000f 1 1 1 @@ -577,7 +584,7 @@ tests: [1655796429.698446][7331:7331] CHIP:DMG: AccessControl: allowed - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent success response [1657884309.994598][2907:2912] CHIP:DMG: WriteResponseMessage = [1657884309.994627][2907:2912] CHIP:DMG: { @@ -630,8 +637,7 @@ tests: [1657884334.614053][2748:2748] CHIP:DMG: }, [1657884334.614128][2748:2748] CHIP:DMG: IM RH moving to [GeneratingReports] - - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent success response [1655796493.233673][6961:6966] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0300 Attribute 0x0000_000F DataVersion: 2788050502 [1655796493.233761][6961:6966] CHIP:TOO: Options: 1 [1655796493.233865][6961:6966] CHIP:EM: Sending Standalone Ack for MessageCounter:185730221 on exchange 37136i @@ -639,7 +645,8 @@ tests: - label: "DUT sends a WriteRequestMessage to the TH with a large list of - attribute data which has to be sent in multiple messages." + attribute data, which is larger than 1 MTU(1280 bytes), that has to be + sent in multiple messages." verification: | DUT implementation required to verify write an attribute which is is larger than 1 MTU(1280 bytes) Here is an example command to verify the write functionality. User must choose an attribute which has large list of attribute data. @@ -650,7 +657,7 @@ tests: "DUT sends the WriteRequestMessage to the TH to write one attribute on a given cluster and endpoint. Repeat the above steps 3 times." verification: | - In case of chip tool, here is an example command to use + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) ./chip-tool any write-by-id 0x0204 0 1 1 1 @@ -685,7 +692,7 @@ tests: [1655796724.512195][7331:7331] CHIP:DMG: }, [1655796724.512344][7331:7331] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_0204 e=1 p=o - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent success response [1657884369.932192][2923:2928] CHIP:DMG: WriteResponseMessage = [1657884369.932226][2923:2928] CHIP:DMG: { [1657884369.932255][2923:2928] CHIP:DMG: AttributeStatusIBs = @@ -737,8 +744,7 @@ tests: [1657884399.502907][2748:2748] CHIP:DMG: }, [1657884399.502989][2748:2748] CHIP:DMG: IM RH moving to [GeneratingReports] - - On DUT as a client side, verify that TH all-clusters-app sent success response + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent success response [1655796786.513406][6976:6981] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0204 Attribute 0x0000_0000 DataVersion: 3165945392 [1655796786.513496][6976:6981] CHIP:TOO: temperature display mode: 1 [1655796786.513593][6976:6981] CHIP:EM: Sending Standalone Ack for MessageCounter:190446058 on exchange 28240i @@ -749,9 +755,9 @@ tests: disabled: true - label: - "[Optional] DUT sends a ReadRequest message to the TH to read any - attribute on two clusters. TH returns with a report data action with - the attribute values and the dataversions of the clusters. DUT sends a + "DUT sends a ReadRequest message to the TH to read any attribute on + two clusters. TH returns with a report data action with the attribute + values and the dataversions of the clusters. DUT sends a WriteRequestMessage to the DUT to both the clusters with the appropriate dataversions(received in the previous step) to modify the value of an attribute" diff --git a/src/app/tests/suites/certification/Test_TC_IDM_4_1.yaml b/src/app/tests/suites/certification/Test_TC_IDM_4_1.yaml index f22a140b6cf067..a27bf4593c59d0 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_4_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_4_1.yaml @@ -26,11 +26,26 @@ config: endpoint: 0 tests: + - label: "Note" + verification: | + Please use Interactive mode to Verify subscription test cases + Here the command to enter interactive mode:-- ./chip-tool interactive start + disabled: true + + - label: "Note" + verification: | + Chip-tool command used below are an example to verify the DUT as client test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + disabled: true + - label: "DUT sends a subscription request message to the target node/reference device for a single attribute of any data type supported." + PICS: MCORE.IDM.C.SubscribeRequest verification: | - In the case of chip tool as a client, here is an example command the client can subscribe to the TH + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) + + Please use Interactive mode to Verify subscription test cases + Here the command to enter interactive mode:-- ./chip-tool interactive start onoff subscribe on-off 10 80 1 1 @@ -60,7 +75,7 @@ tests: [1657446108.598559][11525:11525] CHIP:DMG: IM RH moving to [GeneratingReports] - On DUT as a client side, verify that TH all-clusters-app sent Subscription report with unic subscriptionID + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent Subscription report with unic subscriptionID [1657884469.617473][2938:2943] CHIP:DMG: ReportDataMessage = [1657884469.617508][2938:2943] CHIP:DMG: { [1657884469.617538][2938:2943] CHIP:DMG: SubscriptionId = 0x2d030a2b, @@ -109,8 +124,12 @@ tests: - label: "DUT sends the subscription request message to TH TH sends a report data DUT sends the status response back to TH" + PICS: MCORE.IDM.C.SubscribeRequest verification: | - In the case of chip tool as a client, here is an example command the client can subscribe to the TH + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) + + Please use Interactive mode to Verify subscription test cases + Here the command to enter interactive mode:-- ./chip-tool interactive start onoff subscribe on-off 10 80 1 1 @@ -126,7 +145,8 @@ tests: [1657446108.604672][11525:11525] CHIP:IM: Received status response, status is 0x00 (SUCCESS) [1657446108.604755][11525:11525] CHIP:DMG: Refresh Subscribe Sync Timer with max 80 seconds - On DUT as a client side, verify that TH all-clusters-app sent Subscription report with unic subscriptionID + + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent Subscription report with unic subscriptionID [1657884569.751004][2938:2943] CHIP:DMG: ReportDataMessage = [1657884569.751034][2938:2943] CHIP:DMG: { [1657884569.751059][2938:2943] CHIP:DMG: SubscriptionId = 0x47cd6fdb, @@ -177,8 +197,13 @@ tests: an attribute of data type boolean. Modify that attribute on the TH. TH should send the modified data to the DUT. Modify the attribute multiple times (3 times)." + PICS: MCORE.IDM.C.SubscribeRequest.Attribute.DataType_Bool verification: | - In the case of chip tool as a client, here is an example command the client can subscribe to the TH + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) + + + Please use Interactive mode to Verify subscription test cases + Here the command to enter interactive mode:-- ./chip-tool interactive start basic subscribe local-config-disabled 10 100 1 0 @@ -206,7 +231,8 @@ tests: - On DUT as a client side, verify that TH all-clusters-app sent Subscription report with unic subscriptionID + + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent Subscription report with unic subscriptionID [1657884643.152038][2938:2943] CHIP:DMG: ReportDataMessage = [1657884643.152141][2938:2943] CHIP:DMG: { [1657884643.152206][2938:2943] CHIP:DMG: SubscriptionId = 0x2e0592e3, @@ -257,8 +283,12 @@ tests: an attribute of data type string. Modify that attribute on the TH. TH should send the modified data to the DUT. Modify the attribute multiple times (3 times)." + PICS: MCORE.IDM.C.SubscribeRequest.Attribute.DataType_String verification: | - In the case of chip tool as a client, here is an example command the client can subscribe to the TH + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) + + Please use Interactive mode to Verify subscription test cases + Here the command to enter interactive mode:-- ./chip-tool interactive start basic subscribe node-label 30 200 1 0 @@ -290,7 +320,8 @@ tests: [1657446721.226711][11525:11525] CHIP:DMG: OnReportConfirm: NumReports = 0 [1657446721.226773][11525:11525] CHIP:DMG: IM RH moving to [GeneratingReports] - On DUT as a client side, verify that TH all-clusters-app sent Subscription report with unic subscriptionID + + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent Subscription report with unic subscriptionID [1657884902.175205][2938:2943] CHIP:DMG: ReportDataMessage = [1657884902.175255][2938:2943] CHIP:DMG: { [1657884902.175299][2938:2943] CHIP:DMG: SubscriptionId = 0x6a6457a1, @@ -327,9 +358,12 @@ tests: an attribute of data type unsigned integer. Modify that attribute on the TH. TH should send the modified data to the DUT. Modify the attribute multiple times (3 times)." + PICS: MCORE.IDM.C.SubscribeRequest.Attribute.DataType_UnsignedInteger verification: | - In the case of chip tool as a client, here is an example command the client can subscribe to the TH + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) + Please use Interactive mode to Verify subscription test cases + Here the command to enter interactive mode:-- ./chip-tool interactive start any subscribe-by-id 0x0008 0x0010 10 100 1 1 On TH (On the reference app) Verify if DUT is responding with the below status response for the above command @@ -404,7 +438,8 @@ tests: [1657448453.234577][11525:11525] CHIP:DMG: OnReportConfirm: NumReports = 0 - On DUT as a client side, verify that TH all-clusters-app sent Subscription report with unic subscriptionID + + If the DUT has to provision to verify the logs, , verify that TH all-clusters-app sent Subscription report with unic subscriptionID [1657884955.073466][2938:2943] CHIP:DMG: ReportDataMessage = [1657884955.073516][2938:2943] CHIP:DMG: { [1657884955.073562][2938:2943] CHIP:DMG: SubscriptionId = 0x6cee9660, @@ -444,6 +479,7 @@ tests: an attribute of data type signed integer. Modify that attribute on the TH. TH should send the modified data to the DUT. Modify the attribute multiple times (3 times)" + PICS: MCORE.IDM.C.SubscribeRequest.Attribute.DataType_Integer verification: | DUT implementation required to verify subscribe an attribute of data type signed integer disabled: true @@ -453,6 +489,7 @@ tests: an attribute of data type Floating Point. Modify that attribute on the TH. TH should send the modified data to the DUT. Modify the attribute multiple times (3 times)" + PICS: MCORE.IDM.C.SubscribeRequest.Attribute.DataType_FloatingPoint verification: | DUT implementation required to verify subscribe an attribute of data type floating point disabled: true @@ -462,6 +499,7 @@ tests: an attribute of data type list. Modify that attribute on the TH. TH should send the modified data to the DUT. Modify the attribute multiple times (3 times)" + PICS: MCORE.IDM.C.SubscribeRequest.Attribute.DataType_List verification: | DUT implementation required to verify subscribe and list an attribute of data type list disabled: true @@ -472,6 +510,7 @@ tests: of the maximum interval. After the maximum interval, TH sends a report data with the subscription id created during the subscription activation." + PICS: MCORE.IDM.C.SubscribeRequest verification: | This is not testable in normal scenario, and needs to be tested as part of Unit test. disabled: true @@ -479,8 +518,12 @@ tests: - label: "DUT sends a subscription request message to the target node/reference device for multiple attributes(3 attributes)." + PICS: MCORE.IDM.C.SubscribeRequest.MultipleAttributes verification: | - In the case of chip tool as a client, here is an example command the client can subscribe to the TH + Product maker needs to provide instructions for how to trigger the command on the DUT. For comparison, the DUT behavior for this test step can be simulated using chip-tool (when DUT is a commissioner/Client) + + Please use Interactive mode to Verify subscription test cases + Here the command to enter interactive mode:-- ./chip-tool interactive start any subscribe-by-id "6,8,3" "0,1,0" 10 100 "1" "1,1,1" @@ -534,7 +577,8 @@ tests: [1657449168.674365][11525:11525] CHIP:DMG: Refresh Subscribe Sync Timer with max 100 seconds - On DUT as a client side, verify that TH all-clusters-app sent Subscription report with unic subscriptionID + + If the DUT has to provision to verify the logs, verify that TH all-clusters-app sent Subscription report with unic subscriptionID 884990.165955][2938:2943] CHIP:DMG: }, [1657884990.166021][2938:2943] CHIP:DMG: [1657884990.166072][2938:2943] CHIP:DMG: ], diff --git a/src/app/tests/suites/certification/Test_TC_MOD_2_1.yaml b/src/app/tests/suites/certification/Test_TC_MOD_2_1.yaml index 28d371377c6821..a4fb3db49bba06 100644 --- a/src/app/tests/suites/certification/Test_TC_MOD_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_MOD_2_1.yaml @@ -70,7 +70,7 @@ tests: verification: | ./chip-tool modeselect read current-mode 1 1 - Verify on TH(chip-tool), current modes provides a list of modes + Verify on TH(chip-tool), current modes provides a mode Record for usage in steps 3. [1649678800.298128][10854:10861] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0050 Attribute 0x0000_0003 DataVersion: 4277065073 @@ -98,7 +98,7 @@ tests: verification: | ./chip-tool modeselect read current-mode 1 1 - Verify on TH(chip-tool), current modes provides a list ofmodes + Verify on TH(chip-tool), current modes provides integer provided in step 3a, not the integer from step 2 [1649678800.298128][10854:10861] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0050 Attribute 0x0000_0003 DataVersion: 4277065073 diff --git a/src/app/tests/suites/certification/Test_TC_MOD_3_1.yaml b/src/app/tests/suites/certification/Test_TC_MOD_3_1.yaml index f94f8507d782c5..3e4d2cc36f7f1f 100644 --- a/src/app/tests/suites/certification/Test_TC_MOD_3_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_MOD_3_1.yaml @@ -29,7 +29,7 @@ tests: verification: | ./chip-tool modeselect read on-mode 1 1 - on TH(chip-tool),Verify that the DUT response The attribute is nullable, and null is also acceptable + on TH(chip-tool),Verify that the DUT response is an integer. Record this value for usage in steps 2b. [1649678983.679893][10871:10876] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0050 Attribute 0x0000_0005 DataVersion: 4277065073 [1649678983.680002][10871:10876] CHIP:TOO: OnMode: 0 diff --git a/src/app/tests/suites/certification/Test_TC_MOD_3_3.yaml b/src/app/tests/suites/certification/Test_TC_MOD_3_3.yaml index 1dec78d5a0c0c3..ec53ad0c219e1b 100644 --- a/src/app/tests/suites/certification/Test_TC_MOD_3_3.yaml +++ b/src/app/tests/suites/certification/Test_TC_MOD_3_3.yaml @@ -24,6 +24,29 @@ config: endpoint: 0 tests: + - label: "Pre-conditions:" + verification: | + This test case is verified after the device is provisioned. Pls provision device first, Pass appropriate nodeID in the below command + disabled: true + + - label: "Note" + verification: | + 1.To run this test case build the OTA Provider app in nRF connectedhomeip Docker . [ + https://github.com/project-chip/connectedhomeip/tree/master/examples/ota-provider-app/linux + + 2. Build all-cluster-app in docker + + west build -b nrf52840dk_nrf52840 -- -DCONF_FILE=prj_dfu.conf -DCONFIG_CHIP_LIB_SHELL=y + + + 3.Flash + west flash --erase + + 4.OTA Image needs to build on docker + + west build -b nrf52840dk_nrf52840 -d build2 -- -DCONFIG_CHIP_DEVICE_SOFTWARE_VERSION=2 -DCONF_FILE=prj_dfu.conf -DCONFIG_CHIP_LIB_SHELL=y + disabled: true + - label: "TH reads the StartUpMode attribute from the DUT" PICS: MOD.S.A0004 verification: | diff --git a/src/app/tests/suites/certification/Test_TC_MOD_3_4.yaml b/src/app/tests/suites/certification/Test_TC_MOD_3_4.yaml index 56dc6c9fd5aafa..5a9118852691de 100644 --- a/src/app/tests/suites/certification/Test_TC_MOD_3_4.yaml +++ b/src/app/tests/suites/certification/Test_TC_MOD_3_4.yaml @@ -26,6 +26,25 @@ config: endpoint: 0 tests: + - label: "Pre-conditions:" + verification: | + This test case is verified after the device is provisioned. Pls provision device first, Pass appropriate nodeID in the below command + disabled: true + + - label: "Note" + verification: | + To Execute the TC-MOD-3.4 test case using reboot in raspi device we followed the below suggested way: + + To run a reboot test case on raspi, run the app with --KVS flag with a file in local directory and pass that file to the command to launch the app. Steps + + + step-1: create a file using touch command , something like touch mytest.txt + step-2: chmod 777 mytest.txt + step-3: launch the app sudo ./out/all-clusters-app/chip-all-clusters-app --KVS ./mytest.txt + + if you launch the app with the above commands and provision the app, even when you reboot the app with 'sudo reboot' , next time you launch the app with 'sudo ./out/all-clusters-app/chip-all-clusters-app --KVS ./mytest.txt' , you can run read/write attribs and commands without reprovisioning the device. + disabled: true + - label: "TH reads the StartUpMode attribute from the DUT" PICS: MOD.S.A0004 verification: | diff --git a/src/app/tests/suites/certification/Test_TC_OCC_3_2.yaml b/src/app/tests/suites/certification/Test_TC_OCC_3_2.yaml deleted file mode 100644 index 6dd4e4dc92422d..00000000000000 --- a/src/app/tests/suites/certification/Test_TC_OCC_3_2.yaml +++ /dev/null @@ -1,88 +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: 3.2.6. [TC-OCC-3.2] Primary functionality with client as DUT - -PICS: - - OCC.C - -config: - nodeId: 0x12344321 - cluster: "Basic" - endpoint: 0 - -tests: - - label: "Commission TH to DUT" - verification: | - verification step to be updated. - disabled: true - - - label: "DUT reads Occupancy attribute from TH" - PICS: OCC.C.A0000 - verification: | - ./chip-tool occupancysensing read occupancy 1 1 - - verify On TH(Reference app) receives the right Read Request Message for the data sent in the above command - - [1657906910.080564][2361:2361] CHIP:IM: Received Read request - [1657906910.080689][2361:2361] CHIP:DMG: ReadRequestMessage = - [1657906910.080758][2361:2361] CHIP:DMG: { - [1657906910.080799][2361:2361] CHIP:DMG: AttributePathIBs = - [1657906910.080846][2361:2361] CHIP:DMG: [ - [1657906910.080907][2361:2361] CHIP:DMG: AttributePathIB = - [1657906910.080965][2361:2361] CHIP:DMG: { - [1657906910.081017][2361:2361] CHIP:DMG: Endpoint = 0x1, - [1657906910.081092][2361:2361] CHIP:DMG: Cluster = 0x406, - [1657906910.081152][2361:2361] CHIP:DMG: Attribute = 0x0000_0000, - [1657906910.081206][2361:2361] CHIP:DMG: } - [1657906910.081279][2361:2361] CHIP:DMG: - [1657906910.081331][2361:2361] CHIP:DMG: ], - [1657906910.081398][2361:2361] CHIP:DMG: - [1657906910.081449][2361:2361] CHIP:DMG: isFabricFiltered = true, - [1657906910.081496][2361:2361] CHIP:DMG: InteractionModelRevision = 1 - [1657906910.081538][2361:2361] CHIP:DMG: }, - disabled: true - - - label: "Operate on TH to change the occupancy status" - PICS: OCC.M.OccupancyChange - verification: | - Logs will be device specific[Manual operation required] - disabled: true - - - label: "after a few seconds, DUT reads Occupancy attribute from TH" - PICS: OCC.C.A0000 - verification: | - ./chip-tool occupancysensing read occupancy 1 1 - - verify On TH(Reference app) receives the right Read Request Message for the data sent in the above command - - [1657906923.314549][2361:2361] CHIP:IM: Received Read request - [1657906923.314735][2361:2361] CHIP:DMG: ReadRequestMessage = - [1657906923.314792][2361:2361] CHIP:DMG: { - [1657906923.314838][2361:2361] CHIP:DMG: AttributePathIBs = - [1657906923.314899][2361:2361] CHIP:DMG: [ - [1657906923.314949][2361:2361] CHIP:DMG: AttributePathIB = - [1657906923.315006][2361:2361] CHIP:DMG: { - [1657906923.315064][2361:2361] CHIP:DMG: Endpoint = 0x1, - [1657906923.315132][2361:2361] CHIP:DMG: Cluster = 0x406, - [1657906923.315199][2361:2361] CHIP:DMG: Attribute = 0x0000_0000, - [1657906923.315258][2361:2361] CHIP:DMG: } - [1657906923.315322][2361:2361] CHIP:DMG: - [1657906923.315380][2361:2361] CHIP:DMG: ], - [1657906923.315438][2361:2361] CHIP:DMG: - [1657906923.315497][2361:2361] CHIP:DMG: isFabricFiltered = true, - [1657906923.315560][2361:2361] CHIP:DMG: InteractionModelRevision = 1 - [1657906923.315609][2361:2361] CHIP:DMG: }, - disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_OO_3_1.yaml b/src/app/tests/suites/certification/Test_TC_OO_3_1.yaml index d4affdb99c5eb4..da18a036e8512d 100644 --- a/src/app/tests/suites/certification/Test_TC_OO_3_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_OO_3_1.yaml @@ -81,7 +81,7 @@ tests: ./chip-tool onoff read on-time 1 1 - verify the " on-time-control response" on the TH (all-cluster-app) log: + verify the " on-time response" on the TH (all-cluster-app) log: [...] [1650535552.255428][3678:3678] CHIP:IM: Received Read request diff --git a/src/app/tests/suites/certification/Test_TC_PCC_3_1.yaml b/src/app/tests/suites/certification/Test_TC_PCC_3_1.yaml index 1c3774ba792444..7cf72c58584f9b 100644 --- a/src/app/tests/suites/certification/Test_TC_PCC_3_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_PCC_3_1.yaml @@ -28,6 +28,11 @@ config: 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: "DUT reads all supported mandatory attributes from TH one at a time in a manufacturer specific order" @@ -58,7 +63,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read max-speed 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651148440.471321][2336:2336] CHIP:IM: Received Read request [1651148440.471389][2336:2336] CHIP:DMG: ReadRequestMessage = @@ -82,7 +87,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read max-flow 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651148472.518933][2336:2336] CHIP:IM: Received Read request [1651148472.518993][2336:2336] CHIP:DMG: ReadRequestMessage = @@ -106,7 +111,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read effective-operation-mode 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651570515.206834][9246:9246] CHIP:IM: Received Read request [1651570515.206917][9246:9246] CHIP:DMG: ReadRequestMessage = @@ -128,7 +133,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read effective-control-mode 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651570975.559213][9246:9246] CHIP:IM: Received Read request [1651570975.559268][9246:9246] CHIP:DMG: ReadRequestMessage = @@ -147,7 +152,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read capacity 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651571009.295069][9246:9246] CHIP:IM: Received Read request [1651571009.295158][9246:9246] CHIP:DMG: ReadRequestMessage = @@ -166,7 +171,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read operation-mode 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651571334.617100][9337:9337] CHIP:IM: Received Read request [1651571334.617155][9337:9337] CHIP:DMG: ReadRequestMessage = @@ -192,7 +197,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read min-const-pressure 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651148507.711384][2336:2336] CHIP:IM: Received Read request [1651148507.711452][2336:2336] CHIP:DMG: ReadRequestMessage = @@ -216,7 +221,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read max-const-pressure 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651148537.336390][2336:2336] CHIP:IM: Received Read request [1651148537.336445][2336:2336] CHIP:DMG: ReadRequestMessage = @@ -240,7 +245,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read min-comp-pressure 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651148566.361843][2336:2336] CHIP:IM: Received Read request [1651148566.361897][2336:2336] CHIP:DMG: ReadRequestMessage = @@ -262,7 +267,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read max-comp-pressure 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651148595.417817][2336:2336] CHIP:IM: Received Read request [1651148595.417901][2336:2336] CHIP:DMG: ReadRequestMessage = @@ -286,7 +291,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read min-const-speed 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651148626.823098][2336:2336] CHIP:IM: Received Read request [1651148626.823201][2336:2336] CHIP:DMG: ReadRequestMessage = @@ -308,7 +313,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read max-const-speed 1 1 - Verify in TH all-clusters-app log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651564124.345958][8748:8748] CHIP:IM: Received Read request [1651564124.346033][8748:8748] CHIP:DMG: ReadRequestMessage = @@ -331,7 +336,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read min-const-flow 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651564163.319315][8748:8748] CHIP:IM: Received Read request [1651564163.319399][8748:8748] CHIP:DMG: ReadRequestMessage = @@ -355,7 +360,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read min-const-flow 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651564163.319315][8748:8748] CHIP:IM: Received Read request [1651564163.319399][8748:8748] CHIP:DMG: ReadRequestMessage = @@ -378,7 +383,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read max-const-flow 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651564281.857728][8748:8748] CHIP:IM: Received Read request [1651564281.857784][8748:8748] CHIP:DMG: ReadRequestMessage = @@ -400,7 +405,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read min-const-temp 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651564317.488333][8748:8748] CHIP:IM: Received Read request [1651564317.488417][8748:8748] CHIP:DMG: ReadRequestMessage = @@ -422,7 +427,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read max-const-temp 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651564350.267434][8748:8748] CHIP:IM: Received Read request [1651564350.267489][8748:8748] CHIP:DMG: ReadRequestMessage = @@ -444,7 +449,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read pump-status 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651564415.272861][8748:8748] CHIP:IM: Received Read request [1651564415.272946][8748:8748] CHIP:DMG: ReadRequestMessage = @@ -466,7 +471,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read speed 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651571041.252491][9246:9246] CHIP:IM: Received Read request [1651571041.252548][9246:9246] CHIP:DMG: ReadRequestMessage = @@ -488,7 +493,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read lifetime-running-hours 1 1 - Verify in TH all-clusters-app log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651571194.810592][9337:9337] CHIP:IM: Received Read request [1651571194.810647][9337:9337] CHIP:DMG: ReadRequestMessage = @@ -510,7 +515,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read power 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651571264.121840][9337:9337] CHIP:IM: Received Read request [1651571264.121896][9337:9337] CHIP:DMG: ReadRequestMessage = @@ -532,7 +537,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read lifetime-energy-consumed 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651571293.017448][9337:9337] CHIP:IM: Received Read request [1651571293.017534][9337:9337] CHIP:DMG: ReadRequestMessage = @@ -554,7 +559,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read control-mode 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651571369.365807][9337:9337] CHIP:IM: Received Read request [1651571369.365907][9337:9337] CHIP:DMG: ReadRequestMessage = @@ -583,7 +588,7 @@ tests: ./chip-tool pumpconfigurationandcontrol write operation-mode 0 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the Write Request for the data sent in the above command [1652858465.008652][2107:2107] CHIP:IM: Received Write request [1652858465.008695][2107:2107] CHIP:DMG: IM WH moving to [Initialized] @@ -622,7 +627,7 @@ tests: ./chip-tool pumpconfigurationandcontrol write control-mode 0 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the Write Request for the data sent in the above command [1652858653.083434][2107:2107] CHIP:IM: Received Write request [1652858653.083469][2107:2107] CHIP:DMG: IM WH moving to [Initialized] @@ -655,7 +660,8 @@ tests: ./chip-tool pumpconfigurationandcontrol write lifetime-running-hours 1 1 1 - Verify in DUT as client side Log + + verify on TH all-cluster-app receives the Write Request for the data sent in the above command [1652858777.844427][2107:2107] CHIP:IM: Received Write request [1652858777.844450][2107:2107] CHIP:DMG: IM WH moving to [Initialized] @@ -688,7 +694,8 @@ tests: ./chip-tool pumpconfigurationandcontrol write lifetime-energy-consumed 1 1 1 - Verify in DUT as client side Log + + verify on TH all-cluster-app receives the Write Request for the data sent in the above command [1652858844.149759][2107:2107] CHIP:IM: Received Write request [1652858844.149801][2107:2107] CHIP:DMG: IM WH moving to [Initialized] @@ -730,36 +737,62 @@ tests: ./chip-tool pumpconfigurationandcontrol read attribute-list 1 1 - Verify in DUT as client side Log - [1654247307401] [91803:4011207] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0200 Attribute 0x0000_FFFB DataVersion: 3055704159 - [1654247307401] [91803:4011207] CHIP: [TOO] AttributeList: 12 entries - [1654247307401] [91803:4011207] CHIP: [TOO] [1]: 0 - [1654247307401] [91803:4011207] CHIP: [TOO] [2]: 1 - [1654247307401] [91803:4011207] CHIP: [TOO] [3]: 2 - [1654247307401] [91803:4011207] CHIP: [TOO] [4]: 17 - [1654247307401] [91803:4011207] CHIP: [TOO] [5]: 18 - [1654247307401] [91803:4011207] CHIP: [TOO] [6]: 19 - [1654247307401] [91803:4011207] CHIP: [TOO] [7]: 32 - [1654247307401] [91803:4011207] CHIP: [TOO] [8]: 65528 - [1654247307401] [91803:4011207] CHIP: [TOO] [9]: 65529 - [1654247307401] [91803:4011207] CHIP: [TOO] [10]: 65531 - [1654247307401] [91803:4011207] CHIP: [TOO] [11]: 65532 - [1654247307401] [91803:4011207] CHIP: [TOO] [12]: 65533 + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command + [1660745892.540246][3657:3657] CHIP:IM: Received Read request + [1660745892.540323][3657:3657] CHIP:DMG: ReadRequestMessage = + [1660745892.540346][3657:3657] CHIP:DMG: { + [1660745892.540364][3657:3657] CHIP:DMG: AttributePathIBs = + [1660745892.540401][3657:3657] CHIP:DMG: [ + [1660745892.540422][3657:3657] CHIP:DMG: AttributePathIB = + [1660745892.540452][3657:3657] CHIP:DMG: { + [1660745892.540487][3657:3657] CHIP:DMG: Endpoint = 0x1, + [1660745892.540517][3657:3657] CHIP:DMG: Cluster = 0x200, + [1660745892.540556][3657:3657] CHIP:DMG: Attribute = 0x0000_FFFB, + [1660745892.540582][3657:3657] CHIP:DMG: } + [1660745892.540616][3657:3657] CHIP:DMG: + [1660745892.540638][3657:3657] CHIP:DMG: ], + [1660745892.540673][3657:3657] CHIP:DMG: + [1660745892.540696][3657:3657] CHIP:DMG: isFabricFiltered = true, + [1660745892.540726][3657:3657] CHIP:DMG: InteractionModelRevision = 1 + [1660745892.540747][3657:3657] CHIP:DMG: }, + [1660745892.540821][3657:3657] CHIP:DMG: IM RH moving to [GeneratingReports] + [1660745892.540929][3657:3657] CHIP:DMG: Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0 + [1660745892.540954][3657:3657] CHIP:DMG: Cluster 200, Attribute fffb is dirty + [1660745892.540982][3657:3657] CHIP:DMG: Reading attribute: Cluster=0x0000_0200 Endpoint=1 AttributeId=0x0000_FFFB (expanded=0) ./chip-tool pumpconfigurationandcontrol read feature-map 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command - [1656478569086] [49565:5734437] CHIP: [TOO] Endpoint: 1 Cluster: 0x0000_0200 Attribute 0x0000_FFFC DataVersion: 1816685251 - [1656478569086] [49565:5734437] CHIP: [TOO] FeatureMap: 0 + [1660745929.334567][3657:3657] CHIP:IM: Received Read request + [1660745929.334641][3657:3657] CHIP:DMG: ReadRequestMessage = + [1660745929.334677][3657:3657] CHIP:DMG: { + [1660745929.334696][3657:3657] CHIP:DMG: AttributePathIBs = + [1660745929.334728][3657:3657] CHIP:DMG: [ + [1660745929.334750][3657:3657] CHIP:DMG: AttributePathIB = + [1660745929.334778][3657:3657] CHIP:DMG: { + [1660745929.334814][3657:3657] CHIP:DMG: Endpoint = 0x1, + [1660745929.334853][3657:3657] CHIP:DMG: Cluster = 0x200, + [1660745929.334884][3657:3657] CHIP:DMG: Attribute = 0x0000_FFFC, + [1660745929.334920][3657:3657] CHIP:DMG: } + [1660745929.334947][3657:3657] CHIP:DMG: + [1660745929.334978][3657:3657] CHIP:DMG: ], + [1660745929.335006][3657:3657] CHIP:DMG: + [1660745929.335037][3657:3657] CHIP:DMG: isFabricFiltered = true, + [1660745929.335059][3657:3657] CHIP:DMG: InteractionModelRevision = 1 + [1660745929.335079][3657:3657] CHIP:DMG: }, + [1660745929.335155][3657:3657] CHIP:DMG: IM RH moving to [GeneratingReports] + [1660745929.335256][3657:3657] CHIP:DMG: Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0 + [1660745929.335291][3657:3657] CHIP:DMG: Cluster 200, Attribute fffc is dirty + [1660745929.335311][3657:3657] CHIP:DMG: Reading attribute: Cluster=0x0000_0200 Endpoint=1 AttributeId=0x0000_FFFC (expanded=0) ./chip-tool pumpconfigurationandcontrol read max-pressure 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651148412.273866][2336:2336] CHIP:IM: Received Read request [1651148412.273922][2336:2336] CHIP:DMG: ReadRequestMessage = @@ -782,7 +815,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read max-speed 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651148440.471321][2336:2336] CHIP:IM: Received Read request [1651148440.471389][2336:2336] CHIP:DMG: ReadRequestMessage = @@ -806,7 +839,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read max-flow 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651148472.518933][2336:2336] CHIP:IM: Received Read request [1651148472.518993][2336:2336] CHIP:DMG: ReadRequestMessage = @@ -830,7 +863,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read effective-operation-mode 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651570515.206834][9246:9246] CHIP:IM: Received Read request @@ -853,7 +886,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read effective-control-mode 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651570975.559213][9246:9246] CHIP:IM: Received Read request [1651570975.559268][9246:9246] CHIP:DMG: ReadRequestMessage = @@ -872,7 +905,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read capacity 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651571009.295069][9246:9246] CHIP:IM: Received Read request [1651571009.295158][9246:9246] CHIP:DMG: ReadRequestMessage = @@ -891,7 +924,7 @@ tests: ./chip-tool pumpconfigurationandcontrol read operation-mode 1 1 - Verify in DUT as client side Log + verify on TH all-cluster-app receives the right ReadRequest for the data sent in the above command [1651571334.617100][9337:9337] CHIP:IM: Received Read request [1651571334.617155][9337:9337] CHIP:DMG: ReadRequestMessage = diff --git a/src/app/tests/suites/certification/Test_TC_SC_4_1.yaml b/src/app/tests/suites/certification/Test_TC_SC_4_1.yaml index 3888005a6771b2..e92cba67a2088d 100644 --- a/src/app/tests/suites/certification/Test_TC_SC_4_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_SC_4_1.yaml @@ -28,6 +28,7 @@ tests: "DUT is Commissioned and put in Commissioning Mode using Open Basic Commissioning Window command and starts advertising Commissionable Node Discovery service using DNS-SD" + PICS: CADMIN.S.C01.Rsp verification: | ./chip-tool administratorcommissioning open-basic-commissioning-window 200 1 0 --timedInteractionTimeoutMs 1000 @@ -76,6 +77,7 @@ tests: MCORE.SC.DT_KEY&& MCORE.SC.DN_KEY && MCORE.SC.RI_KEY && MCORE.SC.PH_KEY && MCORE.SC.PI_KEY verification: | + Run the below commands within the mentioned time interval used in open-commissioning-window in step-1. Run the below avahi browse command in the TH terminal avahi-browse -rt _matterc._udp @@ -96,7 +98,7 @@ tests: - Service Domain 422F10CDC290A406.local + If we use Thread setup, then the Service Domain will be 422F10CDC290A406.local verify CM flag is 1 to look for subtypes, on the raspi run $ avahi-browse -p _services._dns-sd._udp | grep _matterc @@ -109,9 +111,10 @@ tests: disabled: true - label: - "DUT is rebooted and Commissioned again, then put in Commissioning - Mode using Open Basic Commissioning Window command, starting - advertising Commissionable Node Discovery service using DNS- SD" + "DUT is rebooted, then put in Commissioning Mode using Open Basic + Commissioning Window command, starting advertising Commissionable Node + Discovery service using DNS-SD" + PICS: CADMIN.S.C01.Rsp verification: | Reboot the device and commission the DUT again. Open the commissioning window using the below command in the TH (Chip-tool) terminal @@ -172,7 +175,7 @@ tests: + eth0 IPv6 19DDF06C3B5DD0C8 _matterc._udp local = veth721e1d9 IPv6 19DDF06C3B5DD0C8 _matterc._udp local - hostname = [E45F0149AE290000.local] + hostname = [E45F0149AE290000.local] address = [fe80::28e0:95ff:fed9:3085] port = [5540] txt = ["PI=" "PH=36" "CM=1" "D=3840" "T=1" "SAI=300" "SII=5000" "VP=65521+32769"] @@ -198,9 +201,15 @@ tests: +;eth0;IPv6;_CM;_sub._matterc._udp;local disabled: true + - label: "Wait for OBCW timeout to expire" + verification: | + Wait until open-basic-commissioning-window time to expire. + disabled: true + - label: "DUT is Commissioned and instructed to enter in commissioning mode using Open Commissioning Window command" + PICS: CADMIN.S.C00.Rsp verification: | Run the below open-commissioning-window in TH Terminal @@ -277,7 +286,7 @@ tests: - label: "Wait for OCW timeout to expire" verification: | - Wait until open-commissioning-window time to expire. (In our example above its 200 sec) + Wait until open-commissioning-window time to expire. disabled: true - label: "If (MCORE.SC.EXTENDED_DISCOVERY ) enable Extended Discovery" @@ -289,7 +298,8 @@ tests: Reference Raspberrypi device is not supporting extended discovery. disabled: true - - label: "If (PICS_EXTENDED_DISCOVERY) check DNS-SD subtypes used by DUT" + - label: + "If (MCORE.SC.EXTENDED_DISCOVERY ) check DNS-SD subtypes used by DUT" PICS: MCORE.SC.EXTENDED_DISCOVERY && MCORE.COM.WIFI && MCORE.COM.ETH && MCORE.COM.THR && MCORE.SC.VENDOR_SUBTYPE && MCORE.SC.DEVTYPE_SUBTYPE diff --git a/src/app/tests/suites/certification/Test_TC_SC_4_10.yaml b/src/app/tests/suites/certification/Test_TC_SC_4_10.yaml index 78cc1e21346212..5398b18c3430ec 100644 --- a/src/app/tests/suites/certification/Test_TC_SC_4_10.yaml +++ b/src/app/tests/suites/certification/Test_TC_SC_4_10.yaml @@ -28,13 +28,13 @@ config: tests: - label: "DUT is instructed to advertise its service" verification: | - verification step to be updated. + 1. Provision the DUT by TH (Chip-tool) disabled: true - label: "TH scans for DNS-SD advertising" verification: | avahi-browse -rt _matter._tcp - Verify on the TH Log: + Verify on the TH(Chip-tool) Log: + eth0 IPv6 3A235FF3FA2DAC10-0000000000000055 _matter._tcp local + eth0 IPv4 3A235FF3FA2DAC10-0000000000000055 _matter._tcp local = eth0 IPv4 3A235FF3FA2DAC10-0000000000000055 _matter._tcp local @@ -48,211 +48,3 @@ tests: port = [5540] txt = ["T=0" "SAI=300" "SII=5000"] disabled: true - - - label: "TH writes ACL entry by setting AuthMode as Group to DUT" - verification: | - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null },{"fabricIndex": 1, "privilege": 4, "authMode": 3, "subjects": [1], "targets": null }]" 1 0 - - Verify success response on the TH Log: - - [1652330385.328196][3240:3245] CHIP:DMG: StatusIB = - [1652330385.328229][3240:3245] CHIP:DMG: { - [1652330385.328264][3240:3245] CHIP:DMG: status = 0x00 (SUCCESS), - [1652330385.328298][3240:3245] CHIP:DMG: }, - disabled: true - - - label: - "Admin generates fabric-unique GroupID, GroupName, random key, - EpochKey0 and GroupKeySetID. Admin sets GroupKeySecurityPolicy = - TrustFirst (1) GroupKeyMulticastPolicy = PerGroupID (0) - EpochStartTime0 = 0" - verification: | - As Admin generates it is not required to verify - disabled: true - - - label: - "Admin sends KeySetWrite command to GroupKeyManagement cluster to DUT - on PIXIT.G.ENDPOINT" - verification: | - ./chip-tool groupkeymanagement key-set-write "{"groupKeySetID": 42, - "groupKeySecurityPolicy": 0, "epochKey0": - "d0d1d2d3d4d5d6d7d8d9dadbdcdddedf", "epochStartTime0": 2220000,"epochKey1": - "d1d1d2d3d4d5d6d7d8d9dadbdcdddedf", "epochStartTime1": 2220001,"epochKey2": - "d2d1d2d3d4d5d6d7d8d9dadbdcdddedf", "epochStartTime2": 2220002 }" 1 0 - - Verify success response on the TH Log: - - [1650610345.847233][2626:2631] CHIP:DMG: - [1650610345.847274][2626:2631] CHIP:DMG: StatusIB = - [1650610345.847317][2626:2631] CHIP:DMG: { - [1650610345.847383][2626:2631] CHIP:DMG: status = 0x00 (SUCCESS), - [1650610345.847429][2626:2631] CHIP:DMG: }, - [1650610345.847477][2626:2631] CHIP:DMG: - disabled: true - - - label: - "Admin binds GroupId with GroupKeySetID in the GroupKeyMap attribute - list on GroupKeyManagement cluster" - verification: | - ./chip-tool groupkeymanagement write group-key-map "[{"groupId": 1, "groupKeySetID": 42, "fabricIndex": 1}]" 1 0 - - Verify success response on the TH Log: - - [1652352019.875893][2552:2557] CHIP:DMG: WriteResponseMessage = - [1652352019.875922][2552:2557] CHIP:DMG: { - [1652352019.875946][2552:2557] CHIP:DMG: AttributeStatusIBs = - [1652352019.875981][2552:2557] CHIP:DMG: [ - [1652352019.876008][2552:2557] CHIP:DMG: AttributeStatusIB = - [1652352019.876041][2552:2557] CHIP:DMG: { - [1652352019.876070][2552:2557] CHIP:DMG: AttributePathIB = - [1652352019.876104][2552:2557] CHIP:DMG: { - [1652352019.876143][2552:2557] CHIP:DMG: Endpoint = 0x0, - [1652352019.876183][2552:2557] CHIP:DMG: Cluster = 0x3f, - [1652352019.876225][2552:2557] CHIP:DMG: Attribute = 0x0000_0000, - [1652352019.876263][2552:2557] CHIP:DMG: } - [1652352019.876303][2552:2557] CHIP:DMG: - [1652352019.876337][2552:2557] CHIP:DMG: StatusIB = - [1652352019.876375][2552:2557] CHIP:DMG: { - [1652352019.876414][2552:2557] CHIP:DMG: status = 0x00 (SUCCESS), - [1652352019.876450][2552:2557] CHIP:DMG: }, - [1652352019.876489][2552:2557] CHIP:DMG: - [1652352019.876519][2552:2557] CHIP:DMG: }, - [1652352019.876562][2552:2557] CHIP:DMG: - [1652352019.876590][2552:2557] CHIP:DMG: AttributeStatusIB = - [1652352019.876622][2552:2557] CHIP:DMG: { - [1652352019.876652][2552:2557] CHIP:DMG: AttributePathIB = - [1652352019.876690][2552:2557] CHIP:DMG: { - [1652352019.876728][2552:2557] CHIP:DMG: Endpoint = 0x0, - [1652352019.876768][2552:2557] CHIP:DMG: Cluster = 0x3f, - [1652352019.876809][2552:2557] CHIP:DMG: Attribute = 0x0000_0000, - [1652352019.876849][2552:2557] CHIP:DMG: ListIndex = Null, - [1652352019.876885][2552:2557] CHIP:DMG: } - [1652352019.876923][2552:2557] CHIP:DMG: - [1652352019.876961][2552:2557] CHIP:DMG: StatusIB = - [1652352019.876995][2552:2557] CHIP:DMG: { - [1652352019.877029][2552:2557] CHIP:DMG: status = 0x00 (SUCCESS), - [1652352019.877077][2552:2557] CHIP:DMG: }, - [1652352019.877132][2552:2557] CHIP:DMG: - [1652352019.877179][2552:2557] CHIP:DMG: }, - [1652352019.877224][2552:2557] CHIP:DMG: - [1652352019.877262][2552:2557] CHIP:DMG: ], - [1652352019.877339][2552:2557] CHIP:DMG: - [1652352019.877381][2552:2557] CHIP:DMG: InteractionModelRevision = 1 - [1652352019.877419][2552:2557] CHIP:DMG: } - disabled: true - - - label: - "Admin sends AddGroup Command to DUT with the GroupID set by Admin on - PIXIT.SC.ENDPOINT" - verification: | - ./chip-tool groups add-group 0x0001 grp1 1 1 - - Verify AddGroupResponse on the TH Log: - - [1651218084.427102][2526:2531] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0004 Command 0x0000_0000 - [1651218084.427203][2526:2531] CHIP:TOO: AddGroupResponse: { - [1651218084.427241][2526:2531] CHIP:TOO: status: 0 - [1651218084.427264][2526:2531] CHIP:TOO: groupId: 1 - [1651218084.427314][2526:2531] CHIP:TOO: } - disabled: true - - - label: - "Admin sends ViewGroup command with the GroupID to the Group cluster - on the DUT on PIXIT.SC.ENDPOINT" - verification: | - ./chip-tool groups view-group 0x0001 1 1 - - Verify ViewGroupResponse on the TH Log: - - [1651218576.149152][2635:2640] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0004 Command 0x0000_0001 - [1651218576.149231][2635:2640] CHIP:TOO: ViewGroupResponse: { - [1651218576.149265][2635:2640] CHIP:TOO: status: 0 - [1651218576.149289][2635:2640] CHIP:TOO: groupId: 1 - [1651218576.149311][2635:2640] CHIP:TOO: groupName: grp1 - [1651218576.149335][2635:2640] CHIP:TOO: } - disabled: true - - - label: "Admin sends KeySetRead Command to DUT" - verification: | - ./chip-tool groupkeymanagement key-set-read 42 1 0 - - Verify KeySetReadResponse on the TH Log: - - [1650610759.578043][2739:2744] CHIP:DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_003F Command=0x0000_0002 - [1650610759.578099][2739:2744] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003F Command 0x0000_0002 - [1650610759.578220][2739:2744] CHIP:TOO: KeySetReadResponse: { - [1650610759.578251][2739:2744] CHIP:TOO: groupKeySet: { - [1650610759.578291][2739:2744] CHIP:TOO: GroupKeySetID: 42 - [1650610759.578334][2739:2744] CHIP:TOO: GroupKeySecurityPolicy: 0 - [1650610759.578363][2739:2744] CHIP:TOO: EpochKey0: null - [1650610759.578391][2739:2744] CHIP:TOO: EpochStartTime0: 2220000 - [1650610759.578418][2739:2744] CHIP:TOO: EpochKey1: null - [1650610759.578445][2739:2744] CHIP:TOO: EpochStartTime1: 2220001 - [1650610759.578472][2739:2744] CHIP:TOO: EpochKey2: null - [1650610759.578498][2739:2744] CHIP:TOO: EpochStartTime2: 2220002 - [1650610759.578527][2739:2744] CHIP:TOO: } - [1650610759.578553][2739:2744] CHIP:TOO: } - disabled: true - - - label: - "TH reads GroupKeyMap Attribute from the GroupKeyManagement cluster - from DUT" - verification: | - ./chip-tool groupkeymanagement read group-key-map 1 0 - - Verify GroupKeyMapStruct on the TH Log: - - 1652429573.936605][2883:2888] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003F Attribute 0x0000_0000 DataVersion: 75110822 - [1652429573.936744][2883:2888] CHIP:TOO: GroupKeyMap: 1 entries - [1652429573.936819][2883:2888] CHIP:TOO: [1]: { - [1652429573.936860][2883:2888] CHIP:TOO: GroupId: 1 - [1652429573.936896][2883:2888] CHIP:TOO: GroupKeySetID: 42 - [1652429573.936932][2883:2888] CHIP:TOO: FabricIndex: 1 - [1652429573.936969][2883:2888] CHIP:TOO: } - disabled: true - - - label: - "TH reads GroupTable attribute from GroupKeyManagement cluster on DUT." - verification: | - ./chip-tool groupkeymanagement read group-table 1 0 - - Verify GroupTable on the TH Log: - - [1655965817.917300][3012:3017] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_003F Attribute 0x0000_0001 DataVersion: 1208492408 - [1655965817.917408][3012:3017] CHIP:TOO: GroupTable: 1 entries - [1655965817.917506][3012:3017] CHIP:TOO: [1]: { - [1655965817.917559][3012:3017] CHIP:TOO: GroupId: 1 - [1655965817.917600][3012:3017] CHIP:TOO: Endpoints: 2 entries - [1655965817.917642][3012:3017] CHIP:TOO: [1]: 0 - [1655965817.917680][3012:3017] CHIP:TOO: [2]: 1 - [1655965817.917718][3012:3017] CHIP:TOO: GroupName: grp1 - [1655965817.917752][3012:3017] CHIP:TOO: FabricIndex: 1 - [1655965817.917784][3012:3017] CHIP:TOO: } - disabled: true - - - label: - "Configure the TH for sending Group message Add the group that was - created in step 3 to the client side Add the keysets with the - GroupKeySetID from the step 2 for the client side Bind the - GroupKeySetID with the GroupID created View the GroupID, GroupName and - GroupKeySetID which is binded for sending the Group message" - verification: | - ./chip-tool groupsettings add-group grp1 0x0001 - - ./chip-tool groupsettings add-keysets 0x0042 0 0x000000000021dfe0 hex:d0d1d2d3d4d5d6d7d8d9dadbdcdddedf - - ./chip-tool groupsettings bind-keyset 0x0001 0x0042 - - ./chip-tool groupsettings show-groups - - Verify groups on the TH Log: - - +-------------------------------------------------------------------------------------+ - | Available Groups : | - +-------------------------------------------------------------------------------------+ - | Group Id | KeySet Id | Group Name | - | 0x101 0x1a1 Group #1 | - | 0x102 0x1a2 Group #2 | - | 0x1 0x42 grp1 | - +-------------------------------------------------------------------------------------+ - disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_SC_4_3.yaml b/src/app/tests/suites/certification/Test_TC_SC_4_3.yaml index e0f8cda7051c3b..887f256cbbc1db 100644 --- a/src/app/tests/suites/certification/Test_TC_SC_4_3.yaml +++ b/src/app/tests/suites/certification/Test_TC_SC_4_3.yaml @@ -13,7 +13,7 @@ # 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.3. [TC-SC-4.3] Operational Discovery - Node +name: 15.4.3. [TC-SC-4.3] Discovery [DUT as Commissionee] PICS: - MCORE.ROLE.COMMISSIONEE @@ -24,9 +24,11 @@ config: endpoint: 0 tests: - - label: "TH is instructed to start advertising a service using DNS-SD" + - label: + "DUT is commissioned to TH and DUT is instructed to advertise its + operational service (_matter._tcp)." verification: | - verification step to be updated. + 1. Provision the DUT by TH (Chip-tool) disabled: true - label: "Scan for DNS-SD advertising" @@ -35,9 +37,7 @@ tests: MCORE.SC.SII_OP_DISCOVERY_KEY && MCORE.SC.SAI_OP_DISCOVERY_KEY && MCORE.SC.T_KEY verification: | - ubuntu@ubuntu:~$ avahi-browse -rt _matter._tcp - - Verify on the TH Log: + avahi-browse -rt _matter._tcp + veth721e1d9 IPv6 433B62F8F07F4327-0000000000000001 _matter._tcp local = veth721e1d9 IPv6 433B62F8F07F4327-0000000000000001 _matter._tcp local @@ -46,49 +46,3 @@ tests: port = [5540] txt = ["T=1" "SAI=300" "SII=5000"] disabled: true - - - label: - "TH is instructed to start advertising an operational service using - DNS-SD with non-standard TXT record keys" - verification: | - Run the publish service command on TH: - - avahi-publish-service --subtype=_S3._sub._matter._tcp --subtype=_L840._sub._matter._tcp DD200C20D25AE5F7 --subtype=_CM._sub._matter._tcp _matter._tcp 11111 D=840 CM=2 INVALID_TEST=40 - disabled: true - - - label: - "DUT is rebooted and Commissioned again, then put in Commissioning - Mode using Open Basic Commissioning Window command, DUT is instructed - to advertise its service with the modified TXT record." - verification: | - ./chip-tool administratorcommissioning open-basic-commissioning-window 200 1 0 --timedInteractionTimeoutMs 1000 - - verify on TH (Chip-tool) logs: - - [1650873075.234374][7964:7969] CHIP:DMG: EndpointId = 0x0, - [1650873075.234449][7964:7969] CHIP:DMG: ClusterId = 0x3c, - [1650873075.234542][7964:7969] CHIP:DMG: CommandId = 0x1, - [1650873075.234613][7964:7969] CHIP:DMG: }, - [1650873075.234693][7964:7969] CHIP:DMG: - [1650873075.234758][7964:7969] CHIP:DMG: StatusIB = - [1650873075.234829][7964:7969] CHIP:DMG: { - [1650873075.234909][7964:7969] CHIP:DMG: status = 0x00 (SUCCESS), - [1650873075.234984][7964:7969] CHIP:DMG: }, - disabled: true - - - label: "Scan for DNS-SD advertising" - PICS: - MCORE.COM.WIFI && MCORE.COM.ETH && MCORE.COM.THR && - MCORE.SC.SII_OP_DISCOVERY_KEY && MCORE.SC.SAI_OP_DISCOVERY_KEY && - MCORE.SC.T_KEY - verification: | - ubuntu@ubuntu:~$ avahi-browse -rt _matter._tcp - Verify on the TH Log: - - + eth0 IPv6 B1605B84E886EDCF-0000000000000258 _matter._tcp local - = eth0 IPv6 21F41C9933CAAF62-000000000000003C _matter._tcp local - hostname = [E45F010EBE440000.local] - address = [fe80::e65f:1ff:fe0e:be44] - port = [5540] - txt = ["T=1" "SAI=300" "SII=5000"] - disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_SC_4_4.yaml b/src/app/tests/suites/certification/Test_TC_SC_4_4.yaml index aa9d9da7d7d8da..0703e6c8f9b512 100644 --- a/src/app/tests/suites/certification/Test_TC_SC_4_4.yaml +++ b/src/app/tests/suites/certification/Test_TC_SC_4_4.yaml @@ -13,7 +13,7 @@ # 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.4. [TC-SC-4.4] Operational Discovery - Controller [DUT - Controller] +name: 15.4.4. [TC-SC-4.4] Discovery [DUT as Controller] PICS: - PICS_MCORE_ROLE_CONTROLLER @@ -24,28 +24,89 @@ config: endpoint: 0 tests: + - label: "Note" + verification: | + Chip-tool command used below are an example to verify the DUT as controller test cases. For certification test, we expect DUT should have a capability or way to run the equivalent command. + disabled: true + - label: "TH starts commissioning process with DUT" verification: | - verification step to be updated. + 1. Provision the DUT by TH (Chip-tool) disabled: true - - label: "DUT reads nodelabel attribute from TH" - PICS: BINFO.C.A0005 + - label: "DUT reads Vendor Id attribute from TH" + PICS: BINFO.C.A0002 verification: | - verification step to be updated. + On TH, Verify that TH read and shows Vendor Id value + ./chip-tool basic read vendor-id 1 0 + + [1660776352.802689][3357:3357] CHIP:DMG: + [1660776352.802776][3357:3357] CHIP:DMG: ReportDataMessage = + [1660776352.802807][3357:3357] CHIP:DMG: { + [1660776352.802832][3357:3357] CHIP:DMG: AttributeReportIBs = + [1660776352.802868][3357:3357] CHIP:DMG: [ + [1660776352.802896][3357:3357] CHIP:DMG: AttributeReportIB = + [1660776352.802933][3357:3357] CHIP:DMG: { + [1660776352.802963][3357:3357] CHIP:DMG: AttributeDataIB = + [1660776352.802999][3357:3357] CHIP:DMG: { + [1660776352.803040][3357:3357] CHIP:DMG: DataVersion = 0x5c6f4557, + [1660776352.803080][3357:3357] CHIP:DMG: AttributePathIB = + [1660776352.803118][3357:3357] CHIP:DMG: { + [1660776352.803157][3357:3357] CHIP:DMG: Endpoint = 0x0, + [1660776352.803198][3357:3357] CHIP:DMG: Cluster = 0x28, + [1660776352.803241][3357:3357] CHIP:DMG: Attribute = 0x0000_0002, + [1660776352.803279][3357:3357] CHIP:DMG: } + [1660776352.803319][3357:3357] CHIP:DMG: + [1660776352.803360][3357:3357] CHIP:DMG: Data = 65521, + [1660776352.803396][3357:3357] CHIP:DMG: }, + [1660776352.803434][3357:3357] CHIP:DMG: + [1660776352.803468][3357:3357] CHIP:DMG: }, + [1660776352.803503][3357:3357] CHIP:DMG: + [1660776352.803530][3357:3357] CHIP:DMG: ], + [1660776352.803571][3357:3357] CHIP:DMG: + [1660776352.803600][3357:3357] CHIP:DMG: SuppressResponse = true, + [1660776352.803628][3357:3357] CHIP:DMG: InteractionModelRevision = 1 + [1660776352.803655][3357:3357] CHIP:DMG: } + [1660776352.803699][3357:3357] CHIP:DMG: disabled: true - label: "Change the IP address of TH by any means within the same network" verification: | - 1. Take two routers connected to the same ISP as input. - 2. Execute step 1 to step 5 using Router1 Configuration. - 3. Once step 1 to step 5 are executed in Router1 switch TH and DUT to Router2. - 4. Execute step 1 to step 5 using Router2 Configuration. - 5. Check the IP so that the Routers(Router1 and Router2) will have different IPs to Raspi. + Connect the raspi running the TH to another router which is on the same network. Make sure that the DUT and TH are on the same network and can ping to each other. Observe that the TH gets a new IP address. Perform Step 4 disabled: true - - label: "DUT reads nodelabel attribute from TH" - PICS: BINFO.C.A0005 + - label: "DUT reads Vendor Id attribute from TH" + PICS: BINFO.C.A0002 verification: | - verification step to be updated. + On TH, Verify that TH read and shows Vendor Id value + ./chip-tool basic read vendor-id 1 0 + + [1660776352.802689][3357:3357] CHIP:DMG: + [1660776352.802776][3357:3357] CHIP:DMG: ReportDataMessage = + [1660776352.802807][3357:3357] CHIP:DMG: { + [1660776352.802832][3357:3357] CHIP:DMG: AttributeReportIBs = + [1660776352.802868][3357:3357] CHIP:DMG: [ + [1660776352.802896][3357:3357] CHIP:DMG: AttributeReportIB = + [1660776352.802933][3357:3357] CHIP:DMG: { + [1660776352.802963][3357:3357] CHIP:DMG: AttributeDataIB = + [1660776352.802999][3357:3357] CHIP:DMG: { + [1660776352.803040][3357:3357] CHIP:DMG: DataVersion = 0x5c6f4557, + [1660776352.803080][3357:3357] CHIP:DMG: AttributePathIB = + [1660776352.803118][3357:3357] CHIP:DMG: { + [1660776352.803157][3357:3357] CHIP:DMG: Endpoint = 0x0, + [1660776352.803198][3357:3357] CHIP:DMG: Cluster = 0x28, + [1660776352.803241][3357:3357] CHIP:DMG: Attribute = 0x0000_0002, + [1660776352.803279][3357:3357] CHIP:DMG: } + [1660776352.803319][3357:3357] CHIP:DMG: + [1660776352.803360][3357:3357] CHIP:DMG: Data = 65521, + [1660776352.803396][3357:3357] CHIP:DMG: }, + [1660776352.803434][3357:3357] CHIP:DMG: + [1660776352.803468][3357:3357] CHIP:DMG: }, + [1660776352.803503][3357:3357] CHIP:DMG: + [1660776352.803530][3357:3357] CHIP:DMG: ], + [1660776352.803571][3357:3357] CHIP:DMG: + [1660776352.803600][3357:3357] CHIP:DMG: SuppressResponse = true, + [1660776352.803628][3357:3357] CHIP:DMG: InteractionModelRevision = 1 + [1660776352.803655][3357:3357] CHIP:DMG: } + [1660776352.803699][3357:3357] CHIP:DMG: disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_SC_4_7.yaml b/src/app/tests/suites/certification/Test_TC_SC_4_7.yaml index f5cf0c10623f3a..9e6781ff6b32a8 100644 --- a/src/app/tests/suites/certification/Test_TC_SC_4_7.yaml +++ b/src/app/tests/suites/certification/Test_TC_SC_4_7.yaml @@ -13,7 +13,7 @@ # 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.7. [TC-SC-4.7] Commissioner Discovery - Commissionee +name: 15.4.7. [TC-SC-4.7] Commissioner Discovery [DUT as Commissionee] PICS: - MCORE.ROLE.COMMISSIONEE @@ -34,7 +34,7 @@ tests: - label: "Scan for DNS-SD commissioner advertisements from TH" PICS: MCORE.SC.DEVTYPE_SUBTYPE && MCORE.SC.VP_KEY && MCORE.SC.DT_KEY && - MCORE.SC.DN_KEY && + MCORE.SC.DN_KEY verification: | if DUT supports discovering UDC, DUT should be able to scan the TV-app @@ -49,20 +49,20 @@ tests: address = [fe80::e65f:1ff:fe49:ae29] port = [5650] txt = ["T=1" "SAI=300" "SII=5000" "DN=Test TV" "DT=35" "VP=65521+32769"] - disabled: true - - label: - "By any means, TH adds an unknown key/value pair in the advertised - data(e.g. AB=12345)" - verification: | - Run the unknown key/value pair on TH Terminal: + to look for subtypes, on the raspi run $ a avahi-browse -p _services._dns-sd._udp | grep _matterd - avahi-publish-service --subtype=_V123._sub._matterd._udp DD200C20D25AE5F7 _matterd._udp 33333 VP=123+456 DT=35 DN="Living Room TV" INVALID_TEST=40 + +;wlan0;IPv6;_T35;_sub._matterd._udp;local + +;wlan0;IPv6;_V65521;_sub._matterd._udp;local + +;wlan0;IPv6;_matterd;_udp;local + +;eth0;IPv6;_T35;_sub._matterd._udp;local + +;eth0;IPv6;_V65521;_sub._matterd._udp;local + +;eth0;IPv6;_matterd;_udp;local disabled: true - label: "Scan for DNS-SD commissioner advertisements from TH" verification: | - Verify the DUT commissioner is able to discover the TH. + Verify the DUT is able to discover the TH. As an example, In the case of chip-tool as commissioner, you can verify with the below command, (Use the equivalent command on the DUT) @@ -73,24 +73,37 @@ tests: [1659544548031] [13752:9267297] CHIP: [DIS] Mdns: OnBrowseAdd name: DD200C20D25AE5F7, type: _matterc._udp., domain: local., interface: 8 [1659544548031] [13752:9267297] CHIP: [DIS] Resolve type=_matterc._udp name=DD200C20D25AE5F7 interface=8 [1659544548032] [13752:9267297] CHIP: [DIS] Mdns : OnNewInterface hostname:ubuntuserverAccessory1.local. fullname:DD200C20D25AE5F7._matterc._udp.local. interface: 8 port: 26411 TXT:D=840CM=2INVALID_TEST=40 [1659544548033] [13752:9267297] CHIP: [DIS] Mdns: OnNewAddress interface: 8 ip:fd5d:9cc0:fc52:0:dea6:32ff:fe8d:7072 [1659544548033] [13752:9267297] CHIP: [DIS] Mdns: Resolve success on interface 8 - [1659544548033] [13752:9267297] CHIP: [DIS] Discovered node: - [1659544548033] [13752:9267297] CHIP: [DIS] Hostname: ubuntuserverAcce [1659544548033] [13752:9267297] CHIP: [DIS] IP Address #1: fd5d:9cc0:fc52:0:dea6:32ff:fe8d:7072 - [1659544548033] [13752:9267297] CHIP: [DIS] Port: 11111 - [1659544548033] [13752:9267297] CHIP: [DIS] Mrp Interval idle: not present - [1659544548033] [13752:9267297] CHIP: [DIS] Mrp Interval active: not present - [1659544548033] [13752:9267297] CHIP: [DIS] TCP Supported: 0 - [1659544548033] [13752:9267297] CHIP: [DIS] Long Discriminator: 840 - [1659544548033] [13752:9267297] CHIP: [DIS] Instance Name: DD200C20D25AE5F7 - [1659544548033] [13752:9267297] CHIP: [DIS] Commissioning Mode: 2 - [1659544548033] [13752:9267297] CHIP: [DIS] Discovered node: - [1659544548033] [13752:9267297] CHIP: [DIS] Hostname: ubuntuserverAcce [1659544548033] [13752:9267297] CHIP: [DIS] IP Address #1: fd5d:9cc0:fc52:0:dea6:32ff:fe8d:7072 - [1659544548033] [13752:9267297] CHIP: [DIS] Port: 11111 - [1659544548033] [13752:9267297] CHIP: [DIS] Mrp Interval idle: not present - [1659544548033] [13752:9267297] CHIP: [DIS] Mrp Interval active: not present - [1659544548033] [13752:9267297] CHIP: [DIS] TCP Supported: 0 - [1659544548033] [13752:9267297] CHIP: [DIS] Long Discriminator: 840 - [1659544548033] [13752:9267297] CHIP: [DIS] Instance Name: DD200C20D25AE5F7 - [1659544548033] [13752:9267297] CHIP: [DIS] Commissioning Mode: 2 + [1660288371.031350][3364:3369] CHIP:DIS: Discovered node: + [1660288371.031374][3364:3369] CHIP:DIS: Hostname: E45F0149AE290000 [1660288371.031402][3364:3369] CHIP:DIS: IP Address #1: fe80::e65f:1ff:fe49:ae29 + [1660288371.031427][3364:3369] CHIP:DIS: Port: 5640 + [1660288371.031450][3364:3369] CHIP:DIS: Mrp Interval idle: 5000 ms + [1660288371.031473][3364:3369] CHIP:DIS: Mrp Interval active: 300 ms + [1660288371.031496][3364:3369] CHIP:DIS: TCP Supported: 1 + [1660288371.031521][3364:3369] CHIP:DIS: Rotating ID: 01005FDB39737473FB22B819CEBB1084AFD5 + [1660288371.031544][3364:3369] CHIP:DIS: Device Name: Test TV + [1660288371.031566][3364:3369] CHIP:DIS: Vendor ID: 65521 + [1660288371.031589][3364:3369] CHIP:DIS: Product ID: 32769 + [1660288371.031609][3364:3369] CHIP:DIS: Device Type: 35 + [1660288371.031628][3364:3369] CHIP:DIS: Long Discriminator: 3840 + [1660288371.031647][3364:3369] CHIP:DIS: Pairing Hint: 36 + [1660288371.031669][3364:3369] CHIP:DIS: Instance Name: 35025D5C5DA30C17 + [1660288371.031694][3364:3369] CHIP:DIS: Commissioning Mode: 0 + [1660288371.031722][3364:3369] CHIP:DIS: Discovered node: + [1660288371.031743][3364:3369] CHIP:DIS: Hostname: E45F0149AE290000 [1660288371.031768][3364:3369] CHIP:DIS: IP Address #1: fe80::e65f:1ff:fe49:ae29 + [1660288371.031791][3364:3369] CHIP:DIS: Port: 5640 + [1660288371.031814][3364:3369] CHIP:DIS: Mrp Interval idle: 5000 ms + [1660288371.031836][3364:3369] CHIP:DIS: Mrp Interval active: 300 ms + [1660288371.031859][3364:3369] CHIP:DIS: TCP Supported: 1 + [1660288371.031888][3364:3369] CHIP:DIS: Rotating ID: 01005FDB39737473FB22B819CEBB1084AFD5 + [1660288371.031909][3364:3369] CHIP:DIS: Device Name: Test TV + [1660288371.031928][3364:3369] CHIP:DIS: Vendor ID: 65521 + [1660288371.031950][3364:3369] CHIP:DIS: Product ID: 32769 + [1660288371.031973][3364:3369] CHIP:DIS: Device Type: 35 + [1660288371.031995][3364:3369] CHIP:DIS: Long Discriminator: 3840 + [1660288371.032018][3364:3369] CHIP:DIS: Pairing Hint: 36 + [1660288371.032042][3364:3369] CHIP:DIS: Instance Name: 35025D5C5DA30C17 + [1660288371.032064][3364:3369] CHIP:DIS: Commissioning Mode: 0 + [1659544578034] [13752:9267291] CHIP: [CTL] Shutting down the commissioner [1659544578034] [13752:9267291] CHIP: [CTL] Stopping commissioning discovery over DNS-SD [1659544578034] [13752:9267291] CHIP: [CTL] Shutting down the controller diff --git a/src/app/tests/suites/certification/Test_TC_SWTCH_2_2.yaml b/src/app/tests/suites/certification/Test_TC_SWTCH_2_2.yaml index 0a18301fb30716..ac51168f2d9a1e 100644 --- a/src/app/tests/suites/certification/Test_TC_SWTCH_2_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_SWTCH_2_2.yaml @@ -24,30 +24,23 @@ config: endpoint: 0 tests: - - label: "Commission DUT to TH (can be skipped if done in a preceding test)" + - label: "Note" verification: | - + NOTE: https://github.com/project-chip/connectedhomeip/tree/master/examples/all-clusters-app/linux#readme + Events to be executed as following + 1. Compile app using below command in connectedhomeip folder + a. ./scripts/run_in_build_env.sh ./scripts/build/build_examples.py --target linux-arm64-all-clusters-no-ble-asan-clang build + b. ./scripts/run_in_build_env.sh ./scripts/build/build_examples.py --target linux-arm64-all-clusters-no-ble-asan-libfuzzer-clang build + 2. Build respective app (all-clusters-app) + 3. Commission DUT to TH + 4. Open 2nd terminal of DUT and provide the below command to obtain PID of DUT + ps -aef|grep all-clusters-app + 5. Follow the Verification step below to generate the event in 2nd terminal of DUT disabled: true - label: "Commission DUT to TH (can be skipped if done in a preceding test)" verification: | - NOTE: - To Run the event test case we need to build event commands on DUT[All-cluster-ap] terminal.Below I mention the commands for how to build for linux arm64 it depends on the DUT what we use.I provided the link for build events. - - https://github.com/project-chip/connectedhomeip/tree/master/examples/all-clusters-app/linux#trigger-switch-events - - - - - Here I provide cmmds for build on linux arm64 - - 1. ./scripts/run_in_build_env.sh "./scripts/build/build_examples.py --target linux-arm64-all-clusters-no-ble-asan-clang build - - 2../scripts/run_in_build_env.sh "./scripts/build/build_examples.py --target linux-arm64-all-clusters-no-ble-asan-libfuzzer-clang build - - 3. ./out/linux-arm64-all-clusters-no-ble-asan-libfuzzer-clang/chip-all-clusters-app-fuzzing - - 4. ./out/linux-arm64-all-clusters-no-ble-asan-libfuzzer-clang/chip-all-clusters-app-fuzzing $(INPUT_FILE) + Commission DUT to TH disabled: true - label: "Set up subscription to SwitchLatched event" @@ -127,7 +120,6 @@ tests: - label: "If NumberOfPositions>2 (see 2c of TC-SWTCH-2.1) : - Operator sets switch to next position - Read CurrentPosition attribute" - PICS: SWTCH.S.F00 verification: | Raspi device doesn"t support more than 2 position ,so this step is not verifiable by using raspi device @@ -877,6 +869,9 @@ tests: [1659696223.568397][3981:3986] CHIP:TOO: } + In Raspi platform to change the switch position use the below command, Pls use equivalent command on the respective DUT.open one more terminal on DUT side execute the echo command on that terminal. + + echo "{"Name":"MultiPressOngoing","previousPosition":1,"CurrentNumberOfPressesCounted":3}" > /tmp/chip_all_clusters_fifo- (PID of DUT) Please use Interactive mode to Verify the subscription of an event Here the command to enter interactive mode:-- @@ -888,7 +883,7 @@ tests: [1659695330.923283][3912:3918] CHIP:TOO: Priority: Info [1659695330.923302][3912:3918] CHIP:TOO: Timestamp: 17754336 [1659695330.923326][3912:3918] CHIP:TOO: MultiPressComplete: { - [1659695330.923346][3912:3918] CHIP:TOO: PrevioiusPosition: 1 + [1659695330.923346][3912:3918] CHIP:TOO: PreviousPosition: 1 [1659695330.923366][3912:3918] CHIP:TOO: TotalNumberOfPressesCounted: 3 [1659695330.923385][3912:3918] CHIP:TOO: } disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_SWTCH_3_2.yaml b/src/app/tests/suites/certification/Test_TC_SWTCH_3_2.yaml index 57f53c5fb9b412..7a302ef34271d6 100644 --- a/src/app/tests/suites/certification/Test_TC_SWTCH_3_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_SWTCH_3_2.yaml @@ -31,22 +31,16 @@ tests: - label: "Note" verification: | - To Run the event test case we need to build event commands on DUT[All-cluster-ap] side.Below I mention the commands for how to build for linux arm64 it depends on the DUT what we use.I provided the link for build events. - - https://github.com/project-chip/connectedhomeip/tree/master/examples/all-clusters-app/linux#trigger-switch-events - - - - - Here I provide cmmds for build on linux arm64 - - 1. ./scripts/run_in_build_env.sh "./scripts/build/build_examples.py --target linux-arm64-all-clusters-no-ble-asan-clang build - - 2../scripts/run_in_build_env.sh "./scripts/build/build_examples.py --target linux-arm64-all-clusters-no-ble-asan-libfuzzer-clang build - - 3. ./out/linux-arm64-all-clusters-no-ble-asan-libfuzzer-clang/chip-all-clusters-app-fuzzing - - 4. ./out/linux-arm64-all-clusters-no-ble-asan-libfuzzer-clang/chip-all-clusters-app-fuzzing $(INPUT_FILE) + NOTE: https://github.com/project-chip/connectedhomeip/tree/master/examples/all-clusters-app/linux#readme + Events to be executed as following + 1. Compile app using below command in connectedhomeip folder + a. ./scripts/run_in_build_env.sh ./scripts/build/build_examples.py --target linux-arm64-all-clusters-no-ble-asan-clang build + b. ./scripts/run_in_build_env.sh ./scripts/build/build_examples.py --target linux-arm64-all-clusters-no-ble-asan-libfuzzer-clang build + 2. Build respective app (all-clusters-app) + 3. Commission DUT to TH + 4. Open 2nd terminal of DUT and provide the below command to obtain PID of DUT + ps -aef|grep all-clusters-app + 5. Follow the Verification step below to generate the event in 2nd terminal of DUT disabled: true - label: diff --git a/src/app/tests/suites/certification/ci-pics-values b/src/app/tests/suites/certification/ci-pics-values index 67322305f85885..1e7cf4e8e128fa 100644 --- a/src/app/tests/suites/certification/ci-pics-values +++ b/src/app/tests/suites/certification/ci-pics-values @@ -1668,3 +1668,15 @@ MCORE.IDM.C.SubscribeRequest.Attribute.DataType_Integer=1 MCORE.IDM.C.SubscribeRequest.Attribute.DataType_FloatingPoint=1 MCORE.IDM.C.SubscribeRequest.Attribute.DataType_List=1 MCORE.IDM.S.LargeData=1 +MCORE.IDM.C.WriteRequest.Attribute.DataType_Bool=1 +MCORE.IDM.C.WriteRequest.Attribute.DataType_String=1 +MCORE.IDM.C.WriteRequest.Attribute.DataType_UnsignedInteger=1 +MCORE.IDM.C.WriteRequest.Attribute.DataType_SignedInteger=1 +MCORE.IDM.C.WriteRequest.Attribute.DataType_Struct=1 +MCORE.IDM.C.WriteRequest.Attribute.DataType_FloatingPoint=1 +MCORE.IDM.C.WriteRequest.Attribute.DataType_List=1 +MCORE.IDM.C.WriteRequest.Attribute.DataType_OctetString=1 +MCORE.IDM.C.WriteRequest.Attribute.DataType_Enum=1 +MCORE.IDM.C.WriteRequest.Attribute.DataType_Bitmap=1 +MCORE.IDM.C.SubscribeRequest.Attribute.DataType_Bool=1 +MCORE.IDM.C.SubscribeRequest.MultipleAttributes=1 diff --git a/src/app/tests/suites/manualTests.json b/src/app/tests/suites/manualTests.json index bfa3a7e67cf84e..0dbf826cca2bee 100644 --- a/src/app/tests/suites/manualTests.json +++ b/src/app/tests/suites/manualTests.json @@ -245,8 +245,7 @@ "Test_TC_OCC_2_2", "Test_TC_OCC_2_3", "Test_TC_OCC_2_4", - "Test_TC_OCC_3_1", - "Test_TC_OCC_3_2" + "Test_TC_OCC_3_1" ], "PressureMeasurement": ["Test_TC_PRS_3_1"], "PowerSource": ["Test_TC_PS_2_2", "Test_TC_PS_3_1"], diff --git a/zzz_generated/chip-tool/zap-generated/test/Commands.h b/zzz_generated/chip-tool/zap-generated/test/Commands.h index 93aea4dc646cd1..da80f584197147 100644 --- a/zzz_generated/chip-tool/zap-generated/test/Commands.h +++ b/zzz_generated/chip-tool/zap-generated/test/Commands.h @@ -494,7 +494,6 @@ class ManualTestList : public Command printf("Test_TC_OCC_2_3\n"); printf("Test_TC_OCC_2_4\n"); printf("Test_TC_OCC_3_1\n"); - printf("Test_TC_OCC_3_2\n"); printf("Test_TC_PRS_3_1\n"); printf("Test_TC_PS_2_2\n"); printf("Test_TC_PS_3_1\n"); @@ -89775,62 +89774,6 @@ class Test_TC_OCC_3_1Suite : public TestCommand } }; -class Test_TC_OCC_3_2Suite : public TestCommand -{ -public: - Test_TC_OCC_3_2Suite(CredentialIssuerCommands * credsIssuerConfig) : TestCommand("Test_TC_OCC_3_2", 0, credsIssuerConfig) - { - AddArgument("nodeId", 0, UINT64_MAX, &mNodeId); - AddArgument("cluster", &mCluster); - AddArgument("endpoint", 0, UINT16_MAX, &mEndpoint); - AddArgument("timeout", 0, UINT16_MAX, &mTimeout); - } - - ~Test_TC_OCC_3_2Suite() {} - - chip::System::Clock::Timeout GetWaitDuration() const override - { - return chip::System::Clock::Seconds16(mTimeout.ValueOr(kTimeoutInSeconds)); - } - -private: - chip::Optional mNodeId; - chip::Optional mCluster; - chip::Optional mEndpoint; - chip::Optional mTimeout; - - chip::EndpointId GetEndpoint(chip::EndpointId endpoint) { return mEndpoint.HasValue() ? mEndpoint.Value() : endpoint; } - - // - // Tests methods - // - - void OnResponse(const chip::app::StatusIB & status, chip::TLV::TLVReader * data) override - { - bool shouldContinue = false; - - switch (mTestIndex - 1) - { - default: - LogErrorOnFailure(ContinueOnChipMainThread(CHIP_ERROR_INVALID_ARGUMENT)); - } - - if (shouldContinue) - { - ContinueOnChipMainThread(CHIP_NO_ERROR); - } - } - - CHIP_ERROR DoTestStep(uint16_t testIndex) override - { - using namespace chip::app::Clusters; - switch (testIndex) - { - } - return CHIP_NO_ERROR; - } -}; - class Test_TC_PRS_3_1Suite : public TestCommand { public: @@ -100651,7 +100594,6 @@ void registerCommandsTests(Commands & commands, CredentialIssuerCommands * creds make_unique(credsIssuerConfig), make_unique(credsIssuerConfig), make_unique(credsIssuerConfig), - make_unique(credsIssuerConfig), make_unique(credsIssuerConfig), make_unique(credsIssuerConfig), make_unique(credsIssuerConfig),