-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TC-VALCC-3.1: Allow immediate open of valve #35851
base: master
Are you sure you want to change the base?
TC-VALCC-3.1: Allow immediate open of valve #35851
Conversation
If the valve can be opened before the command is complete or before the next read is done, the test will fail because it expects the transitioning phase to happen. In the spec: When the movement is complete, the device SHALL set the CurrentState attribute to the Open value. ^ this can happen before the end of the command.
Changed Files
|
PR #35851: Size comparison from 9c6c365 to fa83b47 Full report (88 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
This seems out of sync with the test plan. Is that being updated as well? |
@fessehaeve - yes, the test plan will need to be updated, I can update it from this script once this is approved. The changes to the cluster are happening in a separate branch. I should have the changes up in a PR by the SDK tomorrow, but they're orthogonal to this change - just an explanation for why I'm only doing a partial clean of the current code. |
...p/clusters/valve-configuration-and-control-server/valve-configuration-and-control-server.cpp
Outdated
Show resolved
Hide resolved
...p/clusters/valve-configuration-and-control-server/valve-configuration-and-control-server.cpp
Show resolved
Hide resolved
...p/clusters/valve-configuration-and-control-server/valve-configuration-and-control-server.cpp
Show resolved
Hide resolved
PR #35851: Size comparison from 84fb78f to 0793ceb Full report (10 builds for cc32xx, nrfconnect, qpg, stm32, tizen)
|
If the valve can be opened before the command is complete or before the next read is done, the test will fail because it expects the transitioning phase to happen AND it expects to be able to read the attribute in the intermediate state.
In the spec:
When the movement is complete, the device SHALL set the CurrentState attribute to the Open value.
^ this can happen before the end of the command.
The current implementation does actually set the current state to open immediately, but the test doesn't catch this because the current implementation also doesn't set the target back to NULL when the change to CurrentState happens.
Changes to the test:
Changes to the current cluster implementation:
Note that these changes are being done as part of an effort to refactor this cluster entirely, so changes to the implementation will be short-lived and are implemented only to allow landing the test changes before the refactor.