-
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
Disable Thermostat Clusters attribute tests from Darwin #11446
Disable Thermostat Clusters attribute tests from Darwin #11446
Conversation
@chrisbeach59 could we instead modify the tests to write values that are within spec range? |
@andy31415 We will need to generate manual test cases. They can not be auto generated. I have a series of tests that were used to validate the pre-attribute-changed-callback. Different tests need to be run based on the FeatureMap bits. The test results. Right now the scripting engine does not support reading an attribute and using it's value as a condition for other tests. Also the featuremap remains broken for little endian cpu's. I have some #defines in the thermostat-server.cpp code to work around this. (There is a PR in the ZAP project to address this that is still pending) I am hesitant to add the manual test cases to CI until this is addressed for fear of breaking CI, again. |
@vivien-apple FIY. From my side I am approving based on comments from Chris |
PR #11446: Size comparison from 29747a2 to 40fbf02 Full report (30 builds for efr32, esp32, k32w, mbed, nrfconnect, p6, qpg, telink)
|
/rebase |
When the pre-attribute-change-callback is added to the chip-all-clusters-app it is validating against spec constraints. The auto generated tests violate these constraints and cause CI to fail.
40fbf02
to
e084a4f
Compare
* Remove Thermostat Cluster Tests from Darwin When the pre-attribute-change-callback is added to the chip-all-clusters-app it is validating against spec constraints. The auto generated tests violate these constraints and cause CI to fail. * regen ChipClustersTests.m
…#11446) * Remove Thermostat Cluster Tests from Darwin When the pre-attribute-change-callback is added to the chip-all-clusters-app it is validating against spec constraints. The auto generated tests violate these constraints and cause CI to fail. * regen ChipClustersTests.m
Problem
Thermostat Cluster Server implements constraints per the spec.
The automated test generation for the cluster generates write values that are outside constraints
blocks #11058
Change overview
What's in this PR
Added excluding of Thermostat Cluster Attribute tests to Darwin zapt template file
Testing
Validated that after changes were made and regen:
All ZAP generated files generated successfully
ChipClusterTests.m did not contain any Thermostat Cluster tests