project-chip
[Bug] TC-LVL-4.1 Fails if optional Features LVL.S.A0002 and LVL.S.A0003 are not selected in pics
Describe the bug
Test Step 4g tries executes:
levelcontrol move-to-level null 0 0 0 0xAAAAAAAAAAAA 1
As a result the Test Case fails
Steps to reproduce the behavior
Run Level Control Cluster Test with s LVL.S.A0002 and LVL.S.A0003 not set.
Expected behavior
should exec
levelcontrol move-to-level 1 0 0 0 0xAAAAAAAAAAAA 1
instead of
levelcontrol move-to-level null 0 0 0 0xAAAAAAAAAAAA 1
Log files
No response
PICS file
No response
Screenshots
No response
Environment
No response
Additional Information
No response
The underlying issue seems to be a test plan issue
(from 1.4.2 specs)
[TC-LVL-4.1] Move Verification (DUT as Server)
4f) correctly requires
LVL.S.C01.Rsp(Move) & LVL.S.A0002(MinLevel)
to read the MinLevel attribute
4g) however does not take LVL.S.A0002 into account, instead it specifies
LVL.S.C01.Rsp(Move) & LVL.S.A0000(CurrentLevel)
and requires that
TH sends a MoveToLevel command to immediately (TransitionTime =0) set the level to MinLevel from step 4f
On a sidenote, the test file differs slightly in requirements and uses LVL.S.F01(LT) instead of LVL.S.A0000(CurrentLevel)
- label: "Step 4g: TH sends a MoveToLevel to set the level to MinLevel"
PICS: LVL.S.C01.Rsp && LVL.S.F01
This cannot work for devices that don't implement optional attribute "MinLevel" unless you maybe consider the test setup instructions that state "The levels used in this test assume that MinLevel=1 and MaxLevel=254."
The changes implementing this were introduced here and are still on master branch: https://github.com/project-chip/connectedhomeip/commit/9cac2770028c4991590d8f8cc36a12b3bf5867f2
