diff --git a/src/app/tests/suites/certification/Test_TC_ALOGIN_12_1.yaml b/src/app/tests/suites/certification/Test_TC_ALOGIN_12_1.yaml index 2c7be1eebcf05e..be5f6f789c5c04 100644 --- a/src/app/tests/suites/certification/Test_TC_ALOGIN_12_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_ALOGIN_12_1.yaml @@ -59,7 +59,6 @@ tests: - name: "Status" value: 0 - #Issue: https://github.com/project-chip/connectedhomeip/issues/28992 - label: "Step 1: TH sends a GetSetupPIN command to the DUT with test values provided by the product maker." diff --git a/src/app/tests/suites/certification/Test_TC_CONTENTLAUNCHER_10_4.yaml b/src/app/tests/suites/certification/Test_TC_CONTENTLAUNCHER_10_4.yaml index 1fbbdab81d8a26..638b78cd2ac59d 100644 --- a/src/app/tests/suites/certification/Test_TC_CONTENTLAUNCHER_10_4.yaml +++ b/src/app/tests/suites/certification/Test_TC_CONTENTLAUNCHER_10_4.yaml @@ -36,10 +36,10 @@ tests: verification: | 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) or tv-casting-app (when DUT is a commissionee): - ./chip-tool contentlauncher launch-content '{"parameterList": [ { "type": 0, "value": "exampleString", "externalIDList": [ { "name": "exampleName", "value": "exampleValue"} ] } ] }' 0 '{"playbackPosition": 0, "textTrack": {"languageCode": "", "audioOutputIndex": 0}}' 1 1 + ./chip-tool contentlauncher launch-content '{"parameterList": [ { "type": 0, "value": "exampleString", "externalIDList": [ { "name": "exampleName", "value": "exampleValue"} ] } ] }' 0 1 1 --Data '{"playbackPosition": 0, "textTrack": {"languageCode": "", "audioOutputIndex": 0}}' - ./chip-tv-casting-app contentlauncher launch-content '{"parameterList": [ { "type": 0, "value": "exampleString", "externalIDList": [ { "name": "exampleName", "value": "exampleValue"} ] } ] }' 0 '{"playbackPosition": 0, "textTrack": {"languageCode": "", "audioOutputIndex": 0}}' 1 1 + ./chip-tv-casting-app contentlauncher launch-content '{"parameterList": [ { "type": 0, "value": "exampleString", "externalIDList": [ { "name": "exampleName", "value": "exampleValue"} ] } ] }' 0 1 1 --Data '{"playbackPosition": 0, "textTrack": {"languageCode": "", "audioOutputIndex": 0}}' On TH (tv-app), Verify the launch content command is received successfully. diff --git a/src/app/tests/suites/certification/Test_TC_DEMM_1_1.yaml b/src/app/tests/suites/certification/Test_TC_DEMM_1_1.yaml index 832b21e12ac63b..b2f927d14fd554 100644 --- a/src/app/tests/suites/certification/Test_TC_DEMM_1_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_DEMM_1_1.yaml @@ -48,9 +48,9 @@ tests: On the TH(Chip-tool) Log, Verify featureMap value is 0 and below is the sample log provided for the raspi platform: - [1705923720.577354][23553:23555] CHIP:DMG: } - [1705923720.577393][23553:23555] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_009F Attribute 0x0000_FFFC DataVersion: 2217281174 - [1705923720.577412][23553:23555] CHIP:TOO: FeatureMap: 1 + [1707803263.396282][12695:12697] CHIP:DMG: } + [1707803263.396447][12695:12697] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_009F Attribute 0x0000_FFFC DataVersion: 3404644350 + [1707803263.396492][12695:12697] CHIP:TOO: FeatureMap: 0 cluster: "LogCommands" command: "UserPrompt" PICS: PICS_SKIP_SAMPLE_APP diff --git a/src/app/tests/suites/certification/Test_TC_DESC_2_1.yaml b/src/app/tests/suites/certification/Test_TC_DESC_2_1.yaml index 734282a82e7ca8..2ce0e296bbc2d5 100644 --- a/src/app/tests/suites/certification/Test_TC_DESC_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_DESC_2_1.yaml @@ -136,82 +136,87 @@ tests: verification: | For all the Endpoint id’s listed in step 1a run the following steps. For all the server list entries listed in the output - Convert them to Hex values. For example 29 is 0x001D. Verify that these are also present in the device_type.json. Every server cluster listed in the JSON should correspond to a number here in the output. + The cluster ID's listed in the below log is from the All-Cluster-app. Please run the below command in all the Reference apps (bridge-app, tv-app, microwave-oven-app, Lock-app, Energy-Management-app and Thermostat-app). + ./chip-tool descriptor read server-list 1 1 - Verify ServerList entries on the TH (Chip-tool) and below is the sample log provided for the raspi platform, Here ServerList entries are 70. - - [1693218196.392903][13451:13453] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_001D Attribute 0x0000_0001 DataVersion: 3853201227 - [1693218196.393030][13451:13453] CHIP:TOO: ServerList: 70 entries - [1693218196.393047][13451:13453] CHIP:TOO: [1]: 3 - [1693218196.393059][13451:13453] CHIP:TOO: [2]: 4 - [1693218196.393071][13451:13453] CHIP:TOO: [3]: 5 - [1693218196.393081][13451:13453] CHIP:TOO: [4]: 6 - [1693218196.393092][13451:13453] CHIP:TOO: [5]: 7 - [1693218196.393103][13451:13453] CHIP:TOO: [6]: 8 - [1693218196.393114][13451:13453] CHIP:TOO: [7]: 15 - [1693218196.393125][13451:13453] CHIP:TOO: [8]: 29 - [1693218196.393136][13451:13453] CHIP:TOO: [9]: 30 - [1693218196.393147][13451:13453] CHIP:TOO: [10]: 37 - [1693218196.393159][13451:13453] CHIP:TOO: [11]: 47 - [1693218196.393169][13451:13453] CHIP:TOO: [12]: 59 - [1693218196.393180][13451:13453] CHIP:TOO: [13]: 64 - [1693218196.393191][13451:13453] CHIP:TOO: [14]: 65 - [1693218196.393201][13451:13453] CHIP:TOO: [15]: 69 - [1693218196.393212][13451:13453] CHIP:TOO: [16]: 80 - [1693218196.393222][13451:13453] CHIP:TOO: [17]: 81 - [1693218196.393233][13451:13453] CHIP:TOO: [18]: 82 - [1693218196.393244][13451:13453] CHIP:TOO: [19]: 83 - [1693218196.393254][13451:13453] CHIP:TOO: [20]: 84 - [1693218196.393265][13451:13453] CHIP:TOO: [21]: 85 - [1693218196.393276][13451:13453] CHIP:TOO: [22]: 86 - [1693218196.393286][13451:13453] CHIP:TOO: [23]: 87 - [1693218196.393297][13451:13453] CHIP:TOO: [24]: 89 - [1693218196.393308][13451:13453] CHIP:TOO: [25]: 91 - [1693218196.393318][13451:13453] CHIP:TOO: [26]: 92 - [1693218196.393329][13451:13453] CHIP:TOO: [27]: 93 - [1693218196.393340][13451:13453] CHIP:TOO: [28]: 96 - [1693218196.393350][13451:13453] CHIP:TOO: [29]: 97 - [1693218196.393362][13451:13453] CHIP:TOO: [30]: 113 - [1693218196.393373][13451:13453] CHIP:TOO: [31]: 114 - [1693218196.393384][13451:13453] CHIP:TOO: [32]: 257 - [1693218196.393394][13451:13453] CHIP:TOO: [33]: 258 - [1693218196.393405][13451:13453] CHIP:TOO: [34]: 259 - [1693218196.393416][13451:13453] CHIP:TOO: [35]: 512 - [1693218196.393427][13451:13453] CHIP:TOO: [36]: 513 - [1693218196.393437][13451:13453] CHIP:TOO: [37]: 514 - [1693218196.393448][13451:13453] CHIP:TOO: [38]: 516 - [1693218196.393459][13451:13453] CHIP:TOO: [39]: 768 - [1693218196.393470][13451:13453] CHIP:TOO: [40]: 769 - [1693218196.393481][13451:13453] CHIP:TOO: [41]: 1024 - [1693218196.393492][13451:13453] CHIP:TOO: [42]: 1026 - [1693218196.393503][13451:13453] CHIP:TOO: [43]: 1027 - [1693218196.393514][13451:13453] CHIP:TOO: [44]: 1028 - [1693218196.393525][13451:13453] CHIP:TOO: [45]: 1029 - [1693218196.393536][13451:13453] CHIP:TOO: [46]: 1030 - [1693218196.393546][13451:13453] CHIP:TOO: [47]: 1036 - [1693218196.393557][13451:13453] CHIP:TOO: [48]: 1037 - [1693218196.393568][13451:13453] CHIP:TOO: [49]: 1043 - [1693218196.393579][13451:13453] CHIP:TOO: [50]: 1045 - [1693218196.393590][13451:13453] CHIP:TOO: [51]: 1066 - [1693218196.393601][13451:13453] CHIP:TOO: [52]: 1067 - [1693218196.393611][13451:13453] CHIP:TOO: [53]: 1068 - [1693218196.393622][13451:13453] CHIP:TOO: [54]: 1069 - [1693218196.393633][13451:13453] CHIP:TOO: [55]: 1070 - [1693218196.393643][13451:13453] CHIP:TOO: [56]: 1071 - [1693218196.393654][13451:13453] CHIP:TOO: [57]: 1283 - [1693218196.393664][13451:13453] CHIP:TOO: [58]: 1284 - [1693218196.393675][13451:13453] CHIP:TOO: [59]: 1285 - [1693218196.393686][13451:13453] CHIP:TOO: [60]: 1286 - [1693218196.393697][13451:13453] CHIP:TOO: [61]: 1287 - [1693218196.393708][13451:13453] CHIP:TOO: [62]: 1288 - [1693218196.393718][13451:13453] CHIP:TOO: [63]: 1289 - [1693218196.393729][13451:13453] CHIP:TOO: [64]: 1290 - [1693218196.393740][13451:13453] CHIP:TOO: [65]: 1291 - [1693218196.393750][13451:13453] CHIP:TOO: [66]: 1292 - [1693218196.393761][13451:13453] CHIP:TOO: [67]: 1293 - [1693218196.393772][13451:13453] CHIP:TOO: [68]: 1294 - [1693218196.393783][13451:13453] CHIP:TOO: [69]: 2820 - [1693218196.393794][13451:13453] CHIP:TOO: [70]: 4294048773 + Verify ServerList entries on the TH (Chip-tool) and below is the sample log provided for the raspi platform, + + [1707996554.409850][20755:20757] CHIP:DMG: } + [1707996554.410814][20755:20757] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_001D Attribute 0x0000_0001 DataVersion: 3583190746 + [1707996554.410955][20755:20757] CHIP:TOO: ServerList: 71 entries + [1707996554.410990][20755:20757] CHIP:TOO: [1]: 3 + [1707996554.411002][20755:20757] CHIP:TOO: [2]: 4 + [1707996554.411013][20755:20757] CHIP:TOO: [3]: 6 + [1707996554.411024][20755:20757] CHIP:TOO: [4]: 7 + [1707996554.411034][20755:20757] CHIP:TOO: [5]: 8 + [1707996554.411045][20755:20757] CHIP:TOO: [6]: 15 + [1707996554.411056][20755:20757] CHIP:TOO: [7]: 29 + [1707996554.411067][20755:20757] CHIP:TOO: [8]: 30 + [1707996554.411078][20755:20757] CHIP:TOO: [9]: 37 + [1707996554.411092][20755:20757] CHIP:TOO: [10]: 47 + [1707996554.411103][20755:20757] CHIP:TOO: [11]: 59 + [1707996554.411113][20755:20757] CHIP:TOO: [12]: 64 + [1707996554.411124][20755:20757] CHIP:TOO: [13]: 65 + [1707996554.411135][20755:20757] CHIP:TOO: [14]: 69 + [1707996554.411146][20755:20757] CHIP:TOO: [15]: 72 + [1707996554.411156][20755:20757] CHIP:TOO: [16]: 73 + [1707996554.411167][20755:20757] CHIP:TOO: [17]: 74 + [1707996554.411177][20755:20757] CHIP:TOO: [18]: 80 + [1707996554.411188][20755:20757] CHIP:TOO: [19]: 81 + [1707996554.411199][20755:20757] CHIP:TOO: [20]: 82 + [1707996554.411209][20755:20757] CHIP:TOO: [21]: 83 + [1707996554.411220][20755:20757] CHIP:TOO: [22]: 84 + [1707996554.411231][20755:20757] CHIP:TOO: [23]: 85 + [1707996554.411240][20755:20757] CHIP:TOO: [24]: 86 + [1707996554.411251][20755:20757] CHIP:TOO: [25]: 87 + [1707996554.411261][20755:20757] CHIP:TOO: [26]: 89 + [1707996554.411271][20755:20757] CHIP:TOO: [27]: 91 + [1707996554.411282][20755:20757] CHIP:TOO: [28]: 92 + [1707996554.411293][20755:20757] CHIP:TOO: [29]: 93 + [1707996554.411303][20755:20757] CHIP:TOO: [30]: 94 + [1707996554.411313][20755:20757] CHIP:TOO: [31]: 96 + [1707996554.411323][20755:20757] CHIP:TOO: [32]: 97 + [1707996554.411334][20755:20757] CHIP:TOO: [33]: 98 + [1707996554.411345][20755:20757] CHIP:TOO: [34]: 113 + [1707996554.411355][20755:20757] CHIP:TOO: [35]: 114 + [1707996554.411367][20755:20757] CHIP:TOO: [36]: 128 + [1707996554.411376][20755:20757] CHIP:TOO: [37]: 129 + [1707996554.411387][20755:20757] CHIP:TOO: [38]: 144 + [1707996554.411396][20755:20757] CHIP:TOO: [39]: 145 + [1707996554.411406][20755:20757] CHIP:TOO: [40]: 152 + [1707996554.411417][20755:20757] CHIP:TOO: [41]: 153 + [1707996554.411427][20755:20757] CHIP:TOO: [42]: 157 + [1707996554.411437][20755:20757] CHIP:TOO: [43]: 159 + [1707996554.411449][20755:20757] CHIP:TOO: [44]: 258 + [1707996554.411459][20755:20757] CHIP:TOO: [45]: 259 + [1707996554.411469][20755:20757] CHIP:TOO: [46]: 512 + [1707996554.411480][20755:20757] CHIP:TOO: [47]: 513 + [1707996554.411490][20755:20757] CHIP:TOO: [48]: 514 + [1707996554.411500][20755:20757] CHIP:TOO: [49]: 516 + [1707996554.411511][20755:20757] CHIP:TOO: [50]: 768 + [1707996554.411521][20755:20757] CHIP:TOO: [51]: 769 + [1707996554.411532][20755:20757] CHIP:TOO: [52]: 1024 + [1707996554.411559][20755:20757] CHIP:TOO: [53]: 1026 + [1707996554.411562][20755:20757] CHIP:TOO: [54]: 1027 + [1707996554.411565][20755:20757] CHIP:TOO: [55]: 1028 + [1707996554.411568][20755:20757] CHIP:TOO: [56]: 1029 + [1707996554.411571][20755:20757] CHIP:TOO: [57]: 1030 + [1707996554.411575][20755:20757] CHIP:TOO: [58]: 1036 + [1707996554.411578][20755:20757] CHIP:TOO: [59]: 1037 + [1707996554.411581][20755:20757] CHIP:TOO: [60]: 1043 + [1707996554.411584][20755:20757] CHIP:TOO: [61]: 1045 + [1707996554.411587][20755:20757] CHIP:TOO: [62]: 1066 + [1707996554.411589][20755:20757] CHIP:TOO: [63]: 1067 + [1707996554.411592][20755:20757] CHIP:TOO: [64]: 1068 + [1707996554.411595][20755:20757] CHIP:TOO: [65]: 1069 + [1707996554.411598][20755:20757] CHIP:TOO: [66]: 1070 + [1707996554.411601][20755:20757] CHIP:TOO: [67]: 1071 + [1707996554.411604][20755:20757] CHIP:TOO: [68]: 1283 + [1707996554.411607][20755:20757] CHIP:TOO: [69]: 1288 + [1707996554.411610][20755:20757] CHIP:TOO: [70]: 2820 + [1707996554.411613][20755:20757] CHIP:TOO: [71]: 4294048773 + ./chip-tool descriptor read server-list 1 2 @@ -233,6 +238,8 @@ tests: verification: | For all the Endpoint id’s listed in step 1a run the following steps. For all the client list entries listed in the output - Convert them to Hex values. For example 29 is 0x001D. Verify that these are also present in the device_type.json. Every server cluster listed in the JSON should correspond to a number here in the output. + The cluster ID's listed in the below log is from the All-Cluster-app. Please run the below command in all the Reference apps (bridge-app, tv-app, microwave-oven-app, Lock-app, Energy-Management-app and Thermostat-app). + ./chip-tool descriptor read client-list 1 1 Verify client list entries on the TH (Chip-tool) and below is the sample log provided for the raspi platform, Here ClientList entries are 1. @@ -242,7 +249,6 @@ tests: [1676367470.160282][9805:9807] CHIP:TOO: ClientList: 1 entries [1676367470.160289][9805:9807] CHIP:TOO: [1]: 6 - ./chip-tool descriptor read client-list 1 2 Verify client list entries on the TH (Chip-tool) and below is the sample log provided for the raspi platform, Here ClientList entries are 0. diff --git a/src/app/tests/suites/certification/Test_TC_EEVSEM_1_1.yaml b/src/app/tests/suites/certification/Test_TC_EEVSEM_1_1.yaml index ea416ee91e96b3..769dc5d3cba3ac 100644 --- a/src/app/tests/suites/certification/Test_TC_EEVSEM_1_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_EEVSEM_1_1.yaml @@ -48,9 +48,9 @@ tests: On the TH(Chip-tool) Log, Verify featureMap value is 0 and below is the sample log provided for the raspi platform: - [1705995388.110138][7525:7527] CHIP:DMG: } - [1705995388.110173][7525:7527] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_009D Attribute 0x0000_FFFC DataVersion: 1324786556 - [1705995388.110192][7525:7527] CHIP:TOO: FeatureMap: 1 + [1707803286.349129][12699:12701] CHIP:DMG: } + [1707803286.349183][12699:12701] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_009D Attribute 0x0000_FFFC DataVersion: 811903427 + [1707803286.349202][12699:12701] CHIP:TOO: FeatureMap: 0 cluster: "LogCommands" command: "UserPrompt" PICS: PICS_SKIP_SAMPLE_APP diff --git a/src/app/tests/suites/certification/Test_TC_G_3_2.yaml b/src/app/tests/suites/certification/Test_TC_G_3_2.yaml index 7f718a160bb9a0..bbafb43b2725fd 100644 --- a/src/app/tests/suites/certification/Test_TC_G_3_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_G_3_2.yaml @@ -17,6 +17,7 @@ name: 125.3.2. [TC-G-3.2] Groups Cluster Commands [DUT-Client] PICS: - G.C + - GRPKEY.C config: nodeId: 0x12344321 diff --git a/src/app/tests/suites/certification/Test_TC_ICDM_3_1.yaml b/src/app/tests/suites/certification/Test_TC_ICDM_3_1.yaml index 3fe5afe83a8510..365d820bccf00f 100644 --- a/src/app/tests/suites/certification/Test_TC_ICDM_3_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_ICDM_3_1.yaml @@ -35,6 +35,47 @@ tests: 2c.TH reads from the DUT the RegisteredClients attribute. Verify that the DUT response contains empty list of registered clients. disabled: true + - label: + "Step 0a: Preconfition 1: Read 'register-clients' by sending the + command below and note the check-in nodeID for the entries" + verification: | + ./chip-tool icdmanagement read registered-clients 1 0 + + [1704888897.027204][71644:71646] CHIP:DMG: } + [1704888897.027313][71644:71646] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0046 Attribute 0x0000_0003 DataVersion: 852105378 + [1704888897.027351][71644:71646] CHIP:TOO: RegisteredClients: 1 entries + [1704888897.027394][71644:71646] CHIP:TOO: [1]: { + [1704888897.027412][71644:71646] CHIP:TOO: CheckInNodeID: 112233 + [1704888897.027421][71644:71646] CHIP:TOO: MonitoredSubject: 112233 + [1704888897.027431][71644:71646] CHIP:TOO: FabricIndex: 1 + [1704888897.027440][71644:71646] CHIP:TOO: } + [1704888897.027521][71644:71646] CHIP:EM: <<< [E:49337i S:30873 M:176023643 (Ack:200282364)] (S) Msg TX to 1:0000000000000001 [5BF5] [UDP:[fe80::a70c:61dc:df51:6945%enxd03745ce8f62]:5540] --- Type 0000:10 (SecureChannel:StandaloneAck) + disabled: true + + - label: + "Step 0b: Preconfition 2: Please send the 'unregister client' command + using the check-in nodeID received from the previous read" + verification: | + ./chip-tool icdmanagement unregister-client 112233 1 0 + + [1704888949.629057][71657:71659] CHIP:DMG: + [1704888949.629066][71657:71659] CHIP:DMG: InteractionModelRevision = 11 + [1704888949.629074][71657:71659] CHIP:DMG: }, + [1704888949.629125][71657:71659] CHIP:DMG: Received Command Response Status for Endpoint=0 Cluster=0x0000_0046 Command=0x0000_0002 Status=0x0 + [1704888949.629153][71657:71659] CHIP:DMG: ICR moving to [AwaitingDe] + disabled: true + + - label: + "Step 0c: Preconfition 3: Verify that all entries have been + successfully unregistered by reading 'register-clients'" + verification: | + ./chip-tool icdmanagement read registered-clients 1 0 + [1704889092.945869][71700:71702] CHIP:DMG: } + [1704889092.945955][71700:71702] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0046 Attribute 0x0000_0003 DataVersion: 852105378 + [1704889092.945989][71700:71702] CHIP:TOO: RegisteredClients: 0 entries + [1704889092.946079][71700:71702] CHIP:EM: <<< [E:63454i S:39669 M:600516 (Ack:156383188)] (S) + disabled: true + - label: "Step 1: TH sends RegisterClient command. - CheckInNodeID: registering clients node ID - MonitoredSubject: monitored subject ID - Key: shared diff --git a/src/app/tests/suites/certification/Test_TC_LWM_2_1.yaml b/src/app/tests/suites/certification/Test_TC_LWM_2_1.yaml index b3535b13ceec51..a1641587411efa 100644 --- a/src/app/tests/suites/certification/Test_TC_LWM_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_LWM_2_1.yaml @@ -101,7 +101,6 @@ tests: command: "readAttribute" attribute: "CurrentMode" response: - saveAs: Step6_current_mode_dut constraints: type: int8u minValue: 0 diff --git a/src/app/tests/suites/certification/Test_TC_SU_2_3.yaml b/src/app/tests/suites/certification/Test_TC_SU_2_3.yaml index 09e18d01b69f9c..b913c30975d85b 100644 --- a/src/app/tests/suites/certification/Test_TC_SU_2_3.yaml +++ b/src/app/tests/suites/certification/Test_TC_SU_2_3.yaml @@ -119,11 +119,3 @@ tests: verification: | Out of scope disabled: true - - - label: - "Step 6: Perform the OTA Update on DUT using vendor specific - mechanism." - PICS: MCORE.OTA.VendorSpecific - verification: | - Use vendor specific steps to initiate OTA Update and verify that the software image is transferred to the DUT - disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_SU_2_5.yaml b/src/app/tests/suites/certification/Test_TC_SU_2_5.yaml index 60e55dc65e397b..f58d180b4170bf 100644 --- a/src/app/tests/suites/certification/Test_TC_SU_2_5.yaml +++ b/src/app/tests/suites/certification/Test_TC_SU_2_5.yaml @@ -157,11 +157,3 @@ tests: [1653636406.637617][11116:11121] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_000A DataVersion: 1527020963 [1653636406.637708][11116:11121] CHIP:TOO: SoftwareVersion: 1 disabled: true - - - label: - "Step 6: Apply the OTA Update on DUT using vendor specific mechanism." - PICS: MCORE.OTA.VendorSpecific - verification: | - Use vendor specific steps to apply OTA Update and verify that the DUT starts updating its software. - Once the update is finished verify the software version on the DUT to match the version downloaded for the software update. - disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_SU_3_3.yaml b/src/app/tests/suites/certification/Test_TC_SU_3_3.yaml index fe03bc98caeb3d..a4fad4cc9fbe35 100644 --- a/src/app/tests/suites/certification/Test_TC_SU_3_3.yaml +++ b/src/app/tests/suites/certification/Test_TC_SU_3_3.yaml @@ -121,11 +121,3 @@ tests: verification: | Out of scope disabled: true - - - label: - "Step 6: Perform the OTA Update from DUT using vendor specific - mechanism." - PICS: MCORE.OTA.VendorSpecific - verification: | - Use vendor specific steps to initiate OTA Update and verify that the software image is transferred from the DUT - disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_SU_4_2.yaml b/src/app/tests/suites/certification/Test_TC_SU_4_2.yaml deleted file mode 100644 index 409fdf5b82f1ec..00000000000000 --- a/src/app/tests/suites/certification/Test_TC_SU_4_2.yaml +++ /dev/null @@ -1,209 +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: - 31.15.1. [TC-SU-4.2] Tests for verifying cluster attributes from Admin(DUT) - -PICS: - - MCORE.ACL.Administrator - -config: - nodeId: 0x12344321 - cluster: "Basic Information" - endpoint: 0 - -tests: - - label: - "Step 1: DUT sends a write request for the DefaultOTAProviders - Attribute to the TH." - verification: | - Verify that the OTA Requestor App receives the write command and does not reject the value as invalid. - - ./chip-tool otasoftwareupdaterequestor write default-otaproviders '[{"fabricIndex": 1, "providerNodeID": 123, "endpoint": 0}]' 321 0 - - - Verify write request for the DefaultOTAProviders attribute on TH [OTA-REQ] Logs: - - [1662651310.444641][30167:30167] CHIP:IM: Received Write request - [1662651310.444820][30167:30167] CHIP:DMG: IM WH moving to [Initialized] - [1662651310.444952][30167:30167] CHIP:DMG: WriteRequestMessage = - [1662651310.445036][30167:30167] CHIP:DMG: { - [1662651310.445112][30167:30167] CHIP:DMG: suppressResponse = false, - [1662651310.445225][30167:30167] CHIP:DMG: timedRequest = false, - [1662651310.445335][30167:30167] CHIP:DMG: AttributeDataIBs = - [1662651310.445455][30167:30167] CHIP:DMG: [ - [1662651310.445565][30167:30167] CHIP:DMG: AttributeDataIB = - [1662651310.445698][30167:30167] CHIP:DMG: { - [1662651310.445826][30167:30167] CHIP:DMG: AttributePathIB = - [1662651310.445974][30167:30167] CHIP:DMG: { - [1662651310.446124][30167:30167] CHIP:DMG: Endpoint = 0x0, - [1662651310.446289][30167:30167] CHIP:DMG: Cluster = 0x2a, - [1662651310.446457][30167:30167] CHIP:DMG: Attribute = 0x0000_0000, - [1662651310.446620][30167:30167] CHIP:DMG: } - [1662651310.446772][30167:30167] CHIP:DMG: - [1662651310.446905][30167:30167] CHIP:DMG: Data = [ - [1662651310.447049][30167:30167] CHIP:DMG: - [1662651310.447158][30167:30167] CHIP:DMG: ], - [1662651310.447246][30167:30167] CHIP:DMG: }, - [1662651310.447338][30167:30167] CHIP:DMG: - [1662651310.447410][30167:30167] CHIP:DMG: AttributeDataIB = - [1662651310.447490][30167:30167] CHIP:DMG: { - [1662651310.447570][30167:30167] CHIP:DMG: AttributePathIB = - [1662651310.447661][30167:30167] CHIP:DMG: { - [1662651310.447754][30167:30167] CHIP:DMG: Endpoint = 0x0, - [1662651310.447854][30167:30167] CHIP:DMG: Cluster = 0x2a, - [1662651310.447955][30167:30167] CHIP:DMG: Attribute = 0x0000_0000, - [1662651310.448054][30167:30167] CHIP:DMG: ListIndex = Null, - [1662651310.448171][30167:30167] CHIP:DMG: } - [1662651310.448270][30167:30167] CHIP:DMG: - [1662651310.448360][30167:30167] CHIP:DMG: Data = - [1662651310.448449][30167:30167] CHIP:DMG: { - [1662651310.448540][30167:30167] CHIP:DMG: 0x1 = 123, - [1662651310.448641][30167:30167] CHIP:DMG: 0x2 = 0, - [1662651310.448742][30167:30167] CHIP:DMG: }, - [1662651310.448831][30167:30167] CHIP:DMG: }, - [1662651310.448913][30167:30167] CHIP:DMG: - [1662651310.448979][30167:30167] CHIP:DMG: ], - [1662651310.449053][30167:30167] CHIP:DMG: - [1662651310.449111][30167:30167] CHIP:DMG: moreChunkedMessages = false, - [1662651310.449178][30167:30167] CHIP:DMG: InteractionModelRevision = 1 - [1662651310.449244][30167:30167] CHIP:DMG: }, - [1662651310.449361][30167:30167] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_002A e=0 p=o - [1662651310.449426][30167:30167] CHIP:DMG: AccessControl: allowed - disabled: true - - - label: - "Step 2: DUT sends a read request to read the DefaultOTAProviders - Attribute to the TH." - verification: | - Verify that the OTA Requestor App responds to the read command - - ./chip-tool otasoftwareupdaterequestor read default-otaproviders 321 0 - - Verify read request for the DefaultOTAProviders attribute on TH [OTA-REQ] Logs: - [1662651381.708529][30167:30167] CHIP:IM: Received Read request - [1662651381.708619][30167:30167] CHIP:DMG: ReadRequestMessage = - [1662651381.708648][30167:30167] CHIP:DMG: { - [1662651381.708671][30167:30167] CHIP:DMG: AttributePathIBs = - [1662651381.708733][30167:30167] CHIP:DMG: [ - [1662651381.708762][30167:30167] CHIP:DMG: AttributePathIB = - [1662651381.708813][30167:30167] CHIP:DMG: { - [1662651381.708865][30167:30167] CHIP:DMG: Endpoint = 0x0, - [1662651381.708920][30167:30167] CHIP:DMG: Cluster = 0x2a, - [1662651381.708975][30167:30167] CHIP:DMG: Attribute = 0x0000_0000, - [1662651381.709027][30167:30167] CHIP:DMG: } - [1662651381.709079][30167:30167] CHIP:DMG: - [1662651381.709127][30167:30167] CHIP:DMG: ], - [1662651381.709159][30167:30167] CHIP:DMG: - [1662651381.709189][30167:30167] CHIP:DMG: isFabricFiltered = true, - disabled: true - - - label: - "Step 3: DUT sends a read request to read the UpdatePossible attribute - from the TH." - verification: | - Verify that the OTA Requestor App responds to the read command - - ./chip-tool otasoftwareupdaterequestor read update-possible 321 0 - - Verify UpdatePossible attribute on TH [OTA-REQ] Logs: - - [1662651426.055059][30167:30167] CHIP:IM: Received Read request - [1662651426.055180][30167:30167] CHIP:DMG: ReadRequestMessage = - [1662651426.055225][30167:30167] CHIP:DMG: { - [1662651426.055264][30167:30167] CHIP:DMG: AttributePathIBs = - [1662651426.055308][30167:30167] CHIP:DMG: [ - [1662651426.055349][30167:30167] CHIP:DMG: AttributePathIB = - [1662651426.055397][30167:30167] CHIP:DMG: { - [1662651426.055444][30167:30167] CHIP:DMG: Endpoint = 0x0, - [1662651426.055500][30167:30167] CHIP:DMG: Cluster = 0x2a, - [1662651426.055553][30167:30167] CHIP:DMG: Attribute = 0x0000_0001, - [1662651426.055603][30167:30167] CHIP:DMG: } - [1662651426.055654][30167:30167] CHIP:DMG: - [1662651426.055701][30167:30167] CHIP:DMG: ], - [1662651426.055747][30167:30167] CHIP:DMG: - disabled: true - - - label: - "Step 4: DUT sends a read request to read the UpdateState Attribute - from the TH." - verification: | - Verify that the OTA Requestor App responds to the read command - - ./chip-tool otasoftwareupdaterequestor read update-state 321 0 - - Verify UpdateState attribute on TH [OTA-REQ] Logs: - - [1662651459.324406][30167:30167] CHIP:IM: Received Read request - [1662651459.324545][30167:30167] CHIP:DMG: ReadRequestMessage = - [1662651459.324597][30167:30167] CHIP:DMG: { - [1662651459.324641][30167:30167] CHIP:DMG: AttributePathIBs = - [1662651459.324692][30167:30167] CHIP:DMG: [ - [1662651459.324739][30167:30167] CHIP:DMG: AttributePathIB = - [1662651459.324847][30167:30167] CHIP:DMG: { - [1662651459.324914][30167:30167] CHIP:DMG: Endpoint = 0x0, - [1662651459.324973][30167:30167] CHIP:DMG: Cluster = 0x2a, - [1662651459.325030][30167:30167] CHIP:DMG: Attribute = 0x0000_0002, - [1662651459.325083][30167:30167] CHIP:DMG: } - [1662651459.325138][30167:30167] CHIP:DMG: - [1662651459.325188][30167:30167] CHIP:DMG: ], - [1662651459.325240][30167:30167] CHIP:DMG: - disabled: true - - - label: - "Step 5: TH should start initiating the Software update process. While - the TH is downloading the image, DUT sends a read request to read the - UpdateStateProgress attribute from the TH." - verification: | - Write the acl entry to allow the software update: - - ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null}, {"fabricIndex": 1, "privilege": 3, "authMode": 2, "subjects": [321], "targets": null}]' 123 0 - - [1686306394.095355][30543:30545] CHIP:DMG: StatusIB = - [1686306394.095380][30543:30545] CHIP:DMG: { - [1686306394.095404][30543:30545] CHIP:DMG: status = 0x00 (SUCCESS), - [1686306394.095436][30543:30545] CHIP:DMG: }, - - Run the announce ota provider command to start the software update and check the UpdateStateProgress - - ./chip-tool otasoftwareupdaterequestor announce-otaprovider 123 0 0 0 321 0 - - where 321 is OTA Requestor node ID and 123 is OTA Provider node ID - - Verify that the OTA Requestor App responds to the read command - - ./chip-tool otasoftwareupdaterequestor read update-state-progress 321 0 - - Verify UpdateStateProgress attribute on TH [OTA-REQ] Logs: - - [1662651648.244248][30167:30167] CHIP:IM: Received Read request - [1662651648.244329][30167:30167] CHIP:DMG: ReadRequestMessage = - [1662651648.244353][30167:30167] CHIP:DMG: { - [1662651648.244372][30167:30167] CHIP:DMG: AttributePathIBs = - [1662651648.244399][30167:30167] CHIP:DMG: [ - [1662651648.244430][30167:30167] CHIP:DMG: AttributePathIB = - [1662651648.244457][30167:30167] CHIP:DMG: { - [1662651648.244492][30167:30167] CHIP:DMG: Endpoint = 0x0, - [1662651648.244523][30167:30167] CHIP:DMG: Cluster = 0x2a, - [1662651648.244558][30167:30167] CHIP:DMG: Attribute = 0x0000_0003, - [1662651648.244584][30167:30167] CHIP:DMG: } - [1662651648.244618][30167:30167] CHIP:DMG: - [1662651648.244643][30167:30167] CHIP:DMG: ], - [1662651648.244676][30167:30167] CHIP:DMG: - [1662651648.244700][30167:30167] CHIP:DMG: isFabricFiltered = true, - [1662651648.244721][30167:30167] CHIP:DMG: InteractionModelRevision = 1 - [1662651648.244749][30167:30167] CHIP:DMG: }, - [1662651648.244822][30167:30167] CHIP:DMG: IM RH moving to [GeneratingReports] - disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_S_2_3.yaml b/src/app/tests/suites/certification/Test_TC_S_2_3.yaml index 859204e549f7b2..b39a2e762a1113 100644 --- a/src/app/tests/suites/certification/Test_TC_S_2_3.yaml +++ b/src/app/tests/suites/certification/Test_TC_S_2_3.yaml @@ -309,11 +309,10 @@ tests: to G1, the SceneID field set to 0x01, the TransitionTime field set to 1000 (1s) and a set of extension fields appropriate to AC1." verification: | - ./chip-tool scenesmanagement add-scene GroupID SceneID TransitionTime "SceneName" '[{"clusterId": value, "attributeValueList":[{"attributeId": value, "attributeValue": value}]}' nodeId endpointId + ./chip-tool scenesmanagement add-scene 0x0101 0x01 1000 "scene name" '[{"clusterID": "0x0006", "attributeValueList":[{"attributeID": "0x0001", "attributeValue": "0x01"}, ]}, {"clusterID": "0x0008", "attributeValueList":[{"attributeID": "0x0000", "attributeValue": "0x64"}, ]}]' 1 1 - Note: The number of ExtensionFieldSets, the value of clusterId of each ExtensionFieldSet, the number of attributes in attributeValueList and their values varies for each application + Verify DUT sends a AddSceneResponse command to TH with the Status field set to 0x00 (SUCCESS), the GroupID field set to 257 and the SceneID field set to 0x01 on the TH(Chip-tool) Log and below is the sample log provided for the raspi platform: - Verify the "status is success" on the TH(Chip-tool) Log and below is the sample log provided for the raspi platform: [1705680175.863785][5823:5825] CHIP:DMG: }, [1705680175.863851][5823:5825] CHIP:DMG: Received Command Response Data, Endpoint=1 Cluster=0x0000_0062 Command=0x0000_0000 [1705680175.863880][5823:5825] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0062 Command 0x0000_0000 @@ -613,11 +612,12 @@ tests: set to G1 and the SceneID field set to 0x03." PICS: S.S.C01.Rsp && PICS_SKIP_SAMPLE_APP verification: | - ./chip-tool scenesmanagement view-scene GroupId SceneId Node-Id EndpointId + ./chip-tool scenesmanagement view-scene 0x0101 0x03 1 1 - Note: The number of ExtensionFieldSets, the value of clusterId of each ExtensionFieldSet, the number of attributes in attributeValueList and their values varies for each application + Verify DUT sends a ViewSceneResponse command to TH with the Status field set to 0x00 (SUCCESS), the GroupID field set to 257, the SceneID field set to 0x03, the TransitionTime field set to 1 and a set of extension fields appropriate to AC1 on the TH(Chip-tool) Log and below is the sample log provided for the raspi platform: + + NOTE: The values below are expected to match the values from the specific AC tested - Verify that the extension fields in the log match the ones expected and that the log output is similar to the following: [1707285444.028460][13682:13684] CHIP:DMG: }, [1707285444.028553][13682:13684] CHIP:DMG: Received Command Response Data, Endpoint=1 Cluster=0x0000_0062 Command=0x0000_0001 [1707285444.028579][13682:13684] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0062 Command 0x0000_0001 @@ -627,13 +627,13 @@ tests: [1707285444.028706][13682:13684] CHIP:TOO: sceneID: 3 [1707285444.028717][13682:13684] CHIP:TOO: transitionTime: 1 [1707285444.028728][13682:13684] CHIP:TOO: sceneName: scene name - [1707285444.028766][13682:13684] CHIP:TOO: extensionFieldSets: XX entries - [1707285444.028814][13682:13684] CHIP:TOO: [XX]: { - [1707285444.028828][13682:13684] CHIP:TOO: ClusterID: XX - [1707285444.028853][13682:13684] CHIP:TOO: AttributeValueList: XX entries - [1707285444.028882][13682:13684] CHIP:TOO: [XX]: { - [1707285444.028896][13682:13684] CHIP:TOO: AttributeID: XX - [1707285444.028913][13682:13684] CHIP:TOO: AttributeValue: XX + [1707285444.028766][13682:13684] CHIP:TOO: extensionFieldSets: 1 entries + [1707285444.028814][13682:13684] CHIP:TOO: [1]: { + [1707285444.028828][13682:13684] CHIP:TOO: ClusterID: 768 + [1707285444.028853][13682:13684] CHIP:TOO: AttributeValueList: 1 entries + [1707285444.028882][13682:13684] CHIP:TOO: [1]: { + [1707285444.028896][13682:13684] CHIP:TOO: AttributeID: 16386 + [1707285444.028913][13682:13684] CHIP:TOO: AttributeValue: 1 [1707285444.028925][13682:13684] CHIP:TOO: } [1707285444.028937][13682:13684] CHIP:TOO: } [1707285444.028950][13682:13684] CHIP:TOO: } diff --git a/src/app/tests/suites/certification/Test_TC_S_2_4.yaml b/src/app/tests/suites/certification/Test_TC_S_2_4.yaml index c3ba72dcf05b80..196d08a4eb46cf 100644 --- a/src/app/tests/suites/certification/Test_TC_S_2_4.yaml +++ b/src/app/tests/suites/certification/Test_TC_S_2_4.yaml @@ -440,7 +440,7 @@ tests: response: value: 100 - - label: "DUT transitions to AC2 over 20." + - label: "DUT transitions to AC1 over 20s." verification: | Is the transition done over 20s? cluster: "LogCommands" @@ -449,7 +449,7 @@ tests: arguments: values: - name: "message" - value: "Please confirm that transition to AC2 was made over 5s" + value: "Please confirm that transition to AC1 was made over 20s" - name: "expectedValue" value: "y" diff --git a/src/app/tests/suites/certification/Test_TC_S_2_5.yaml b/src/app/tests/suites/certification/Test_TC_S_2_5.yaml index e0a2998e06d965..8616c15665531e 100644 --- a/src/app/tests/suites/certification/Test_TC_S_2_5.yaml +++ b/src/app/tests/suites/certification/Test_TC_S_2_5.yaml @@ -17,7 +17,6 @@ name: 132.2.5. [TC-S-2.5] RemainingCapacity functionality with DUT as Server PICS: - S.S - - S.S.F03 config: nodeId: 0x12344321 @@ -250,7 +249,7 @@ tests: to 20000 (20s) and no extension field sets." PICS: S.S.C00.Rsp verification: | - ./chip-tool scenesmanagement add-scene 0x0001 0x01 20000 scene1 [] 1 1 + scenesmanagement add-scene 0x0001 0x01 20000 scene1 [] 1 1 Verify the AddSceneResponse with following fields: Status is SUCCESS @@ -331,7 +330,7 @@ tests: 8a." PICS: S.S.C04.Rsp verification: | - ./chiptool scenesmanagement store-scene 0x0001 0x02 1 1 + scenesmanagement store-scene 0x0001 0x02 1 1 Verify the StoreSceneResponse with following fields: Status is SUCCESS @@ -412,7 +411,7 @@ tests: field sets. If RemainingCapacity is 0, continue to Step 8a." PICS: S.S.C00.Rsp verification: | - ./chip-tool scenesmanagement add-scene 0x0001 0x03 20000 scene1 [] 1 1 + scenesmanagement add-scene 0x0001 0x03 20000 scene1 [] 1 1 Verify the AddSceneResponse with following fields: Status is SUCCESS @@ -491,7 +490,7 @@ tests: set to G1 and the SceneID field set to 0x01." PICS: S.S.C02.Rsp verification: | - ./chip-tool scenesmanagement remove-scene 0x0001 0x01 1 1 + scenesmanagement remove-scene 0x0001 0x01 1 1 Verify the RemoveScenesResponse with following fields: Status is SUCCESS @@ -646,7 +645,7 @@ tests: KeySetRemove command to the GroupKeyManagement cluster with the GroupKeySetID field set to 0x01a1" verification: | - ./chip-tool groupkeymanagement key-set-remove 0x01a1 1 0 + groupkeymanagement key-set-remove 0x01a1 1 0 Verify DUT responds with SUCCESS status response on the TH(Chip-tool) Log and below is the sample log provided for the raspi platform: diff --git a/src/app/tests/suites/certification/Test_TC_S_2_6.yaml b/src/app/tests/suites/certification/Test_TC_S_2_6.yaml index 2c8d0ce4e5a820..5a578eeb8a7866 100644 --- a/src/app/tests/suites/certification/Test_TC_S_2_6.yaml +++ b/src/app/tests/suites/certification/Test_TC_S_2_6.yaml @@ -19,7 +19,6 @@ name: PICS: - S.S - - S.S.F03 config: nodeId: 0x12344321 @@ -30,7 +29,7 @@ tests: - label: "Precondition: Commission DUT to TH1" verification: | Once DUT reach the commissionable state send the following command on TH1: - ./chip-tool pairing onnetwork 1 20202021 + pairing onnetwork 1 20202021 Verify the commissioning completed with success on TH(chip-tool) from DUT [1650455358.501816][4366:4371] CHIP:TOO: Device commissioning completed with success disabled: true @@ -39,7 +38,7 @@ tests: verification: | Open a commissioning window On TH1(Chiptool)using below command - ./chip-tool pairing open-commissioning-window 1 1 400 2000 3841 + pairing open-commissioning-window 1 1 400 2000 3841 Verify the Successfully opened pairing window On TH1(Chiptool)e device @@ -53,7 +52,7 @@ tests: verification: | Now send the below command for commissionin DUT to TH2 with Manual pairing code generated in TH1 using open commission window - ./chip-tool pairing code 2 36253605617 --commissioner-name beta + pairing code 2 36253605617 --commissioner-name beta Verify the commissioning completed with success on TH2(chip-tool) from DUT @@ -65,7 +64,7 @@ tests: verification: | Open a commissioning window On TH1(Chiptool)using below command - ./chip-tool pairing open-commissioning-window 1 1 400 2000 3842 + pairing open-commissioning-window 1 1 400 2000 3842 Verify the Successfully opened pairing window On TH1(Chiptool)e device @@ -79,7 +78,7 @@ tests: verification: | send the below command for commissionin DUT to TH3 with Manual pairing code generated in TH1 using open commission window - ./chip-tool pairing code 3 36545248276 --commissioner-name gamma + pairing code 3 36545248276 --commissioner-name gamma Verify the commissioning completed with success on TH3(chip-tool) from DUT @@ -92,7 +91,7 @@ tests: field set to 0x0000." PICS: S.S.C03.Rsp verification: | - ./chip-tool scenesmanagement remove-all-scenes 0x0000 1 1 + scenesmanagement remove-all-scenes 0x0000 1 1 Verify the RemoveAllScenesResponse with following fields: Status is SUCCESS @@ -108,7 +107,7 @@ tests: - label: "Step 1b: Repeat Step 1a with TH2." PICS: S.S.C03.Rsp verification: | - ./chip-tool scenesmanagement remove-all-scenes 0x0000 2 1 --commissioner-name beta + scenesmanagement remove-all-scenes 0x0000 2 1 --commissioner-name beta Verify the RemoveAllScenesResponse with following fields: Status is SUCCESS @@ -125,7 +124,7 @@ tests: - label: "Step 1C: Repeat Step 1a with TH3." PICS: S.S.C03.Rsp verification: | - ./chip-tool scenesmanagement remove-all-scenes 0x0000 3 1 --commissioner-name gamma + scenesmanagement remove-all-scenes 0x0000 3 1 --commissioner-name gamma Verify the RemoveAllScenesResponse with following fields: Status is SUCCESS @@ -141,7 +140,7 @@ tests: - label: "Step 2a: TH1 reads from the DUT the SceneTableSize attribute" verification: | - ./chip-tool scenesmanagement read scene-table-size 1 1 + scenesmanagement read scene-table-size 1 1 Verify the "SceneTableSize" attribute value is SceneTableSize(minimum=16) which is recorded into SceneTableSize on the TH (Chip-tool) and below is the sample log provided for the raspi platform: @@ -156,7 +155,7 @@ tests: verification: | Please use Interactive mode to Verify the subscription Here the command to enter interactive mode:-- - ./chip-tool interactive start + interactive start Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully @@ -236,7 +235,7 @@ tests: Please use Interactive mode to Verify the subscription of an event Here the command to enter interactive mode:-- - ./chip-tool interactive start + interactive start Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully @@ -296,7 +295,7 @@ tests: verification: | Please use Interactive mode to Verify the subscription of an event Here the command to enter interactive mode:-- - ./chip-tool interactive start + interactive start Set up the subscription between DUT and TH by sending the command mentioned below, and verify that the subscription is activated successfully @@ -358,7 +357,7 @@ tests: set to 20000 (20s) and no extension field sets." PICS: S.S.C00.Rsp verification: | - ./chip-tool scenesmanagement add-scene 0x0000 0x01 20000 scene1 [] 1 1 + scenesmanagement add-scene 0x0000 0x01 20000 scene1 [] 1 1 Verify the AddSceneResponse with following fields: Status is SUCCESS @@ -381,7 +380,7 @@ tests: FabricSceneInfo into Remaining1stCapacity; verify Remaining1stCapacity equals (MaxRemainingCapacity-1)." verification: | - ./chipt-tool scenesmanagement subscribe fabric-scene-info 100 200 1 1 + scenesmanagement subscribe fabric-scene-info 100 200 1 1 Verify the DUT sends a report data to TH1 for FabricSceneInfo after the MinIntervalFloor time; store the RemainingCapacity field from this fabric’s entry reported in FabricSceneInfo into Remaining1stCapacity and is equals to (MaxRemainingCapacity-1) on the TH (Chip-tool) and below is the sample log provided for the raspi platform: @@ -441,7 +440,7 @@ tests: becomes 0." PICS: S.S.C00.Rsp verification: | - ./chip-tool scenesmanagement add-scene 0x0000 0x02 20000 scene2 [] 1 1 + scenesmanagement add-scene 0x0000 0x02 20000 scene2 [] 1 1 Verify the AddSceneResponse with following fields: Status is SUCCESS @@ -457,7 +456,7 @@ tests: [1700827508.579697][16026:16028] CHIP:TOO: } - ./chip-tool scenesmanagement subscribe fabric-scene-info 100 200 1 1 + scenesmanagement subscribe fabric-scene-info 100 200 1 1 Verify the DUT sends a report data messages after the MinIntervalFloor time to TH1 for RemainingCapacity field in FabricSceneInfo for that fabric with updated valueon the TH1 (Chip-tool) and below is the sample log provided for the raspi platform: [1701243677.717829][7642:7644] CHIP:DMG: ReportDataMessage = [1701243677.717834][7642:7644] CHIP:DMG: { @@ -508,7 +507,7 @@ tests: . . . - ./chip-tool scenesmanagement add-scene 0x0000 0x07 20000 scene8 [] 1 1 + scenesmanagement add-scene 0x0000 0x07 20000 scene8 [] 1 1 Verify the AddSceneResponse with following fields: Status is SUCCESS @@ -524,7 +523,7 @@ tests: [1700827941.415498][16068:16070] CHIP:TOO: sceneID: 7 [1700827941.415508][16068:16070] CHIP:TOO: } - ./chip-tool scenesmanagement subscribe fabric-scene-info 100 200 1 1 + scenesmanagement subscribe fabric-scene-info 100 200 1 1 Verify the DUT sends a report data messages after the MinIntervalFloor time to TH1 for RemainingCapacity field in FabricSceneInfo for that fabric with updated valueon the TH1 (Chip-tool) and below is the sample log provided for the raspi platform: @@ -583,7 +582,7 @@ tests: field sets." PICS: S.S.C00.Rsp verification: | - ./chip-tool scenesmanagement add-scene 0x0000 0x08 20000 scene9 [] 1 1 + scenesmanagement add-scene 0x0000 0x08 20000 scene9 [] 1 1 Verify the AddSceneResponse with following fields: Status is RESOURCE_EXHAUSTED(0x89) on the TH1(Chip-tool) log and below is the sample log provided for the raspi platform: @@ -601,7 +600,7 @@ tests: - label: "Step 5a: Repeat Step 4a with TH2" PICS: S.S.C00.Rsp verification: | - ./chip-tool scenesmanagement add-scene 0x0000 0x02 0x0014 scene1 [] 2 1 --commissioner-name beta + scenesmanagement add-scene 0x0000 0x02 0x0014 scene1 [] 2 1 --commissioner-name beta Verify the AddSceneResponse with following fields: Status is SUCCESS @@ -617,7 +616,7 @@ tests: [1700828173.261638][16115:16117] CHIP:TOO: sceneID: 2 [1700828173.261640][16115:16117] CHIP:TOO: } - ./chip-tool scenesmanagement subscribe fabric-scene-info 100 200 2 1 --commissioner-name beta + scenesmanagement subscribe fabric-scene-info 100 200 2 1 --commissioner-name beta Verify the DUT sends a report data messages after the MinIntervalFloor time to TH2 for RemainingCapacity field in FabricSceneInfo for that fabric with updated value on the TH2 (Chip-tool) and below is the sample log provided for the raspi platform: @@ -670,7 +669,7 @@ tests: . . . - ./chip-tool scenesmanagement add-scene 0x0000 0x08 0x0014 scene7 [] 2 1 --commissioner-name beta + scenesmanagement add-scene 0x0000 0x08 0x0014 scene7 [] 2 1 --commissioner-name beta Verify the AddSceneResponse with following fields: Status is SUCCESS @@ -685,7 +684,7 @@ tests: [1700829509.052521][16198:16200] CHIP:TOO: sceneID: 8 [1700829509.052532][16198:16200] CHIP:TOO: } - ./chip-tool scenesmanagement subscribe fabric-scene-info 100 200 2 1 --commissioner-name beta + scenesmanagement subscribe fabric-scene-info 100 200 2 1 --commissioner-name beta Verify the DUT sends a report data messages after the MinIntervalFloor time to TH2 for RemainingCapacity field in FabricSceneInfo for that fabric with updated value(decreasing to 0) on the TH2 (Chip-tool) and below is the sample log provided for the raspi platform: @@ -736,7 +735,7 @@ tests: [1701245132.870584][7824:7826] CHIP:TOO: FabricIndex: 2 [1701245132.870594][7824:7826] CHIP:TOO: } - ./chip-tool scenesmanagement subscribe fabric-scene-info 100 200 3 1 --commissioner-name gamma + scenesmanagement subscribe fabric-scene-info 100 200 3 1 --commissioner-name gamma Verify that the DUT sends report data messages after the MinIntervalFloor time to TH3 for RemainingCapacity field in FabricSceneInfo for that fabric with updated value (decreasing to SceneTableSize - (2 * MaxRemainingCapacity)) on the TH2 (Chip-tool) and below is the sample log provided for the raspi platform: @@ -791,7 +790,7 @@ tests: - label: "Step 5b: Repeat Step 4b with TH2" PICS: S.S.C00.Rsp verification: | - ./chip-tool scenesmanagement add-scene 0x0000 0x09 0x0014 scene8 [] 2 1 --commissioner-name beta + scenesmanagement add-scene 0x0000 0x09 0x0014 scene8 [] 2 1 --commissioner-name beta Verify the AddSceneResponse with following fields: Status is RESOURCE_EXHAUSTED(0x89) on the TH2(Chip-tool) log and below is the sample log provided for the raspi platform: @@ -808,7 +807,7 @@ tests: - label: "Step 6a: Repeat Step 4a with TH3" PICS: S.S.C00.Rsp verification: | - ./chip-tool scenesmanagement add-scene 0x0000 0x02 0x0014 scene1 [] 3 1 --commissioner-name gamma + scenesmanagement add-scene 0x0000 0x02 0x0014 scene1 [] 3 1 --commissioner-name gamma Verify the AddSceneResponse with following fields: Status is SUCCESS @@ -951,7 +950,7 @@ tests: set to 20000 20s and no extension field sets." PICS: S.S.C00.Rsp verification: | - ./chipt-tool scenesmanagement add-scene 0x0000 0x01 20000 scene [] 3 1 --commissioner-name gamma + scenesmanagement add-scene 0x0000 0x01 20000 scene [] 3 1 --commissioner-name gamma Verify the AddSceneResponse with following fields: Status is RESOURCE_EXHAUSTED(0x89) on the TH3(Chip-tool) log and below is the sample log provided for the raspi platform: @@ -971,7 +970,7 @@ tests: set to 0x0000, the SceneID field set to 0x01." PICS: S.S.C04.Rsp verification: | - ./chipt-tool scenesmanagement store-scene 0x0000 0x01 3 1 --commissioner-name gamma + scenesmanagement store-scene 0x0000 0x01 3 1 --commissioner-name gamma Verify the StoreSceneResponse with following fields: Status is RESOURCE_EXHAUSTED(0x89) on the TH3(Chip-tool) log and below is the sample log provided for the raspi platform: @@ -993,7 +992,7 @@ tests: to 0x0000 and the scene identifier to field set to 0xFE." PICS: S.S.C40.Rsp verification: | - ./chipt-tool scenesmanagement copy-scene 0x00 0x0000 0x02 0x0000 0x00 3 1 --commissioner-name gamma + scenesmanagement copy-scene 0x00 0x0000 0x02 0x0000 0x00 3 1 --commissioner-name gamma Verify the CopySceneResponse with following fields: Status is RESOURCE_EXHAUSTED(0x89) on the TH(Chip-tool) log and below is the sample log provided for the raspi platform: @@ -1013,7 +1012,7 @@ tests: field set to 0x0000." PICS: S.S.C03.Rsp verification: | - ./chipt-tool scenesmanagement remove-all-scenes 0x0000 1 1 + scenesmanagement remove-all-scenes 0x0000 1 1 Verify the RemoveAllScenesResponse with following fields: Status is SUCCESS @@ -1038,7 +1037,7 @@ tests: should send 'empty' report data since there is no update for this attribute for TH2)." verification: | - ./chipt-tool scenesmanagement subscribe fabric-scene-info 100 200 1 1 + scenesmanagement subscribe fabric-scene-info 100 200 1 1 Verify that the DUT sends a report data to TH1 for FabricSceneInfo after the MinIntervalFloor time; store the RemainingCapacity field from this fabric’s entry the reported in FabricSceneInfo into Remaining1stCapacity; verify Remaining1stCapacity equals (MaxRemainingCapacity) on TH1(Chip-tool) log and below is the sample log provided for the raspi platform: @@ -1097,7 +1096,7 @@ tests: field set to 0x0000." PICS: S.S.C03.Rsp verification: | - ./chipt-tool scenesmanagement remove-all-scenes 0x0000 2 1 --commissioner-name beta + scenesmanagement remove-all-scenes 0x0000 2 1 --commissioner-name beta Verify the RemoveAllScenesResponse with following fields: Status is SUCCESS @@ -1119,7 +1118,7 @@ tests: FabricSceneInfo into Remaining2ndCapacity; verify Remaining2ndCapacity equals (MaxRemainingCapacity)." verification: | - ./chip-tool scenesmanagement subscribe fabric-scene-info 100 200 2 1 --commissioner-name beta + scenesmanagement subscribe fabric-scene-info 100 200 2 1 --commissioner-name beta Verify that the DUT sends a report data to TH2 for FabricSceneInfo after the MinIntervalFloor time; store the RemainingCapacity field from this fabric’s entry reported in FabricSceneInfo into Remaining2ndCapacity; verify Remaining2ndCapacity equals (MaxRemainingCapacity) on TH2(Chip-tool) log and below is the sample log provided for the raspi platform: @@ -1141,7 +1140,7 @@ tests: "Step 11a: TH1 removes the TH2 fabric by sending the RemoveFabric command to the DUT with the FabricIndex set to th2FabricIndex" verification: | - ./chip-tool operationalcredentials remove-fabric th2FabricIndex 1 0 + operationalcredentials remove-fabric th2FabricIndex 1 0 On TH1(chip-tool) verify the success with the nocresponse with statuscode is success(0) @@ -1158,7 +1157,7 @@ tests: "Step 11b: TH1 removes the TH3 fabric by sending the RemoveFabric command to the DUT with the FabricIndex set to th3FabricIndex" verification: | - ./chip-tool operationalcredentials remove-fabric th3FabricIndex 1 0 + operationalcredentials remove-fabric th3FabricIndex 1 0 On TH1(chip-tool) verify the success with the nocresponse with statuscode is success(0) diff --git a/src/app/tests/suites/certification/Test_TC_S_3_1.yaml b/src/app/tests/suites/certification/Test_TC_S_3_1.yaml index 66912006363345..ffb3023c67b862 100644 --- a/src/app/tests/suites/certification/Test_TC_S_3_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_S_3_1.yaml @@ -154,16 +154,34 @@ tests: - label: "Step 0d: Precondition 4: TH sends a RemoveAllGroups command to DUT." verification: | - Please execute the below commands before starting the test case : - ./chip-tool groups remove-all-groups 1 1 - Verify DUT responds with SUCCESS status response on the TH(Chip-tool) Log and below is the sample log provided for the raspi platform: - - [1653485455.344097][11508:11513] CHIP:DMG: StatusIB = - [1653485455.344141][11508:11513] CHIP:DMG: { - [1653485455.344190][11508:11513] CHIP:DMG: status = 0x00 (SUCCESS), - [1653485455.344236][11508:11513] CHIP:DMG: }, + Verify the RemoveAllGroups attribute On TH (all-Clusters-app) log and below is the sample log provided for the raspi platform: + + [1707992121.754676][18074:18074] CHIP:DMG: InvokeRequestMessage = + [1707992121.754689][18074:18074] CHIP:DMG: { + [1707992121.754697][18074:18074] CHIP:DMG: suppressResponse = false, + [1707992121.754707][18074:18074] CHIP:DMG: timedRequest = false, + [1707992121.754714][18074:18074] CHIP:DMG: InvokeRequests = + [1707992121.754730][18074:18074] CHIP:DMG: [ + [1707992121.754744][18074:18074] CHIP:DMG: CommandDataIB = + [1707992121.754756][18074:18074] CHIP:DMG: { + [1707992121.754766][18074:18074] CHIP:DMG: CommandPathIB = + [1707992121.754776][18074:18074] CHIP:DMG: { + [1707992121.754788][18074:18074] CHIP:DMG: EndpointId = 0x1, + [1707992121.754801][18074:18074] CHIP:DMG: ClusterId = 0x4, + [1707992121.754810][18074:18074] CHIP:DMG: CommandId = 0x4, + [1707992121.754827][18074:18074] CHIP:DMG: }, + [1707992121.754841][18074:18074] CHIP:DMG: + [1707992121.754852][18074:18074] CHIP:DMG: CommandFields = + [1707992121.754863][18074:18074] CHIP:DMG: { + [1707992121.754874][18074:18074] CHIP:DMG: }, + [1707992121.754883][18074:18074] CHIP:DMG: }, + [1707992121.754899][18074:18074] CHIP:DMG: + [1707992121.754907][18074:18074] CHIP:DMG: ], + [1707992121.754924][18074:18074] CHIP:DMG: + [1707992121.754934][18074:18074] CHIP:DMG: InteractionModelRevision = 11 + [1707992121.754943][18074:18074] CHIP:DMG: }, disabled: true - label: