Address review: gate the AddWash master write on a readable mask
The master alarm switch wrote AddWashSet_7/_0 without consulting _add_wash_mask, so a device reporting a wider mask (AddWashSet_15) or a non-numeric one had it truncated to three bits -- the write that mask's own docstring rules out, while the per-moment switches already refused it. Also corrects the washer_ww6500 golden docstring: the fixture carries no /oic/d and the test passes no device_types, so the device is typed solely by the WW consumer prefix in its description. A51 is not a board token, which makes that the fragile route worth naming.
This commit is contained in:
1 parent
6003394cb2
commit
51bce3c8cf
3 files changed
+40
-5
No files matched your search
@@ -390,9 +390,12 @@ def test_registry_reproduces_golden_state_keys_for_washer_dryer_combo():
|
||||
|
||||
|
||||
def test_registry_reproduces_golden_state_keys_for_washer_ww6500():
|
||||
"""DA_WM_A51_20 front-loader, routed by /oic/d's oic.d.washer rather
|
||||
than a board token. Reports the AddWash tokens and an empty
|
||||
/wm/editcourse/vs/0, so its cycle list comes from supportedOptions."""
|
||||
"""DA_WM_A51_20 front-loader, typed solely by the WW consumer prefix in
|
||||
its /information/vs/0 description: A51 is not a board token, so with the
|
||||
description blanked this device resolves to nothing and drops to the
|
||||
unknown-device fallback. That is the fragile route this test pins.
|
||||
Reports the AddWash tokens and an empty /wm/editcourse/vs/0, so its cycle
|
||||
list comes from supportedOptions."""
|
||||
from tests.conftest import _load_device
|
||||
|
||||
resources = _load_device("washer_ww6500")
|
||||
|
||||
Reference in new issue
Block a user