From 02fee4c1e1204a2219fce7abb907268cf05cdbeb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20Salavisa?= Date: Wed, 5 Aug 2026 12:15:30 +0200 Subject: [PATCH] fix(e2e): give the plan-mode projection assertion the same timeout as its siblings (#2273) Co-authored-by: Kandev Agent Co-authored-by: Claude Opus 5 (1M context) --- apps/web/e2e/tests/workflow/workflow-automation.spec.ts | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/apps/web/e2e/tests/workflow/workflow-automation.spec.ts b/apps/web/e2e/tests/workflow/workflow-automation.spec.ts index 1d56f186e2..13d2b4afdd 100644 --- a/apps/web/e2e/tests/workflow/workflow-automation.spec.ts +++ b/apps/web/e2e/tests/workflow/workflow-automation.spec.ts @@ -226,8 +226,13 @@ test.describe("Workflow automation", () => { await expect(session.planModeInput()).toBeVisible({ timeout: 15_000 }); // The active kanban projection must win over any stale all-workflow - // snapshot that was already in flight when the turn completed. - await expect(session.taskInSection("Plan Mode Workflow Task", "Turn Finished")).toBeVisible(); + // snapshot that was already in flight when the turn completed. That + // reconciliation is exactly what this waits on, so it needs the same + // explicit budget as the assertions above — on the default expect timeout + // it loses the race under a loaded 14-shard run while passing locally. + await expect(session.taskInSection("Plan Mode Workflow Task", "Turn Finished")).toBeVisible({ + timeout: 15_000, + }); }); /**