I've encountered a problem while running tests on ThermostatCluster:
Step 16
WARNING | 2024-04-10 13:13:17.703276 | Test Failure: The test expectation "value (2800) == 2900" is false INFO | 2024-04-10 13:13:17.709551 | Test Step Completed [FAILED]: Step 16: Test Harness Reads back OccupiedCoolingSetpoint to confirm the success of the write
Step 18
OccupiedCoolingSetpoint
WARNING | 2024-04-10 13:13:20.601786 | Test Failure: The test expectation "value (2800) == 2900" is false INFO | 2024-04-10 13:13:20.602152 | Test Step Completed [FAILED]: Step 18: Test Harness Reads back OccupiedCoolingSetpoint to confirm the success of the write
OccupiedHeatingSetpoint
WARNING | 2024-04-10 13:13:20.926616 | Test Failure: The test expectation "value (2200) == 2300" is false INFO | 2024-04-10 13:13:20.927450 | Test Step Completed [FAILED]: Step 18: Test Harness Reads back OccupiedHeatingSetpoint to confirm the success of the write
The problem arises when the "setpoint-raise-lower" command is called during testing. Although we have implemented support for all Absolute Setpoint Limits (such as AbsMinCoolSetpointLimit, AbsMaxCoolSetpointLimit, AbsMinHeatSetpointLimit, AbsMaxHeatSetpointLimit), there's an issue when the coolingSetpoint exceeds its limit. For instance, let's say our max limit for coolingSetpoint is 2800. When attempting to set a value above this limit, the function EnforceCoolingSetpointLimits is triggered within the emberAfThermostatClusterSetpointRaiseLowerCallback.
Describe the bug
Greetings,
I've encountered a problem while running tests on ThermostatCluster:
WARNING | 2024-04-10 13:13:17.703276 | Test Failure: The test expectation "value (2800) == 2900" is false INFO | 2024-04-10 13:13:17.709551 | Test Step Completed [FAILED]: Step 16: Test Harness Reads back OccupiedCoolingSetpoint to confirm the success of the write
OccupiedCoolingSetpoint
WARNING | 2024-04-10 13:13:20.601786 | Test Failure: The test expectation "value (2800) == 2900" is false INFO | 2024-04-10 13:13:20.602152 | Test Step Completed [FAILED]: Step 18: Test Harness Reads back OccupiedCoolingSetpoint to confirm the success of the write
OccupiedHeatingSetpoint
WARNING | 2024-04-10 13:13:20.926616 | Test Failure: The test expectation "value (2200) == 2300" is false INFO | 2024-04-10 13:13:20.927450 | Test Step Completed [FAILED]: Step 18: Test Harness Reads back OccupiedHeatingSetpoint to confirm the success of the write
The problem arises when the "setpoint-raise-lower" command is called during testing. Although we have implemented support for all Absolute Setpoint Limits (such as AbsMinCoolSetpointLimit, AbsMaxCoolSetpointLimit, AbsMinHeatSetpointLimit, AbsMaxHeatSetpointLimit), there's an issue when the coolingSetpoint exceeds its limit. For instance, let's say our max limit for coolingSetpoint is 2800. When attempting to set a value above this limit, the function EnforceCoolingSetpointLimits is triggered within the emberAfThermostatClusterSetpointRaiseLowerCallback.
CoolingSetpoint = EnforceCoolingSetpointLimits(CoolingSetpoint, aEndpointId);
This function ensures that the value is within the acceptable range and cuts it to the AbsMaxCoolSetpointLimit if it exceeds it.
However, the test does not verify these limitations and consequently fails to account for this behavior. Thanks in advance.
Platform
all