From 3cde13768bba6cf4fa9f35eade2e857105d77de5 Mon Sep 17 00:00:00 2001
From: Multica Eve <eve@devv.ai>
Date: Wed, 15 Jul 2026 17:54:38 +0800
Subject: [PATCH] test(desktop): de-flake UpdatesSettingsTab preference-load
 test (#5460)

Co-authored-by: Eve <eve@multica-ai.local>
Co-authored-by: multica-agent <github@multica.ai>
---
 .../renderer/src/components/updates-settings-tab.test.tsx  | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/apps/desktop/src/renderer/src/components/updates-settings-tab.test.tsx b/apps/desktop/src/renderer/src/components/updates-settings-tab.test.tsx
index 630f72026..9bee2f4c2 100644
--- a/apps/desktop/src/renderer/src/components/updates-settings-tab.test.tsx
+++ b/apps/desktop/src/renderer/src/components/updates-settings-tab.test.tsx
@@ -85,8 +85,11 @@ describe("UpdatesSettingsTab", () => {
     const toggle = screen.getByRole("switch", {
       name: "Automatic background updates",
     });
-    await waitFor(() => expect(toggle).toBeEnabled());
-    expect(toggle).not.toBeChecked();
+    // The switch renders as <span role="switch">, so jest-dom's toBeEnabled()
+    // treats it as always enabled and does not actually wait for getPreferences
+    // to resolve. Wait on the persisted value being reflected instead, which
+    // deterministically holds until the loaded preference (false) is applied.
+    await waitFor(() => expect(toggle).not.toBeChecked());
 
     fireEvent.click(toggle);