From 8678a3edc468c866c300f11bc33ba2313a78ce84 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Bombeck?= Date: Sun, 25 Oct 2026 15:16:14 +0100 Subject: [PATCH] test(recovery): keep the weekly-copy push test to its one signal With the real dump health wired in, an empty test database also reports a missing dump. The file follows the weekly copy alone; the dump signal is judged in the readiness unit tests. --- tests/integration/recovery-readiness-notify.test.ts | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/tests/integration/recovery-readiness-notify.test.ts b/tests/integration/recovery-readiness-notify.test.ts index 2f199f482..863f2220b 100644 --- a/tests/integration/recovery-readiness-notify.test.ts +++ b/tests/integration/recovery-readiness-notify.test.ts @@ -48,6 +48,13 @@ vi.mock("@parse/node-apn", () => { return { default: { Provider, Notification }, Provider, Notification }; }); +// This file follows the weekly-copy signal alone. The database dump has its +// own signal, judged in the readiness unit tests; here no dump is scheduled, +// so an empty test database does not add a dump alarm of its own. +vi.mock("@/lib/recovery/database-dump-health", () => ({ + readDatabaseBackupHealth: async () => null, +})); + vi.mock("@/lib/db-compat", () => ({ ensureDbCompatibility: vi.fn().mockResolvedValue(undefined), }));