diff --git a/src/app/tests/suites/certification/PICS.yaml b/src/app/tests/suites/certification/PICS.yaml index de8d60c6fa20f5..09db826072c0f1 100644 --- a/src/app/tests/suites/certification/PICS.yaml +++ b/src/app/tests/suites/certification/PICS.yaml @@ -30,9 +30,6 @@ PICS: - label: "Does the device support manufacturing date" id: MANF_DATE - - label: "Does the device support part number" - id: PART_NUM - - label: "Does the device support Intermediate CA Certificate" id: DM_ICACERT diff --git a/src/app/tests/suites/certification/Test_TC_ACT_3_1.yaml b/src/app/tests/suites/certification/Test_TC_ACT_3_1.yaml index 7cdb52289f63a8..9bbfbe56d38ea5 100644 --- a/src/app/tests/suites/certification/Test_TC_ACT_3_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_ACT_3_1.yaml @@ -64,7 +64,7 @@ tests: - ./chip-tool actions read endpoint-list 1 1 + ./chip-tool actions read endpoint-lists 1 1 Verify read command is received on TH(all-clusters-app ) @@ -157,7 +157,7 @@ tests: [1658393025.603258][13481:13486] CHIP:EM: Sending Standalone Ack for MessageCounter:114510707 on exchange 23501i - ./chip-tool bridgedactions read action-list 1 1 + ./chip-tool actions read action-list 1 1 Verify read command is received on TH(all-clusters-minimal-app) Log @@ -184,7 +184,7 @@ tests: - ./chip-tool bridgedactions read endpoint-list 1 1 + ./chip-tool actions read endpoint-lists 1 1 Verify read command is received on TH(all-clusters-minimal-app) diff --git a/src/app/tests/suites/certification/Test_TC_ACT_3_2.yaml b/src/app/tests/suites/certification/Test_TC_ACT_3_2.yaml index 83653e623e23ba..d5bcb1a0514275 100644 --- a/src/app/tests/suites/certification/Test_TC_ACT_3_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_ACT_3_2.yaml @@ -31,22 +31,49 @@ tests: - label: "Preparation: TH as server exposes an Actions server cluster on EP 1, - with one action (supporting all possible commands) and corresponding - ActionLists and EndpointLists attributes: ActionList: contains one - list element (ActionListStruct): ActionIO = 0x1001 Name = some - test Type = other EndpointListID = 0xE001 SupportedCommands = - 0x0fff // suppports all commands State = Inactive EndpointLists: - contains one list element (EndpointListStruct): EndpointListID = - 0xE001 Name = test room Type = room Endpoints = - [3] SetupURL: (empty string)" + with one action (supporting all possible commands) and corresponding + ActionLists and EndpointLists attributes: ActionList: contains one + list element (ActionListStruct): ActionIO = 0x1001 Name = some + test Type = other EndpointListID = 0xE001 SupportedCommands = + 0x0fff // suppports all commands State = Inactive EndpointLists: + contains one list element (EndpointListStruct): EndpointListID = + 0xE001 Name = test room Type = room Endpoints = [3] + SetupURL: (empty string)" verification: | - verification step to be updated. + pre-condition : + Please use the below chip-tool commmands as example on how this TC can be performed using chip-tool. The DUT vendor to use commands per the DUT implemetnation + + 1. First read action-list by following command + + ./chip-tool actions read action-list 1 1 + + [1662053538.864044][37149:37154] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0025 Attribute 0x0000_0000 DataVersion: 3676955533 + [1662053538.864116][37149:37154] CHIP:TOO: ActionList: 2 entries + [1662053538.864180][37149:37154] CHIP:TOO: [1]: { + [1662053538.864202][37149:37154] CHIP:TOO: ActionID: 4097 + [1662053538.864221][37149:37154] CHIP:TOO: Name: Room 1 On + [1662053538.864240][37149:37154] CHIP:TOO: Type: 3 + [1662053538.864259][37149:37154] CHIP:TOO: EndpointListID: 57345 + [1662053538.864276][37149:37154] CHIP:TOO: SupportedCommands: 1 + [1662053538.864295][37149:37154] CHIP:TOO: State: 0 + [1662053538.864313][37149:37154] CHIP:TOO: } + [1662053538.864342][37149:37154] CHIP:TOO: [2]: { + [1662053538.864360][37149:37154] CHIP:TOO: ActionID: 4098 + [1662053538.864377][37149:37154] CHIP:TOO: Name: Turn On Room 2 + [1662053538.864395][37149:37154] CHIP:TOO: Type: 3 + [1662053538.864413][37149:37154] CHIP:TOO: EndpointListID: 57346 + [1662053538.864431][37149:37154] CHIP:TOO: SupportedCommands: 1 + [1662053538.864449][37149:37154] CHIP:TOO: State: 0 + [1662053538.864466][37149:37154] CHIP:TOO: } + + 2. Use the above obtained ActionID to verify the following commands + ./chip-tool actions instant-action 4097 1 1 disabled: true - label: "DUT issues an InstantAction command to TH" PICS: ACT.C.C00.Tx verification: | - ./chip-tool actions instant-action 0xA001 1 1 + ./chip-tool actions instant-action 4097 1 1 Verify command is successfully sent on TH(bridge-app) @@ -97,79 +124,59 @@ tests: - label: "DUT issues an StopAction command to TH" PICS: ACT.C.C04.Tx verification: | - ./chip-tool actions stop-action 0 1 1 - - Note: Message log similar as in step 1 + Out of scope for V1.0, The reference app doesn"t have implementation for this command disabled: true - label: "DUT issues an PauseAction command to TH" PICS: ACT.C.C05.Tx verification: | - ./chip-tool actions pause-action 0 1 1 - - Note: Message log similar as in step 1 + Out of scope for V1.0, The reference app doesn"t have implementation for this command disabled: true - label: "DUT issues an ResumeAction command to TH" PICS: ACT.C.C07.Tx verification: | - ./chip-tool actions resume-action 0 1 1 - - Note: Message log similar as in step 1 + Out of scope for V1.0, The reference app doesn"t have implementation for this command disabled: true - label: "DUT issues an EnableAction command to TH" PICS: ACT.C.C08.Tx verification: | - ./chip-tool actions enable-action 0 1 1 - - Note: Message log similar as in step 1 + Out of scope for V1.0, The reference app doesn"t have implementation for this command disabled: true - label: "DUT issues an DisableAction command to TH" PICS: ACT.C.C0a.Tx verification: | - ./chip-tool actions disable-action 0 1 1 - - Note: Message log similar as in step 1 + Out of scope for V1.0, The reference app doesn"t have implementation for this command disabled: true - label: "DUT issues an StartActionWithDuration command to TH" PICS: ACT.C.C03.Tx verification: | - ./chip-tool actions start-action-with-duration 0x1001 100 1 1 - - Note: Message log similar as in step 1 + Out of scope for V1.0, The reference app doesn"t have implementation for this command disabled: true - label: "DUT issues an PauseActionWithDuration command to TH" PICS: ACT.C.C06.Tx verification: | - ./chip-tool actions pause-action-with-duration 0x1001 200 1 1 - - Note: Message log similar as in step 1 + Out of scope for V1.0, The reference app doesn"t have implementation for this command disabled: true - label: "DUT issues an EnableActionWithDuration command to TH" PICS: ACT.C.C09.Tx verification: | - ./chip-tool actions enable-action-with-duration 0x1001 300 1 1 - - Note: Message log similar as in step 1 + Out of scope for V1.0, The reference app doesn"t have implementation for this command disabled: true - label: "DUT issues an DisableActionWithDuration command to TH" PICS: ACT.C.C0b.Tx verification: | - ./chip-tool actions disable-action-with-duration 0x1001 100 1 1 - - Note: Message log similar as in step 1 + Out of scope for V1.0, The reference app doesn"t have implementation for this command disabled: true - label: "DUT issues an InstantActionWithTransition command to TH" PICS: ACT.C.C01.Tx verification: | - ./chip-tool actions instant-action-with-transition 0x1001 400 1 1 - - Note: Message log similar as in step 1 + Out of scope for V1.0, The reference app doesn"t have implementation for this command disabled: 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 c7a463b52543b1..65a5286a1588be 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 @@ -89,6 +89,48 @@ tests: Endpoint 0." PICS: GRPKEY.C.C00.Tx 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": + "d1d1d2d3d4d5d6d7d8d9dadbdcdddedf", "epochStartTime1": 2220001,"epochKey2": + "d2d1d2d3d4d5d6d7d8d9dadbdcdddedf", "epochStartTime2": 2220002 }" 74 0 + + On TH1(Chip-tool), Verify the success response for KeySetWrite + + [1657719041.075123][4541:4546] CHIP:DMG: ICR moving to [ResponseRe] + [1657719041.075174][4541:4546] CHIP:DMG: InvokeResponseMessage = + [1657719041.075200][4541:4546] CHIP:DMG: { + [1657719041.075224][4541:4546] CHIP:DMG: suppressResponse = false, + [1657719041.075255][4541:4546] CHIP:DMG: InvokeResponseIBs = + [1657719041.075287][4541:4546] CHIP:DMG: [ + [1657719041.075311][4541:4546] CHIP:DMG: InvokeResponseIB = + [1657719041.075347][4541:4546] CHIP:DMG: { + [1657719041.075376][4541:4546] CHIP:DMG: CommandStatusIB = + [1657719041.075408][4541:4546] CHIP:DMG: { + [1657719041.075439][4541:4546] CHIP:DMG: CommandPathIB = + [1657719041.075473][4541:4546] CHIP:DMG: { + [1657719041.075507][4541:4546] CHIP:DMG: EndpointId = 0x0, + [1657719041.075542][4541:4546] CHIP:DMG: ClusterId = 0x3f, + [1657719041.075577][4541:4546] CHIP:DMG: CommandId = 0x0, + [1657719041.075609][4541:4546] CHIP:DMG: }, + [1657719041.075646][4541:4546] CHIP:DMG: + [1657719041.075676][4541:4546] CHIP:DMG: StatusIB = + [1657719041.075709][4541:4546] CHIP:DMG: { + [1657719041.075743][4541:4546] CHIP:DMG: status = 0x00 (SUCCESS), + [1657719041.075775][4541:4546] CHIP:DMG: }, + [1657719041.075809][4541:4546] CHIP:DMG: + [1657719041.075840][4541:4546] CHIP:DMG: }, + [1657719041.075874][4541:4546] CHIP:DMG: + [1657719041.075902][4541:4546] CHIP:DMG: }, + [1657719041.075935][4541:4546] CHIP:DMG: + [1657719041.075959][4541:4546] CHIP:DMG: ], + [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, @@ -138,6 +180,19 @@ tests: list on GroupKeyManagement cluster to TH2 on Endpoint 0" PICS: GRPKEY.C.A0000 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 TH1(Chip-tool), Verify the success response for GroupKeySetID + + [1657719130.464175][4557:4562] CHIP:DMG: StatusIB = + [1657719130.464214][4557:4562] CHIP:DMG: { + [1657719130.464256][4557:4562] CHIP:DMG: status = 0x00 (SUCCESS), + [1657719130.464298][4557:4562] CHIP:DMG: }, + [1657719130.464342][4557:4562] CHIP:DMG: + + Run this cmmd for lighting app in chip-tool: ./chip-tool groupkeymanagement write group-key-map "[{"groupId": 1, "groupKeySetID": 42, "fabricIndex": 1}]" 2 0 @@ -155,6 +210,19 @@ tests: Endpoint 1." PICS: G.C.C00.Tx verification: | + Run this cmmd for [ nRF52840-DK ]Thread device in chip-tool: + + ./chip-tool groups add-group 0x0001 grp1 74 1 + + On TH1(Chip-tool), Verify the success response for AddGroup + + [1657719097.788236][4548:4554] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0004 Command 0x0000_0000 + [1657719097.788325][4548:4554] CHIP:TOO: AddGroupResponse: { + [1657719097.788366][4548:4554] CHIP:TOO: status: 0 + [1657719097.788393][4548:4554] CHIP:TOO: groupId: 1 + [1657719097.788418][4548:4554] CHIP:TOO: } + + Run this cmmd for lighting app in chip-tool: ./chip-tool groups add-group 0x0001 grp1 2 1 @@ -168,6 +236,9 @@ tests: [1657717342.600054][3368:3373] CHIP:TOO: } [1657717342.600130][3368:3373] CHIP:DMG: ICR moving + + Run this commands for both Ligh-switch-app and Lighting-app: + ./chip-tool groupsettings add-group grp1 0x0001 ./chip-tool groupsettings add-keysets 0x0042 0 0x000000000021dfe0 hex:d0d1d2d3d4d5d6d7d8d9dadbdcdddedf 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 870f3a188ac896..29ad2f893085a4 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 @@ -202,6 +202,8 @@ tests: [1657719097.788418][4548:4554] CHIP:TOO: } + Run this commands for both Ligh-switch-app and Lighting-app: + ./chip-tool groupsettings add-group grp1 0x0001 ./chip-tool groupsettings add-keysets 0x0042 0 0x000000000021dfe0 hex:d0d1d2d3d4d5d6d7d8d9dadbdcdddedf diff --git a/src/app/tests/suites/certification/Test_TC_BINFO_2_1.yaml b/src/app/tests/suites/certification/Test_TC_BINFO_2_1.yaml index bef34663834d7d..44c5e8f25aea2d 100644 --- a/src/app/tests/suites/certification/Test_TC_BINFO_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_BINFO_2_1.yaml @@ -32,7 +32,7 @@ tests: - name: "nodeId" value: nodeId - #not supported in YAML + #Saving the CountryCode during commissioning not supported in YAML - label: "During Commissioning, TH Saves the CountryCode Information from SetRegulatoryConfig command" @@ -441,7 +441,7 @@ tests: value: ManufacturingDateValue - label: "TH reads PartNumber from the DUT" - PICS: BINFO.S.A000c && PART_NUM + PICS: BINFO.S.A000c command: "readAttribute" attribute: "PartNumber" response: @@ -460,7 +460,7 @@ tests: error: UNSUPPORTED_WRITE - label: "TH reads PartNumber from the DUT" - PICS: BINFO.S.A000c && PART_NUM + PICS: BINFO.S.A000c command: "readAttribute" attribute: "PartNumber" response: 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 83891c653b5b23..bb99e0d88ac3b9 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 @@ -122,7 +122,7 @@ tests: Verify CommissionedFabrics=SupportedFabrics-1 on TH_CR1(chip-tool) log - ./chip-tool operationalcredentials read commissioned-fabrics 1 0 + ./chip-tool operationalcredentials read commissioned-fabrics 2 0 --commissioner-name beta [1660907933.677983][33780:33785] CHIP:TOO: CommissionedFabrics: 15 disabled: true 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 18672ffa5ddad4..e723b6d8694234 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 @@ -140,9 +140,9 @@ tests: CHIP:TOO: } CHIP:DMG: ICR moving to [AwaitingDe] - Verify CommissionedFabrics=SupportedFabrics-1 on TH_CR1(chip-tool) log + Verify CommissionedFabrics=SupportedFabrics-1 on TH_CR2(chip-tool) log - ./chip-tool operationalcredentials read commissioned-fabrics 1 0 + ./chip-tool operationalcredentials read commissioned-fabrics 2 0 --commissioner-name beta [1660907933.677983][33780:33785] CHIP:TOO: CommissionedFabrics: 15 disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_CC_6_2.yaml b/src/app/tests/suites/certification/Test_TC_CC_6_2.yaml index 9d05f0a81c43f1..47494e62171c2b 100644 --- a/src/app/tests/suites/certification/Test_TC_CC_6_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_CC_6_2.yaml @@ -139,11 +139,8 @@ tests: command: "readAttribute" attribute: "ColorTemperatureMireds" response: - saveAs: ColorTemperatureMiredsStep2c constraints: - minValue: - ( ColorTempPhysicalMinMiredsValue + - ColorTempPhysicalMaxMiredsValue ) / 2 + minValue: ColorTempPhysicalMinMiredsValue maxValue: ColorTempPhysicalMaxMiredsValue - label: "Wait 10s" @@ -159,9 +156,8 @@ tests: command: "readAttribute" attribute: "ColorTemperatureMireds" response: - saveAs: ColorTemperatureMiredsStep2d constraints: - minValue: ColorTemperatureMiredsStep2c + minValue: ColorTempPhysicalMinMiredsValue maxValue: ColorTempPhysicalMaxMiredsValue - label: "Wait 5s" @@ -177,8 +173,9 @@ tests: command: "readAttribute" attribute: "ColorTemperatureMireds" response: + value: ColorTempPhysicalMaxMiredsValue constraints: - minValue: ColorTemperatureMiredsStep2d + minValue: ColorTempPhysicalMinMiredsValue maxValue: ColorTempPhysicalMaxMiredsValue - label: @@ -217,7 +214,6 @@ tests: command: "readAttribute" attribute: "ColorTemperatureMireds" response: - saveAs: ColorTemperatureMiredsStep3b constraints: minValue: ColorTempPhysicalMinMiredsValue maxValue: ColorTempPhysicalMaxMiredsValue @@ -235,10 +231,9 @@ tests: command: "readAttribute" attribute: "ColorTemperatureMireds" response: - saveAs: ColorTemperatureMiredsStep3c constraints: minValue: ColorTempPhysicalMinMiredsValue - maxValue: ColorTemperatureMiredsStep3b + maxValue: ColorTempPhysicalMaxMiredsValue - label: "Wait 5s" cluster: "DelayCommands" @@ -253,9 +248,10 @@ tests: command: "readAttribute" attribute: "ColorTemperatureMireds" response: + value: ColorTempPhysicalMinMiredsValue constraints: minValue: ColorTempPhysicalMinMiredsValue - maxValue: ColorTemperatureMiredsStep3c + maxValue: ColorTempPhysicalMaxMiredsValue - label: "TH sends MoveColorTemperature command to DUT with MoveMode = @@ -318,9 +314,7 @@ tests: response: saveAs: ColorTemperatureMiredsStep4c constraints: - minValue: - ( ColorTempPhysicalMaxMiredsValue - - ColorTempPhysicalMinMiredsValue ) / 20 + minValue: ColorTempPhysicalMinMiredsValue maxValue: ColorTempPhysicalMaxMiredsValue - label: "Wait 2s" diff --git a/src/app/tests/suites/certification/Test_TC_CC_6_3.yaml b/src/app/tests/suites/certification/Test_TC_CC_6_3.yaml index cf7771b31bddbe..2b069441c5ba96 100644 --- a/src/app/tests/suites/certification/Test_TC_CC_6_3.yaml +++ b/src/app/tests/suites/certification/Test_TC_CC_6_3.yaml @@ -141,11 +141,8 @@ tests: command: "readAttribute" attribute: "ColorTemperatureMireds" response: - saveAs: ColorTemperatureMiredsStep2c constraints: - minValue: - ( ColorTempPhysicalMinMiredsValue + - ColorTempPhysicalMaxMiredsValue ) / 2 + minValue: ColorTempPhysicalMinMiredsValue maxValue: ColorTempPhysicalMaxMiredsValue - label: "Wait 10s" @@ -161,9 +158,8 @@ tests: command: "readAttribute" attribute: "ColorTemperatureMireds" response: - saveAs: ColorTemperatureMiredsStep2d constraints: - minValue: ColorTemperatureMiredsStep2c + minValue: ColorTempPhysicalMinMiredsValue maxValue: ColorTempPhysicalMaxMiredsValue - label: "Wait 5s" @@ -174,13 +170,15 @@ tests: - name: "ms" value: 5000 + #Issue https://github.com/CHIP-Specifications/chip-test-plans/issues/2175 - label: "TH reads ColorTemperatureMireds attribute from DUT." - PICS: CC.S.F04 && CC.S.A0007 && CC.S.C4c.Rsp + PICS: CC.S.F04 && CC.S.A0007 && CC.S.C4c.Rsp && PICS_SKIP_SAMPLE_APP command: "readAttribute" attribute: "ColorTemperatureMireds" response: + value: ColorTempPhysicalMaxMiredsValue constraints: - minValue: ColorTemperatureMiredsStep2d + minValue: ColorTempPhysicalMinMiredsValue maxValue: ColorTempPhysicalMaxMiredsValue - label: @@ -221,7 +219,6 @@ tests: command: "readAttribute" attribute: "ColorTemperatureMireds" response: - saveAs: ColorTemperatureMiredsStep3b constraints: minValue: ColorTempPhysicalMinMiredsValue maxValue: ColorTempPhysicalMaxMiredsValue @@ -239,10 +236,9 @@ tests: command: "readAttribute" attribute: "ColorTemperatureMireds" response: - saveAs: ColorTemperatureMiredsStep3c constraints: minValue: ColorTempPhysicalMinMiredsValue - maxValue: ColorTemperatureMiredsStep3b + maxValue: ColorTempPhysicalMaxMiredsValue - label: "Wait 5s" cluster: "DelayCommands" @@ -257,9 +253,10 @@ tests: command: "readAttribute" attribute: "ColorTemperatureMireds" response: + value: ColorTempPhysicalMinMiredsValue constraints: minValue: ColorTempPhysicalMinMiredsValue - maxValue: ColorTemperatureMiredsStep3c + maxValue: ColorTempPhysicalMaxMiredsValue - label: "TH reads ColorMode attribute from DUT" PICS: CC.S.F04 && CC.S.A0008 diff --git a/src/app/tests/suites/certification/Test_TC_CHANNEL_5_5.yaml b/src/app/tests/suites/certification/Test_TC_CHANNEL_5_5.yaml index c70564dd35bcbb..d984e27acf0d45 100644 --- a/src/app/tests/suites/certification/Test_TC_CHANNEL_5_5.yaml +++ b/src/app/tests/suites/certification/Test_TC_CHANNEL_5_5.yaml @@ -26,41 +26,57 @@ config: endpoint: 0 tests: + - label: "Preconditions" + verification: | + Commission TH to DUT, if not done so already. In some cases, such as with a Casting Video Player, the TH commissions the DUT. + disabled: true + - label: "DUT sends ChangeChannelByNumber command to TH" PICS: CHANNEL.C.C02.Tx 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 channel change-channel-by-number 33 22 1 1 - ./chip-tv-casting-app channel change-channel-by-number 33 22 1 1 + If the DUT knows the MajorNumber and MinorNumber in channel InputList then those can be sent as the argument. Else User needs to execute the following command to know the MajorNumber and MinorNumber to change the channel + + ./chip-tool channel read channel-list 1 1 + + By sending above command user can select the MajorNumber and MinorNumber instead 9 1 which are listed in chanel list + + ./chip-tool channel change-channel-by-number 9 1 1 1 + ./chip-tv-casting-app channel change-channel-by-number 9 1 1 1 The log below shows the resulting log on the TH (tv-app or all-clusters-app): - [1658530848358] [21924:317544] CHIP: [DMG] InvokeRequestMessage = - [1658530848358] [21924:317544] CHIP: [DMG] { - [1658530848358] [21924:317544] CHIP: [DMG] suppressResponse = false, - [1658530848358] [21924:317544] CHIP: [DMG] timedRequest = false, - [1658530848358] [21924:317544] CHIP: [DMG] InvokeRequests = - [1658530848358] [21924:317544] CHIP: [DMG] [ - [1658530848358] [21924:317544] CHIP: [DMG] CommandDataIB = - [1658530848358] [21924:317544] CHIP: [DMG] { - [1658530848358] [21924:317544] CHIP: [DMG] CommandPathIB = - [1658530848358] [21924:317544] CHIP: [DMG] { - [1658530848358] [21924:317544] CHIP: [DMG] EndpointId = 0x1, - [1658530848358] [21924:317544] CHIP: [DMG] ClusterId = 0x504, - [1658530848358] [21924:317544] CHIP: [DMG] CommandId = 0x2, - [1658530848358] [21924:317544] CHIP: [DMG] }, - [1658530848358] [21924:317544] CHIP: [DMG] - [1658530848358] [21924:317544] CHIP: [DMG] CommandFields = - [1658530848358] [21924:317544] CHIP: [DMG] { - [1658530848358] [21924:317544] CHIP: [DMG] 0x0 = 33, - [1658530848358] [21924:317544] CHIP: [DMG] 0x1 = 22, - [1658530848358] [21924:317544] CHIP: [DMG] }, - [1658530848358] [21924:317544] CHIP: [DMG] }, - [1658530848358] [21924:317544] CHIP: [DMG] - [1658530848358] [21924:317544] CHIP: [DMG] ], - [1658530848358] [21924:317544] CHIP: [DMG] - [1658530848358] [21924:317544] CHIP: [DMG] InteractionModelRevision = 1 - [1658530848358] [21924:317544] CHIP: [DMG] }, + [1661515240.201737][4433:4433] CHIP:DMG: InvokeRequestMessage = + [1661515240.201782][4433:4433] CHIP:DMG: { + [1661515240.201816][4433:4433] CHIP:DMG: suppressResponse = false, + [1661515240.201855][4433:4433] CHIP:DMG: timedRequest = false, + [1661515240.201975][4433:4433] CHIP:DMG: InvokeRequests = + [1661515240.202024][4433:4433] CHIP:DMG: [ + [1661515240.202060][4433:4433] CHIP:DMG: CommandDataIB = + [1661515240.202100][4433:4433] CHIP:DMG: { + [1661515240.202141][4433:4433] CHIP:DMG: CommandPathIB = + [1661515240.202193][4433:4433] CHIP:DMG: { + [1661515240.202245][4433:4433] CHIP:DMG: EndpointId = 0x1, + [1661515240.202294][4433:4433] CHIP:DMG: ClusterId = 0x504, + [1661515240.202338][4433:4433] CHIP:DMG: CommandId = 0x2, + [1661515240.202382][4433:4433] CHIP:DMG: }, + [1661515240.202436][4433:4433] CHIP:DMG: + [1661515240.202477][4433:4433] CHIP:DMG: CommandFields = + [1661515240.202523][4433:4433] CHIP:DMG: { + [1661515240.202571][4433:4433] CHIP:DMG: 0x0 = 9, + [1661515240.202619][4433:4433] CHIP:DMG: 0x1 = 1, + [1661515240.202671][4433:4433] CHIP:DMG: }, + [1661515240.202712][4433:4433] CHIP:DMG: }, + [1661515240.202753][4433:4433] CHIP:DMG: + [1661515240.202786][4433:4433] CHIP:DMG: ], + [1661515240.202827][4433:4433] CHIP:DMG: + [1661515240.202860][4433:4433] CHIP:DMG: InteractionModelRevision = 1 + [1661515240.202892][4433:4433] CHIP:DMG: }, + [1661515240.202975][4433:4433] CHIP:DMG: AccessControl: checking f=2 a=c s=0x000000000001B669 t= c=0x0000_0504 e=1 p=o + [1661515240.203023][4433:4433] CHIP:DMG: AccessControl: allowed + + + Enter the below command to read the current input. ./chip-tool channel read current-channel 1 1 disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_DRLK_2_10.yaml b/src/app/tests/suites/certification/Test_TC_DRLK_2_10.yaml index ac3e56a27d585c..28bdf63ef0a90f 100644 --- a/src/app/tests/suites/certification/Test_TC_DRLK_2_10.yaml +++ b/src/app/tests/suites/certification/Test_TC_DRLK_2_10.yaml @@ -116,7 +116,7 @@ tests: [1656497453.684077][25847:25853] CHIP:DMG: status = 0x00 (SUCCESS), - ./chip-tool doorlock set-credential 0 '{ "credentialType" : 1 , "credentialIndex" : 1 }' 123456 1 0 0 1 1 --timedInteractionTimeoutMs 1000 + ./chip-tool doorlock set-credential 0 '{ "credentialType" : 1 , "credentialIndex" : 1 }' 123456 1 null null 1 1 --timedInteractionTimeoutMs 1000 Verify "DUT sends SUCCESS response" on the TH(Chip-tool) Log: @@ -271,7 +271,7 @@ tests: - label: "TH reads the LockOperationError event from DUT" PICS: DRLK.S.E03 verification: | - ./chip-tool doorlock read-event lock-operation 1 1 + ./chip-tool doorlock read-event lock-operation-error 1 1 Verify " LockOperationType is set to Unlock and Event priority is set to CRITICAL" on the TH(Chip-tool) Log: @@ -555,7 +555,7 @@ tests: [1659778601.601785][3414:3419] CHIP:DMG: }, [1659778601.601823][3414:3419] CHIP:DMG: - ./chip-tool doorlock set-credential 0 '{ "credentialType" : 1 , "credentialIndex" : 1 }' 123456 1 0 0 1 1 --timedInteractionTimeoutMs 1000 + ./chip-tool doorlock set-credential 0 '{ "credentialType" : 1 , "credentialIndex" : 1 }' 123456 1 null null 1 1 --timedInteractionTimeoutMs 1000 Verify "DUT sends Set Credential Response command with status as SUCCESS" on the TH(Chip-tool) Log: diff --git a/src/app/tests/suites/certification/Test_TC_IDM_1_2.yaml b/src/app/tests/suites/certification/Test_TC_IDM_1_2.yaml index df8a4c473fb01b..3f891d2db133fe 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_1_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_1_2.yaml @@ -78,9 +78,8 @@ tests: To Setup the TH(chip-tool) such that it should not have the privilege for the cluster in the path. , 1st we need to send below mentioned ACL command - Here by sending below mentioned ACL command giving only access for ACL cluster(31), So except identify cluster command if try to send any other command will get status as unsupported access. - - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]" 1 0 + Here by sending below mentioned ACL command giving only access for ACL cluster(31), So except ACL cluster command if try to send any other command will get status as unsupported access + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]' 1 0 [1659419722.669629][1915:1920] CHIP:DMG: WriteResponseMessage = [1659419722.669657][1915:1920] CHIP:DMG: { [1659419722.669687][1915:1920] CHIP:DMG: AttributeStatusIBs = @@ -136,7 +135,7 @@ tests: With the above command, we are overwriting the default privilege that chip-tool has as an admin. After this test step you need to send below mentioned command to Grant access to all clusters again. - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]' 1 0 disabled: true - label: @@ -148,9 +147,9 @@ tests: To Setup the TH(chip-tool) such that it should not have the privilege for the cluster in the path. , 1st we need to send below mentioned ACL command - Here by sending below mentioned ACL command giving only access for ACL cluster(31), So except identify cluster command if try to send any other command will get status as unsupported access. + Here by sending below mentioned ACL command giving only access for ACL cluster(31), So except ACL cluster command if try to send any other command will get status as unsupported access - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]' 1 0 [1659419722.669629][1915:1920] CHIP:DMG: WriteResponseMessage = [1659419722.669657][1915:1920] CHIP:DMG: { [1659419722.669687][1915:1920] CHIP:DMG: AttributeStatusIBs = @@ -207,7 +206,7 @@ tests: With the above command, we are overwriting the default privilege that chip-tool has as an admin. After this test step you need to send below mentioned command to Grant access to all clusters again. - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]' 1 0 disabled: true - label: @@ -277,7 +276,7 @@ tests: To Setup the TH(chip-tool) such that it should not have the privilege for the cluster in the path. , 1st we need to send below mentioned ACL command Here by sending below mentioned ACL command giving only access for identify cluster(3), So except identify cluster command if try to send any other command will get status as unsupported access. - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]' 1 0 [1659419722.669629][1915:1920] CHIP:DMG: WriteResponseMessage = [1659419722.669657][1915:1920] CHIP:DMG: { [1659419722.669687][1915:1920] CHIP:DMG: AttributeStatusIBs = @@ -337,7 +336,7 @@ tests: With the above command, we are overwriting the default privilege that chip-tool has as an admin. After this test step you need to send below mentioned command to Grant access to all clusters again. - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]' 1 0 disabled: true - label: diff --git a/src/app/tests/suites/certification/Test_TC_IDM_2_1.yaml b/src/app/tests/suites/certification/Test_TC_IDM_2_1.yaml index f3e052db3241b3..bc9c3b5dee16da 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_2_1.yaml @@ -585,7 +585,7 @@ tests: verification: | DUT implementation required to verify read an attribute of data type Float - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: 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 4feb09f5d728d1..c968217d885833 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 @@ -419,7 +419,7 @@ tests: verification: | DUT implementation required to verify read an attribute of data type Float - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -581,7 +581,7 @@ tests: which is not readable. DUT responds with the report data action." verification: | DUT implementation required to verify read an attribute which is not having a read access - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -593,9 +593,9 @@ tests: To Setup the TH(chip-tool) such that it should not have the privilege for the cluster in the path. , 1st we need to send below mentioned ACL command - Here by sending below mentioned ACL command giving only access for ACL cluster(31), So except identify cluster command if try to send any other command will get status as unsupported access. + Here by sending below mentioned ACL command giving only access for ACL cluster(31), So except ACL cluster command if try to send any other command will get status as unsupported access - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]' 1 0 [1659419722.669629][1915:1920] CHIP:DMG: WriteResponseMessage = [1659419722.669657][1915:1920] CHIP:DMG: { [1659419722.669687][1915:1920] CHIP:DMG: AttributeStatusIBs = @@ -654,7 +654,7 @@ tests: With the above command, we are overwriting the default privilege that chip-tool has as an admin. After this test step you need to send below mentioned command to Grant access to all clusters again. - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]' 1 0 disabled: true - label: @@ -1037,7 +1037,7 @@ tests: PICS: MCORE.IDM.S.LargeData verification: | DUT implementation required to verify read an attribute which is is larger than 1 MTU(1280 bytes) - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -1092,9 +1092,9 @@ tests: To Setup the TH(chip-tool) such that it should not have the privilege for the cluster in the path. , 1st we need to send below mentioned ACL command - Here by sending below mentioned ACL command giving only access for ACL cluster(31), So except identify cluster command if try to send any other command will get status as unsupported access. + Here by sending below mentioned ACL command giving only access for ACL cluster(31), So except ACL cluster command if try to send any other command will get status as unsupported access - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]' 1 0 [1659419722.669629][1915:1920] CHIP:DMG: WriteResponseMessage = [1659419722.669657][1915:1920] CHIP:DMG: { [1659419722.669687][1915:1920] CHIP:DMG: AttributeStatusIBs = @@ -1193,7 +1193,7 @@ tests: With the above command, we are overwriting the default privilege that chip-tool has as an admin. After this test step you need to send below mentioned command to Grant access to all clusters again. - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]' 1 0 disabled: true - label: 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 e331b6bd425b80..be72e71408c125 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 @@ -429,7 +429,7 @@ tests: verification: | DUT implementation required to verify write an attribute of data type signed integer. - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -439,7 +439,7 @@ tests: verification: | DUT implementation required to verify write an attribute of data type float - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -449,7 +449,7 @@ tests: verification: | DUT implementation required to verify write an attribute of data type Octet String - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -459,7 +459,7 @@ tests: verification: | DUT implementation required to verify write an attribute ofdata type Struct - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -469,7 +469,7 @@ tests: verification: | DUT implementation required to verify write an attribute of data type List - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -662,7 +662,7 @@ tests: Here is an example command to verify the write functionality. User must choose an attribute which has large list of attribute data. ./chip-tool basic write node-label node 1 0 - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: diff --git a/src/app/tests/suites/certification/Test_TC_IDM_3_2.yaml b/src/app/tests/suites/certification/Test_TC_IDM_3_2.yaml index d7fe32d542c34d..2e999ee455cd07 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_3_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_3_2.yaml @@ -219,7 +219,7 @@ tests: verification: | DUT implementation required to verify write an attribute of data type signed integer. - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -229,7 +229,7 @@ tests: verification: | DUT implementation required to verify write an attribute of data type float - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -239,7 +239,7 @@ tests: verification: | DUT implementation required to verify write an attribute of data type Octet String - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -249,7 +249,7 @@ tests: verification: | DUT implementation required to verify write an attribute ofdata type Struct - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -259,7 +259,7 @@ tests: verification: | DUT implementation required to verify write an attribute of data type List - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -299,8 +299,7 @@ tests: [1649152707.515250][16226:16231] CHIP:DMG: } [1649152707.515374][16226:16231] CHIP:DMG: WriteClient moving to [AwaitingDe] - - ./chip-tool any read-by-id 0x0008 0x0010 1 1 + ./chip-tool any read-by-id 0x0204 0 1 1 [1655201353.941835][3634:3639] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0204 Attribute 0x0000_0000 DataVersion: 263686993 [1655201353.941926][3634:3639] CHIP:TOO: temperature display mode: 1 [1655201353.942030][3634:3639] CHIP:EM: Sending Standalone Ack for MessageCounter:58103180 on exchange 16578i @@ -523,7 +522,7 @@ tests: To Setup the TH such that it should not have the privilege for the cluster in the path. , 1st we need to send below mentioned ACL command Here by sending below mentioned ACL command giving only access for ACL cluster(31), So except identify cluster command if try to send any other command will get status as unsupported access. - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]' 1 0 [1659419722.669629][1915:1920] CHIP:DMG: WriteResponseMessage = [1659419722.669657][1915:1920] CHIP:DMG: { [1659419722.669687][1915:1920] CHIP:DMG: AttributeStatusIBs = @@ -580,7 +579,7 @@ tests: With the above command, we are overwriting the default privilege that chip-tool has as an admin. After this test step you need to send below mentioned command to Grant access to all clusters again. - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]' 1 0 disabled: true - label: @@ -843,5 +842,5 @@ tests: verification: | DUT implementation required to verify write an attribute which need NEEDS_TIMED_INTERACTION. - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true 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 6e65a74fe92f83..f6843e1e8f24a9 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 @@ -484,7 +484,7 @@ tests: DUT implementation required to verify subscribe an attribute of data type signed integer - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -498,7 +498,7 @@ tests: - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -512,7 +512,7 @@ tests: - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -535,8 +535,7 @@ tests: 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" + any subscribe-by-id "6,8,3" "0,1,0" 10 100 1 "1,1,1" On TH (On the reference app) Verify if DUT is responding with the below status response for the above command @@ -590,31 +589,13 @@ tests: 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: ], - [1657884990.166149][2938:2943] CHIP:DMG: - [1657884990.166201][2938:2943] CHIP:DMG: InteractionModelRevision = 1 - [1657884990.166255][2938:2943] CHIP:DMG: } - [1657884990.166480][2938:2943] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0003 Attribute 0x0000_0000 DataVersion: 2311319147 - [1657884990.166551][2938:2943] CHIP:TOO: identify time: 0 - [1657884990.166667][2938:2943] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0008 Attribute 0x0000_0001 DataVersion: 3439199877 - [1657884990.166727][2938:2943] CHIP:TOO: remaining time: 0 - [1657884990.166850][2938:2943] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0006 Attribute 0x0000_0000 DataVersion: 1121586347 - [1657884990.166907][2938:2943] CHIP:TOO: OnOff: FALSE - [1657884990.166994][2938:2943] CHIP:DMG: MoveToState ReadClient[0xffffa40091f0]: Moving to [AwaitingSu] - [1657884990.167092][2938:2943] CHIP:EM: Piggybacking Ack for MessageCounter:137911489 on exchange: 45832i - [1657884990.167206][2938:2943] CHIP:IN: Prepared secure message 0xffffa4000db8 to 0x0000000000000001 (1) of type 0x1 and protocolId (0, 1) on exchange 45832i with MessageCounter:83158102. - [1657884990.167277][2938:2943] CHIP:IN: Sending encrypted msg 0xffffa4000db8 with MessageCounter:83158102 to 0x0000000000000001 (1) at monotonic time: 00000000007567AF msec - [1657884990.169637][2938:2943] CHIP:EM: Received message of type 0x4 with protocolId (0, 1) and MessageCounter:137911490 on exchange 45832i - [1657884990.169705][2938:2943] CHIP:EM: Found matching exchange: 45832i, Delegate: 0xffffa40091f0 - [1657884990.169769][2938:2943] CHIP:EM: Rxd Ack; Removing MessageCounter:83158102 from Retrans Table on exchange 45832i - [1657884990.169821][2938:2943] CHIP:EM: Removed CHIP MessageCounter:83158102 from RetransTable on exchange 45832i - [1657884990.169905][2938:2943] CHIP:DMG: SubscribeResponseMessage = - [1657884990.169960][2938:2943] CHIP:DMG: { - [1657884990.170011][2938:2943] CHIP:DMG: SubscriptionId = 0x496bb4cf, - [1657884990.170067][2938:2943] CHIP:DMG: MaxInterval = 0x64, - [1657884990.170120][2938:2943] CHIP:DMG: InteractionModelRevision = 1 - [1657884990.170169][2938:2943] CHIP:DMG: } - [1657884990.170223][2938:2943] CHIP:DMG: Subscription established with SubscriptionID = 0x496bb4cf MinInterval = 10s MaxInterval = 100s Peer = 01:0000000000000001 + [1662036515.630221][166451:166456] CHIP:DMG: } + [1662036515.630284][166451:166456] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0003 Attribute 0x0000_0000 DataVersion: 3175537504 + [1662036515.630298][166451:166456] CHIP:TOO: identify time: 0 + [1662036515.630329][166451:166456] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0008 Attribute 0x0000_0001 DataVersion: 3999635638 + [1662036515.630338][166451:166456] CHIP:TOO: RemainingTime: 0 + [1662036515.630366][166451:166456] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0006 Attribute 0x0000_0000 DataVersion: 2488235261 + [1662036515.630375][166451:166456] CHIP:TOO: OnOff: FALSE + [1662036515.630396][166451:166456] CHIP:DMG: MoveToState ReadClient[0x7fee1c024260]: Moving to [AwaitingSu] + [1662036515.630416][166451:166456] CHIP:EM: Piggybacking Ack for MessageCounter:196351589 on exchange: 20857i disabled: true diff --git a/src/app/tests/suites/certification/Test_TC_IDM_4_3.yaml b/src/app/tests/suites/certification/Test_TC_IDM_4_3.yaml index 0098180fec907f..4a10b805110959 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_4_3.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_4_3.yaml @@ -461,7 +461,7 @@ tests: Subscribe to an attribute of type signed integer to the Harness - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -475,7 +475,7 @@ tests: Subscribe to an attribute of type floating point to the Harness - If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "\Not Applicable\" + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: @@ -500,7 +500,7 @@ tests: [1655896309.160851][1885:1890] CHIP:DMG: MoveToState ReadClient[0xffffa0005710]: Moving to [AwaitingSu] here is an example command the TH can write an attribute in the userlabel cluster in the DUT to change the value that the TH subscribed in the above command. - userlabel write label-list "[{"label":"room", "value":"bedroom 1"}, {"label":"orientation", "value":"east"}]" 1 0 + userlabel write label-list '[{"label":"room", "value":"bedroom 1"}, {"label":"orientation", "value":"east"}]' 1 0 ./chip-tool userlabel subscribe label-list 100 500 1 0 [1655896422.936972][1899:1904] CHIP:DMG: } diff --git a/src/app/tests/suites/certification/Test_TC_IDM_6_1.yaml b/src/app/tests/suites/certification/Test_TC_IDM_6_1.yaml index 35f087fa7fd66e..66beebca83d8a5 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_6_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_6_1.yaml @@ -418,9 +418,9 @@ tests: The cluster used in the below command is an example, User can use any supported chip cluster. To Setup the TH such that it should not have the privilege for the cluster in the path. , 1st we need to send below mentioned ACL command - Here by sending below mentioned ACL command giving only access for ACL cluster(31), So except identify cluster command if try to send any other command will get status as unsupported access. + Here by sending below mentioned ACL command giving only access for ACL cluster(31), So except ACL cluster command if try to send any other command will get status as unsupported access - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects":[1,112233], "targets": [{ "cluster":31, "endpoint":0, "deviceType":null }]}]' 1 0 [1659419722.669629][1915:1920] CHIP:DMG: WriteResponseMessage = [1659419722.669657][1915:1920] CHIP:DMG: { [1659419722.669687][1915:1920] CHIP:DMG: AttributeStatusIBs = @@ -501,7 +501,7 @@ tests: With the above command, we are overwriting the default privilege that chip-tool has as an admin. After this test step you need to send below mentioned command to Grant access to all clusters again. - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects":[112233], "targets":null}]' 1 0 disabled: true - label: @@ -511,7 +511,7 @@ tests: verification: | To Setup the TH such that there is no accessing fabric, 1st we need to send below mentioned ACL command - ./chip-tool accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [1234], "targets": null}]" 1 0 + ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [1234], "targets": null}]' 1 0 ./chip-tool any read-event-by-id 0xFFFFFFFF 0xFFFFFFFF 1 0xFFFF On TH(chip-tool) verify DUT sends Report Data Message with no entry for that event in EventReports list. diff --git a/src/app/tests/suites/certification/Test_TC_IDM_6_2.yaml b/src/app/tests/suites/certification/Test_TC_IDM_6_2.yaml index 7b975023679079..c7947a866f51cb 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_6_2.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_6_2.yaml @@ -884,7 +884,7 @@ tests: To Setup the TH(chip-tool) such that it should not have the privilege for the cluster in the path. , 1st we need to send below mentioned ACL command Here by sending below mentioned ACL command giving only access for identify cluster(3), So except identify cluster command if try to send any other command will get status as unsupported access. - accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets":[{ "cluster": 3, "endpoint": 1, "deviceType": null }]}]" 1 0 + accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets":[{ "cluster": 3, "endpoint": 1, "deviceType": null }]}]' 1 0 basic subscribe-event-by-id 0x000 100 1000 1 0 @@ -937,7 +937,7 @@ tests: To Setup the TH such that there is no accessing fabric, 1st we need to send below mentioned ACL command - accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [1234], "targets": null}]" 1 0 + accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [1234], "targets": null}]' 1 0 any subscribe-event-by-id 0xFFFFFFFF 0xFFFFFFFF 100 1000 1 0xFFFF @@ -1221,7 +1221,7 @@ tests: By sending the command mentioned below, change attribute values on DUT to create events multiple times. - accesscontrol write acl "[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null}, {"fabricIndex": 1, "privilege": 1, "authMode": 3, "subjects": [111,222,333,444], "targets": [{"cluster":11 , "endpoint":22, "deviceType": null}]}, {"fabricIndex": 1, "privilege": 3, "authMode": 3, "subjects": [555,666,777,888], "targets": [{"cluster": 55, "endpoint": 66, "deviceType":null }]}]" 1 0 + accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null}, {"fabricIndex": 1, "privilege": 1, "authMode": 3, "subjects": [111,222,333,444], "targets": [{"cluster":11 , "endpoint":22, "deviceType": null}]}, {"fabricIndex": 1, "privilege": 3, "authMode": 3, "subjects": [555,666,777,888], "targets": [{"cluster": 55, "endpoint": 66, "deviceType":null }]}]' 1 0 On TH Verify that each event record is assigned a number that is exactly 1 greater than the last created event record on that Node. diff --git a/src/app/tests/suites/certification/Test_TC_IDM_6_3.yaml b/src/app/tests/suites/certification/Test_TC_IDM_6_3.yaml index ab5421f1ded75d..bf3ebdf8496a50 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_6_3.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_6_3.yaml @@ -32,18 +32,15 @@ tests: - label: "DUT sends Read Request Message to the TH for a supported event." verification: | The cluster used in the below command is an example, User can use any supported chip cluster. + disabled: true - - Please run this test in chip tool interactive mode ./chip-tool interactive start - + - label: "DUT sends Read Request Message to the TH for a supported event." + verification: | sudo ./chip-tool any read-event-by-id 0xFFFFFFFF 0xFFFFFFFF 1 0xFFFF On TH(Reference app) verify the Read Request Message received has these fields EventRequests, EventFilters and FabricFiltered If the DUT has to provision to verify the logs, verify that Read Request Message received has these fields EventRequests, EventFilters, and FabricFiltered. - - - [1655210591.986723][4218:4223] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0028 Event 0x0000_0000 [1655210591.986748][4218:4223] CHIP:TOO: Event number: 65536 [1655210591.986771][4218:4223] CHIP:TOO: Priority: Critical diff --git a/src/app/tests/suites/certification/Test_TC_IDM_8_1.yaml b/src/app/tests/suites/certification/Test_TC_IDM_8_1.yaml index 0320f91139cd10..c34016628540da 100644 --- a/src/app/tests/suites/certification/Test_TC_IDM_8_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_IDM_8_1.yaml @@ -368,6 +368,9 @@ tests: data. Modify attribute1 on the DUT." verification: | DUT implementation required to verify the list of structs which contain some fabric-sensitive data + + + If the Vendor DUT doesn"t implement/supported this attribute, Please mark the test step as "Not Applicable" disabled: true - label: diff --git a/src/app/tests/suites/certification/Test_TC_I_1_1.yaml b/src/app/tests/suites/certification/Test_TC_I_1_1.yaml index b9bd3c92c77d24..9bfd93eb98c13e 100644 --- a/src/app/tests/suites/certification/Test_TC_I_1_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_I_1_1.yaml @@ -74,7 +74,7 @@ tests: contains: [0] - label: "Read the optional command(TriggerEffect) in AcceptedCommandList" - PICS: I.C.C40.Tx + PICS: I.S.C40.Rsp command: "readAttribute" attribute: "AcceptedCommandList" response: @@ -84,7 +84,7 @@ tests: #Commenting out the step IdentifyQuery (0x01) is not supported by Matter 1.0. #- label: "Read the optional attribute(IdentifyQuery) in AcceptedCommandList" - # PICS: I.C.C01.Tx + # PICS: I.S.C01.Rsp # command: "readAttribute" # attribute: "AcceptedCommandList" # response: 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 1034429074839e..732419bb175e9c 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 @@ -109,7 +109,7 @@ tests: 1b..1d below." PICS: SWTCH.C.F00 verification: | - verification step to be updated. + disabled: true - label: "DUT reads global attribute FeatureMap." @@ -141,9 +141,9 @@ tests: the switch is operated." PICS: SWTCH.C.F00 && SWTCH.C.M.EV verification: | - In Raspi platform the event is triggered with below command, Pls use equivalent command on the respective DUT + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - echo "{"Name":"SwitchLatched","NewPosition":0}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"SwitchLatched","NewPosition":0}" > /tmp/chip_all_clusters_fifo_ (PID of DUT) [1659679728.732056][2530:2538] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":0}" [1659679728.732389][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e7706 @@ -171,7 +171,7 @@ tests: minute period) DUT reads attribute CurrentPosition regularly," PICS: SWTCH.C.F00 && SWTCH.C.M.RA verification: | - In Raspi platform to change the simulated switch between positions using the below commands + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) echo "{"Name":"SwitchLatched","NewPosition":1}" > /tmp/chip_all_clusters_fifo- (PID of DUT) @@ -204,9 +204,9 @@ tests: NewPosition reflecting the new state) on every change" PICS: SWTCH.C.F00 && SWTCH.C.M.EV verification: | - In Raspi platform to change the simulated switch between positions using the below commands + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - echo "{"Name":"SwitchLatched","NewPosition":1}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"SwitchLatched","NewPosition":1}" > /tmp/chip_all_clusters_fifo_ (PID of DUT) [1659621148.831745][8590:8596] CHIP:-: Received payload: "{"Name":"SwitchLatched","NewPosition":1}" [1659621148.832236][8590:8590] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4be58f54 @@ -283,7 +283,7 @@ tests: 3b..3d below." PICS: SWTCH.C.F01 verification: | - verification step to be updated. + disabled: true - label: "DUT reads global attribute FeatureMap." @@ -315,9 +315,9 @@ tests: switch is operated." PICS: SWTCH.C.F01 && SWTCH.C.M.EV verification: | - In Raspi platform the event is triggered with below command, Pls use equivalent command on the respective DUT + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - echo "{"Name":"InitialPress","NewPosition":0}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"InitialPress","NewPosition":0}" > /tmp/chip_all_clusters_fifo_ (PID of DUT) [1659624126.646996][8590:8596] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":0}" [1659624126.647380][8590:8590] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4be58f55 @@ -339,7 +339,7 @@ tests: [1659683181.743470][2829:2835] CHIP:TOO: NewPosition: 0 [1659683181.743506][2829:2835] CHIP:TOO: } - echo "{"Name":"ShortRelease","PreviousPosition":0}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"ShortRelease","PreviousPosition":0}" > /tmp/chip_all_clusters_fifo_ (PID of DUT) [1659683678.805455][2530:2538] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":0}" [1659683678.805739][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e7715 @@ -361,7 +361,7 @@ tests: if SWTCH.C.F03, also: - echo "{"Name":"LongPress","NewPosition":1}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"LongPress","NewPosition":1}" > /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:-- @@ -377,7 +377,7 @@ tests: [1659527630.476934][4774:4779] CHIP:TOO: NewPosition: 1 [1659527630.476969][4774:4779] CHIP:TOO: } - echo "{"Name":"LongRelease","PreviousPosition":1}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"LongRelease","PreviousPosition":1}" > /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:-- @@ -401,9 +401,9 @@ tests: to 0 - wait 10 seconds DUT reads attribute CurrentPosition regularly" PICS: SWTCH.C.F01 && SWTCH.C.M.RA verification: | - In Raspi platform to change the simulated switch between positions using the below commands + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - echo "{"Name":"InitialPress","NewPosition":1}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"InitialPress","NewPosition":1}" > /tmp/chip_all_clusters_fifo_ (PID of DUT) [1659624126.646996][8590:8596] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" [1659624126.647380][8590:8590] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4be58f55 @@ -412,7 +412,7 @@ tests: After 0.2 seconds, send this command - echo "{"Name":"ShortRelease","PreviousPosition":1}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"ShortRelease","PreviousPosition":1}" > /tmp/chip_all_clusters_fifo_ (PID of DUT) [1659683678.805455][2530:2538] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" [1659683678.805739][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e7715 @@ -446,9 +446,9 @@ tests: the event ShortRelease (with field PreviousPosition=1) wait 10 seconds" PICS: SWTCH.C.F01 && SWTCH.C.M.EV verification: | - In Raspi platform to change the simulated switch between positions using the below commands + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - echo "{"Name":"InitialPress","NewPosition":1}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"InitialPress","NewPosition":1}" > /tmp/chip_all_clusters_fifo_ (PID of DUT) [1659624126.646996][8590:8596] CHIP:-: Received payload: "{"Name":"InitialPress","NewPosition":1}" [1659624126.647380][8590:8590] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to 4be58f55 @@ -456,7 +456,7 @@ tests: [1659624126.647480][8590:8590] CHIP:ZCL: SwitchServer: OnInitialPress After 0.2 seconds, send this command - echo "{"Name":"ShortRelease","PreviousPosition":1}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"ShortRelease","PreviousPosition":1}" > /tmp/chip_all_clusters_fifo_ (PID of DUT) [1659684051.064329][2530:2538] CHIP:-: Received payload: "{"Name":"ShortRelease","PreviousPosition":1}" [1659684051.064820][2530:2530] CHIP:DMG: Endpoint 1, Cluster 0x0000_003B update version to ee5e7716 @@ -507,17 +507,17 @@ tests: LongRelease (with field PreviousPosition=1) wait 8 seconds" PICS: SWTCH.C.F01 && SWTCH.C.F03 && SWTCH.C.M.EV verification: | - In Raspi platform to change the simulated switch between positions using the below commands + On Raspi platform To trigger the event give the below command by opening an another terminal in DUT (Below is the example command developed in all-clusters-app to generate the event, Vendor Dut should have capability to generate this event) - echo "{"Name":"InitialPress","NewPosition":1}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"InitialPress","NewPosition":1}" > /tmp/chip_all_clusters_fifo_ (PID of DUT) After 0.75 seconds, send this command - echo "{"Name":"LongPress","NewPosition":1}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"LongPress","NewPosition":1}" > /tmp/chip_all_clusters_fifo_ (PID of DUT) After 2 seconds, send this command - echo "{"Name":"LongRelease","PreviousPosition":1}" > /tmp/chip_all_clusters_fifo- (PID of DUT) + echo "{"Name":"LongRelease","PreviousPosition":1}" > /tmp/chip_all_clusters_fifo_ (PID of DUT) After 8 seconds, repeat this set of commands Repeat this for 1 minute total. diff --git a/src/app/tests/suites/certification/Test_TC_TMP_2_1.yaml b/src/app/tests/suites/certification/Test_TC_TMP_2_1.yaml index 38cd27cbfd46b0..bfedfea792cb0c 100644 --- a/src/app/tests/suites/certification/Test_TC_TMP_2_1.yaml +++ b/src/app/tests/suites/certification/Test_TC_TMP_2_1.yaml @@ -33,16 +33,6 @@ tests: - name: "nodeId" value: nodeId - - label: "Read the mandatory attribute: MeasuredValue" - PICS: TMP.S.A0000 - command: "readAttribute" - attribute: "MeasuredValue" - response: - constraints: - type: int16s - minValue: -27315 - maxValue: 32767 - - label: "Read the mandatory attribute: MinMeasuredValue" PICS: TMP.S.A0001 command: "readAttribute" @@ -63,6 +53,16 @@ tests: minValue: -27314 maxValue: 32767 + - label: "Read the mandatory attribute: MeasuredValue" + PICS: TMP.S.A0000 + command: "readAttribute" + attribute: "MeasuredValue" + response: + constraints: + type: int16s + minValue: -27315 + maxValue: 32767 + - label: "Read the optional attribute: Tolerance" PICS: TMP.S.A0003 command: "readAttribute" diff --git a/src/app/tests/suites/certification/ci-pics-values b/src/app/tests/suites/certification/ci-pics-values index 20d0abc051ce71..d3fdc71534a461 100644 --- a/src/app/tests/suites/certification/ci-pics-values +++ b/src/app/tests/suites/certification/ci-pics-values @@ -3,7 +3,6 @@ WIFI=1 THREAD=1 ETH=1 MANF_DATE=1 -PART_NUM=1 DM_ICACERT=1 A_PRESENTVALUE=1 A_OUTOFSERVICE=1 diff --git a/zzz_generated/chip-tool/zap-generated/test/Commands.h b/zzz_generated/chip-tool/zap-generated/test/Commands.h index 358738a95d5e4a..ead25e1abc9aaf 100644 --- a/zzz_generated/chip-tool/zap-generated/test/Commands.h +++ b/zzz_generated/chip-tool/zap-generated/test/Commands.h @@ -8975,10 +8975,6 @@ class Test_TC_CC_6_2Suite : public TestCommand uint16_t ColorTempPhysicalMinMiredsValue; uint16_t ColorTempPhysicalMaxMiredsValue; - uint16_t ColorTemperatureMiredsStep2c; - uint16_t ColorTemperatureMiredsStep2d; - uint16_t ColorTemperatureMiredsStep3b; - uint16_t ColorTemperatureMiredsStep3c; uint16_t ColorTemperatureMiredsStep4c; chip::EndpointId GetEndpoint(chip::EndpointId endpoint) { return mEndpoint.HasValue() ? mEndpoint.Value() : endpoint; } @@ -9054,10 +9050,8 @@ class Test_TC_CC_6_2Suite : public TestCommand { uint16_t value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); - VerifyOrReturn(CheckConstraintMinValue("value", value, - (ColorTempPhysicalMinMiredsValue + ColorTempPhysicalMaxMiredsValue) / 2)); + VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); - ColorTemperatureMiredsStep2c = value; } break; case 11: @@ -9069,9 +9063,8 @@ class Test_TC_CC_6_2Suite : public TestCommand { uint16_t value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); - VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTemperatureMiredsStep2c)); + VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); - ColorTemperatureMiredsStep2d = value; } break; case 13: @@ -9083,7 +9076,8 @@ class Test_TC_CC_6_2Suite : public TestCommand { uint16_t value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); - VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTemperatureMiredsStep2d)); + VerifyOrReturn(CheckValue("colorTemperatureMireds", value, ColorTempPhysicalMaxMiredsValue)); + VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); } break; @@ -9101,7 +9095,6 @@ class Test_TC_CC_6_2Suite : public TestCommand VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); - ColorTemperatureMiredsStep3b = value; } break; case 18: @@ -9114,8 +9107,7 @@ class Test_TC_CC_6_2Suite : public TestCommand uint16_t value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); - VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTemperatureMiredsStep3b)); - ColorTemperatureMiredsStep3c = value; + VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); } break; case 20: @@ -9127,8 +9119,9 @@ class Test_TC_CC_6_2Suite : public TestCommand { uint16_t value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); + VerifyOrReturn(CheckValue("colorTemperatureMireds", value, ColorTempPhysicalMinMiredsValue)); VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); - VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTemperatureMiredsStep3c)); + VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); } break; case 22: @@ -9146,8 +9139,7 @@ class Test_TC_CC_6_2Suite : public TestCommand { uint16_t value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); - VerifyOrReturn(CheckConstraintMinValue("value", value, - (ColorTempPhysicalMaxMiredsValue - ColorTempPhysicalMinMiredsValue) / 20)); + VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); ColorTemperatureMiredsStep4c = value; } @@ -9509,10 +9501,6 @@ class Test_TC_CC_6_3Suite : public TestCommand uint16_t ColorTempPhysicalMinMiredsValue; uint16_t ColorTempPhysicalMaxMiredsValue; - uint16_t ColorTemperatureMiredsStep2c; - uint16_t ColorTemperatureMiredsStep2d; - uint16_t ColorTemperatureMiredsStep3b; - uint16_t ColorTemperatureMiredsStep3c; chip::EndpointId GetEndpoint(chip::EndpointId endpoint) { return mEndpoint.HasValue() ? mEndpoint.Value() : endpoint; } @@ -9587,10 +9575,8 @@ class Test_TC_CC_6_3Suite : public TestCommand { uint16_t value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); - VerifyOrReturn(CheckConstraintMinValue("value", value, - (ColorTempPhysicalMinMiredsValue + ColorTempPhysicalMaxMiredsValue) / 2)); + VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); - ColorTemperatureMiredsStep2c = value; } break; case 11: @@ -9602,9 +9588,8 @@ class Test_TC_CC_6_3Suite : public TestCommand { uint16_t value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); - VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTemperatureMiredsStep2c)); + VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); - ColorTemperatureMiredsStep2d = value; } break; case 13: @@ -9616,7 +9601,8 @@ class Test_TC_CC_6_3Suite : public TestCommand { uint16_t value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); - VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTemperatureMiredsStep2d)); + VerifyOrReturn(CheckValue("colorTemperatureMireds", value, ColorTempPhysicalMaxMiredsValue)); + VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); } break; @@ -9634,7 +9620,6 @@ class Test_TC_CC_6_3Suite : public TestCommand VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); - ColorTemperatureMiredsStep3b = value; } break; case 18: @@ -9647,8 +9632,7 @@ class Test_TC_CC_6_3Suite : public TestCommand uint16_t value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); - VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTemperatureMiredsStep3b)); - ColorTemperatureMiredsStep3c = value; + VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); } break; case 20: @@ -9660,8 +9644,9 @@ class Test_TC_CC_6_3Suite : public TestCommand { uint16_t value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); + VerifyOrReturn(CheckValue("colorTemperatureMireds", value, ColorTempPhysicalMinMiredsValue)); VerifyOrReturn(CheckConstraintMinValue("value", value, ColorTempPhysicalMinMiredsValue)); - VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTemperatureMiredsStep3c)); + VerifyOrReturn(CheckConstraintMaxValue("value", value, ColorTempPhysicalMaxMiredsValue)); } break; case 22: @@ -9830,7 +9815,8 @@ class Test_TC_CC_6_3Suite : public TestCommand } case 14: { LogStep(14, "TH reads ColorTemperatureMireds attribute from DUT."); - VerifyOrDo(!ShouldSkip("CC.S.F04 && CC.S.A0007 && CC.S.C4c.Rsp"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); + VerifyOrDo(!ShouldSkip("CC.S.F04 && CC.S.A0007 && CC.S.C4c.Rsp && PICS_SKIP_SAMPLE_APP"), + return ContinueOnChipMainThread(CHIP_NO_ERROR)); return ReadAttribute(kIdentityAlpha, GetEndpoint(1), ColorControl::Id, ColorControl::Attributes::ColorTemperatureMireds::Id, true, chip::NullOptional); } @@ -13243,7 +13229,7 @@ class Test_TC_BINFO_2_1Suite : public TestCommand } case 42: { LogStep(42, "TH reads PartNumber from the DUT"); - VerifyOrDo(!ShouldSkip("BINFO.S.A000c && PART_NUM"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); + VerifyOrDo(!ShouldSkip("BINFO.S.A000c"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); return ReadAttribute(kIdentityAlpha, GetEndpoint(0), Basic::Id, Basic::Attributes::PartNumber::Id, true, chip::NullOptional); } @@ -13258,7 +13244,7 @@ class Test_TC_BINFO_2_1Suite : public TestCommand } case 44: { LogStep(44, "TH reads PartNumber from the DUT"); - VerifyOrDo(!ShouldSkip("BINFO.S.A000c && PART_NUM"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); + VerifyOrDo(!ShouldSkip("BINFO.S.A000c"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); return ReadAttribute(kIdentityAlpha, GetEndpoint(0), Basic::Id, Basic::Attributes::PartNumber::Id, true, chip::NullOptional); } @@ -16162,7 +16148,7 @@ class Test_TC_I_1_1Suite : public TestCommand } case 5: { LogStep(5, "Read the optional command(TriggerEffect) in AcceptedCommandList"); - VerifyOrDo(!ShouldSkip("I.C.C40.Tx"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); + VerifyOrDo(!ShouldSkip("I.S.C40.Rsp"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); return ReadAttribute(kIdentityAlpha, GetEndpoint(1), Identify::Id, Identify::Attributes::AcceptedCommandList::Id, true, chip::NullOptional); } @@ -32842,7 +32828,7 @@ class Test_TC_TMP_2_1Suite : public TestCommand chip::app::DataModel::Nullable value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); VerifyOrReturn(CheckConstraintType("value", "int16s", "int16s")); - VerifyOrReturn(CheckConstraintMinValue("value", value, -27315)); + VerifyOrReturn(CheckConstraintMinValue("value", value, -27314)); VerifyOrReturn(CheckConstraintMaxValue("value", value, 32767)); } break; @@ -32852,7 +32838,7 @@ class Test_TC_TMP_2_1Suite : public TestCommand chip::app::DataModel::Nullable value; VerifyOrReturn(CheckDecodeValue(chip::app::DataModel::Decode(*data, value))); VerifyOrReturn(CheckConstraintType("value", "int16s", "int16s")); - VerifyOrReturn(CheckConstraintMinValue("value", value, -27314)); + VerifyOrReturn(CheckConstraintMinValue("value", value, -27315)); VerifyOrReturn(CheckConstraintMaxValue("value", value, 32767)); } break; @@ -32889,23 +32875,23 @@ class Test_TC_TMP_2_1Suite : public TestCommand return WaitForCommissionee(kIdentityAlpha, value); } case 1: { - LogStep(1, "Read the mandatory attribute: MeasuredValue"); - VerifyOrDo(!ShouldSkip("TMP.S.A0000"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); - return ReadAttribute(kIdentityAlpha, GetEndpoint(1), TemperatureMeasurement::Id, - TemperatureMeasurement::Attributes::MeasuredValue::Id, true, chip::NullOptional); - } - case 2: { - LogStep(2, "Read the mandatory attribute: MinMeasuredValue"); + LogStep(1, "Read the mandatory attribute: MinMeasuredValue"); VerifyOrDo(!ShouldSkip("TMP.S.A0001"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); return ReadAttribute(kIdentityAlpha, GetEndpoint(1), TemperatureMeasurement::Id, TemperatureMeasurement::Attributes::MinMeasuredValue::Id, true, chip::NullOptional); } - case 3: { - LogStep(3, "Read the mandatory attribute: MaxMeasuredValue"); + case 2: { + LogStep(2, "Read the mandatory attribute: MaxMeasuredValue"); VerifyOrDo(!ShouldSkip("TMP.S.A0002"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); return ReadAttribute(kIdentityAlpha, GetEndpoint(1), TemperatureMeasurement::Id, TemperatureMeasurement::Attributes::MaxMeasuredValue::Id, true, chip::NullOptional); } + case 3: { + LogStep(3, "Read the mandatory attribute: MeasuredValue"); + VerifyOrDo(!ShouldSkip("TMP.S.A0000"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); + return ReadAttribute(kIdentityAlpha, GetEndpoint(1), TemperatureMeasurement::Id, + TemperatureMeasurement::Attributes::MeasuredValue::Id, true, chip::NullOptional); + } case 4: { LogStep(4, "Read the optional attribute: Tolerance"); VerifyOrDo(!ShouldSkip("TMP.S.A0003"), return ContinueOnChipMainThread(CHIP_NO_ERROR)); diff --git a/zzz_generated/darwin-framework-tool/zap-generated/test/Commands.h b/zzz_generated/darwin-framework-tool/zap-generated/test/Commands.h index a99e1dccb3d26f..5b07d41b2116d9 100644 --- a/zzz_generated/darwin-framework-tool/zap-generated/test/Commands.h +++ b/zzz_generated/darwin-framework-tool/zap-generated/test/Commands.h @@ -22335,7 +22335,7 @@ class Test_TC_I_1_1 : public TestCommandBridge { break; case 5: ChipLogProgress(chipTool, " ***** Test Step 5 : Read the optional command(TriggerEffect) in AcceptedCommandList\n"); - if (ShouldSkip("I.C.C40.Tx")) { + if (ShouldSkip("I.S.C40.Rsp")) { NextTest(); return; } @@ -52072,28 +52072,28 @@ class Test_TC_TMP_2_1 : public TestCommandBridge { err = TestWaitForTheCommissionedDeviceToBeRetrieved_0(); break; case 1: - ChipLogProgress(chipTool, " ***** Test Step 1 : Read the mandatory attribute: MeasuredValue\n"); - if (ShouldSkip("TMP.S.A0000")) { + ChipLogProgress(chipTool, " ***** Test Step 1 : Read the mandatory attribute: MinMeasuredValue\n"); + if (ShouldSkip("TMP.S.A0001")) { NextTest(); return; } - err = TestReadTheMandatoryAttributeMeasuredValue_1(); + err = TestReadTheMandatoryAttributeMinMeasuredValue_1(); break; case 2: - ChipLogProgress(chipTool, " ***** Test Step 2 : Read the mandatory attribute: MinMeasuredValue\n"); - if (ShouldSkip("TMP.S.A0001")) { + ChipLogProgress(chipTool, " ***** Test Step 2 : Read the mandatory attribute: MaxMeasuredValue\n"); + if (ShouldSkip("TMP.S.A0002")) { NextTest(); return; } - err = TestReadTheMandatoryAttributeMinMeasuredValue_2(); + err = TestReadTheMandatoryAttributeMaxMeasuredValue_2(); break; case 3: - ChipLogProgress(chipTool, " ***** Test Step 3 : Read the mandatory attribute: MaxMeasuredValue\n"); - if (ShouldSkip("TMP.S.A0002")) { + ChipLogProgress(chipTool, " ***** Test Step 3 : Read the mandatory attribute: MeasuredValue\n"); + if (ShouldSkip("TMP.S.A0000")) { NextTest(); return; } - err = TestReadTheMandatoryAttributeMaxMeasuredValue_3(); + err = TestReadTheMandatoryAttributeMeasuredValue_3(); break; case 4: ChipLogProgress(chipTool, " ***** Test Step 4 : Read the optional attribute: Tolerance\n"); @@ -52156,23 +52156,23 @@ class Test_TC_TMP_2_1 : public TestCommandBridge { return WaitForCommissionee("alpha", value); } - CHIP_ERROR TestReadTheMandatoryAttributeMeasuredValue_1() + CHIP_ERROR TestReadTheMandatoryAttributeMinMeasuredValue_1() { MTRBaseDevice * device = GetDevice("alpha"); MTRBaseClusterTemperatureMeasurement * cluster = [[MTRBaseClusterTemperatureMeasurement alloc] initWithDevice:device endpoint:1 queue:mCallbackQueue]; VerifyOrReturnError(cluster != nil, CHIP_ERROR_INCORRECT_STATE); - [cluster readAttributeMeasuredValueWithCompletionHandler:^(NSNumber * _Nullable value, NSError * _Nullable err) { - NSLog(@"Read the mandatory attribute: MeasuredValue Error: %@", err); + [cluster readAttributeMinMeasuredValueWithCompletionHandler:^(NSNumber * _Nullable value, NSError * _Nullable err) { + NSLog(@"Read the mandatory attribute: MinMeasuredValue Error: %@", err); VerifyOrReturn(CheckValue("status", err ? err.code : 0, 0)); if (value != nil) { - VerifyOrReturn(CheckConstraintType("measuredValue", "int16s", "int16s")); - VerifyOrReturn(CheckConstraintMinValue("measuredValue", [value shortValue], -27315)); - VerifyOrReturn(CheckConstraintMaxValue("measuredValue", [value shortValue], 32767)); + VerifyOrReturn(CheckConstraintType("minMeasuredValue", "int16s", "int16s")); + VerifyOrReturn(CheckConstraintMinValue("minMeasuredValue", [value shortValue], -27315)); + VerifyOrReturn(CheckConstraintMaxValue("minMeasuredValue", [value shortValue], 32767)); } NextTest(); @@ -52181,23 +52181,23 @@ class Test_TC_TMP_2_1 : public TestCommandBridge { return CHIP_NO_ERROR; } - CHIP_ERROR TestReadTheMandatoryAttributeMinMeasuredValue_2() + CHIP_ERROR TestReadTheMandatoryAttributeMaxMeasuredValue_2() { MTRBaseDevice * device = GetDevice("alpha"); MTRBaseClusterTemperatureMeasurement * cluster = [[MTRBaseClusterTemperatureMeasurement alloc] initWithDevice:device endpoint:1 queue:mCallbackQueue]; VerifyOrReturnError(cluster != nil, CHIP_ERROR_INCORRECT_STATE); - [cluster readAttributeMinMeasuredValueWithCompletionHandler:^(NSNumber * _Nullable value, NSError * _Nullable err) { - NSLog(@"Read the mandatory attribute: MinMeasuredValue Error: %@", err); + [cluster readAttributeMaxMeasuredValueWithCompletionHandler:^(NSNumber * _Nullable value, NSError * _Nullable err) { + NSLog(@"Read the mandatory attribute: MaxMeasuredValue Error: %@", err); VerifyOrReturn(CheckValue("status", err ? err.code : 0, 0)); if (value != nil) { - VerifyOrReturn(CheckConstraintType("minMeasuredValue", "int16s", "int16s")); - VerifyOrReturn(CheckConstraintMinValue("minMeasuredValue", [value shortValue], -27315)); - VerifyOrReturn(CheckConstraintMaxValue("minMeasuredValue", [value shortValue], 32767)); + VerifyOrReturn(CheckConstraintType("maxMeasuredValue", "int16s", "int16s")); + VerifyOrReturn(CheckConstraintMinValue("maxMeasuredValue", [value shortValue], -27314)); + VerifyOrReturn(CheckConstraintMaxValue("maxMeasuredValue", [value shortValue], 32767)); } NextTest(); @@ -52206,23 +52206,23 @@ class Test_TC_TMP_2_1 : public TestCommandBridge { return CHIP_NO_ERROR; } - CHIP_ERROR TestReadTheMandatoryAttributeMaxMeasuredValue_3() + CHIP_ERROR TestReadTheMandatoryAttributeMeasuredValue_3() { MTRBaseDevice * device = GetDevice("alpha"); MTRBaseClusterTemperatureMeasurement * cluster = [[MTRBaseClusterTemperatureMeasurement alloc] initWithDevice:device endpoint:1 queue:mCallbackQueue]; VerifyOrReturnError(cluster != nil, CHIP_ERROR_INCORRECT_STATE); - [cluster readAttributeMaxMeasuredValueWithCompletionHandler:^(NSNumber * _Nullable value, NSError * _Nullable err) { - NSLog(@"Read the mandatory attribute: MaxMeasuredValue Error: %@", err); + [cluster readAttributeMeasuredValueWithCompletionHandler:^(NSNumber * _Nullable value, NSError * _Nullable err) { + NSLog(@"Read the mandatory attribute: MeasuredValue Error: %@", err); VerifyOrReturn(CheckValue("status", err ? err.code : 0, 0)); if (value != nil) { - VerifyOrReturn(CheckConstraintType("maxMeasuredValue", "int16s", "int16s")); - VerifyOrReturn(CheckConstraintMinValue("maxMeasuredValue", [value shortValue], -27314)); - VerifyOrReturn(CheckConstraintMaxValue("maxMeasuredValue", [value shortValue], 32767)); + VerifyOrReturn(CheckConstraintType("measuredValue", "int16s", "int16s")); + VerifyOrReturn(CheckConstraintMinValue("measuredValue", [value shortValue], -27315)); + VerifyOrReturn(CheckConstraintMaxValue("measuredValue", [value shortValue], 32767)); } NextTest();