From f85948488d7e62c80bd033e1d41e5d3cc86d9f02 Mon Sep 17 00:00:00 2001
From: Matt <matt@letsbe.solutions>
Date: Thu, 14 May 2026 22:50:51 +0200
Subject: [PATCH] =?UTF-8?q?test:=20update=20GDPR=20export=20test=20for=20d?=
 =?UTF-8?q?ashed=20jobId=20=E2=80=94=20companion=20to=20F3?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The test asserted the old `gdpr-export:${id}` shape that BullMQ rejects.
Mirrors the production fix in 7da3c5b.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 tests/integration/gdpr-export.test.ts | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/tests/integration/gdpr-export.test.ts b/tests/integration/gdpr-export.test.ts
index b303be91..0944c671 100644
--- a/tests/integration/gdpr-export.test.ts
+++ b/tests/integration/gdpr-export.test.ts
@@ -166,7 +166,8 @@ describe('requestGdprExport', () => {
     expect(add).toHaveBeenCalledWith(
       'gdpr-export',
       expect.objectContaining({ exportId: row.id, emailToClient: true }),
-      expect.objectContaining({ jobId: `gdpr-export:${row.id}` }),
+      // F3: BullMQ 5.x rejects colons in custom job IDs — switched to dash.
+      expect.objectContaining({ jobId: `gdpr-export-${row.id}` }),
     );
 
     // Cleanup the mock so other tests don't see a stubbed queue.