[CERT-TEST-FAILURE] - TC-WASHERCTRL-3.2 - Test failed

[KishokG]

Feature Area

Other

Test Case

TC-WASHERCTRL-3.2

Reproduction steps

1. Bring up the DUT with all-clusters-app.
2. Pair the DUT using chip-tool through "onnetwork" transport.
3. Run the command ./chip-tool laundrywashercontrols write spin-speed-current 20 1 1

Expected Outcome:

[1692858657.915468][6723:6725] CHIP:DMG: StatusIB =
[1692858657.915511][6723:6725] CHIP:DMG: {
[1692858657.915570][6723:6725] CHIP:DMG: status = CONSTRAINT_ERROR,
[1692858657.915639][6723:6725] CHIP:DMG: },

Actual Outcome:

[1692858657.915468][6723:6725] CHIP:DMG: StatusIB =
[1692858657.915511][6723:6725] CHIP:DMG: {
[1692858657.915570][6723:6725] CHIP:DMG: status = 0x00 (SUCCESS),
[1692858657.915639][6723:6725] CHIP:DMG: },

Bug prevalence

Whenever I try to write SpinSpeedCurrent with unsupported value.

GitHub hash of the SDK that was being used

5532798

Platform

raspi

Anything else?

• In TC-WASHERCTRL-2.1, STEP 1 TH reads from the DUT the the SpinSpeeds attribute we get SpinSpeeds: 4 entries [ 1, 2, 3, 4].
• So as per spec, the SpinSpeedCurrent should be able to toggle between 1-4 with SUCCESS response and if user attempts to write a value that doesn't correspond to a valid index the DUT should respond with CONSTRAINT_ERROR.
• But with current sample app we are able to write the value up to 4 - 31 without any issue.

[crlonxp]

We use TOT source which include this commit:
2e59655 (HEAD -> master, origin/master, origin/HEAD) Add the Pre-Attribute checking for laundry washer controls cluster (#28618)
The test can pass. The log is attached

issue-28863.zip

[KishokG]

Issue resolved in 2e59655