-
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
[HVAC] Implement TC-TSTAT-2.2 #36023
base: master
Are you sure you want to change the base?
[HVAC] Implement TC-TSTAT-2.2 #36023
Conversation
Review changes with SemanticDiff. Analyzed 1 of 2 files.
|
PR #36023: Size comparison from 6a29ee5 to 83be40a Full report (81 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
def steps_TC_TSTAT_2_2(self) -> list[TestStep]: | ||
steps = [ | ||
TestStep("1", "Commission DUT to TH"), | ||
TestStep("2a", "Test Harness Client reads attribute OccupiedCoolingSetpoint from the DUT"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we store all initial attribute values (mainly min and max values) so that we can restore them at the end of the test? I wasn't able to run this test back to back since by the end of the test some of the attribute values don't make sense anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The exact issue I saw here is that, by the end of the test, the heatingsetpoint is very close to the abs/maxheatingsetpoint and some tests increment fixed values to heatingsetpoint which would be out of range and fail a test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This turned out to be harder than you might expect, as the default values for the thermostat cluster violate its own constraints. Once PR 36023 is merged, we can update the code to match, and then this will work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hasty are you referencing the correct PR in your comment? It is referring to this PR itself.
Co-authored-by: fesseha-eve <[email protected]>
|
||
def steps_TC_TSTAT_2_2(self) -> list[TestStep]: | ||
steps = [ | ||
TestStep("1", "Commission DUT to TH"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please change this to
TestStep("1", "Commission DUT to TH",
is_commissioning=True),
so that the TH commissions the DUT if necessary?
@hasty We have to add steps 19 to 22c as per the test plan. Here is the test plan reference: https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/cluster/thermostat.adoc#tc-tstat-2-2-setpoint-test-cases-with-server-as-dut |
This provides a Python implementation of TC-TSTAT-2.2 to replace the unused TC-TSTAT-2.2 YAML test.
Fixes #35748