From 52448a374e71cdad86e35dca445aad63eb3db3c0 Mon Sep 17 00:00:00 2001 From: maziggy Date: Thu, 18 Jun 2026 12:07:56 +0200 Subject: [PATCH] test(settings): include preset fields in /ui-preferences pin assertion MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Follow-up to the temperature & fan-speed presets feature — the TestUiPreferencesEndpoint.test_returns_expected_field_set test pins the exact set of fields the endpoint exposes (so adding a sensitive field by accident fails the assert). The 4 preset fields were added to _UI_PREFERENCE_FIELDS without updating the pin, breaking the full backend test run. --- backend/tests/integration/test_settings_ui_preferences.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/backend/tests/integration/test_settings_ui_preferences.py b/backend/tests/integration/test_settings_ui_preferences.py index 769c87a17..7dca6596a 100644 --- a/backend/tests/integration/test_settings_ui_preferences.py +++ b/backend/tests/integration/test_settings_ui_preferences.py @@ -88,6 +88,10 @@ class TestUiPreferencesEndpoint: "ams_temp_good", "ams_temp_fair", "bed_cooled_threshold", + "nozzle_temp_presets", + "bed_temp_presets", + "chamber_temp_presets", + "fan_speed_presets", } assert set(data.keys()) == expected