From 6fa88fb2f6e78b5ca9b14a0116f2033bc2d791a7 Mon Sep 17 00:00:00 2001 From: Vito Sansevero Date: Thu, 22 Oct 2026 21:44:37 -0700 Subject: [PATCH] test(review): give the multi-route shell comparison a fitting time budget The dispatched CI run failed "shell geometry, tokens and controls match the concept 390x844 light" on WebKit with a 30 s test timeout (no assertion failed). Each of these tests makes twelve page loads with captures, hovers and focus checks: 15-19 s on a CI WebKit runner on main, 22-31 s on this run's loaded shard. With 2 CPUs and 3 workers it fails locally the same way (6 of 12 timed out); with a 90 s budget, as the other multi-state concept comparisons have, all 12 pass. --- tests/browser/shell-concept.spec.mjs | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tests/browser/shell-concept.spec.mjs b/tests/browser/shell-concept.spec.mjs index ce4d17c..4bb4130 100644 --- a/tests/browser/shell-concept.spec.mjs +++ b/tests/browser/shell-concept.spec.mjs @@ -179,6 +179,9 @@ async function captureFooter(page,testInfo,name) { test.beforeEach(async({request})=>{await seedConcept(request);}); for(const [width,height] of SIZES)for(const theme of THEMES)test(`shell geometry, tokens and controls match the concept ${width}x${height} ${theme}`,async({page},testInfo)=>{ + // Twelve page loads (3 routes x 2 motions, concept and production) with captures, hovers and focus: 15-19 s on a + // CI WebKit runner, and past the 30 s default when the runner is loaded (reproduced with 2 CPUs and 3 workers). + test.setTimeout(90_000); await page.setViewportSize({width,height});const result={}; for(const motion of MOTIONS)for(const [route,breadcrumb] of ROUTES) { await openConcept(page,route,theme,motion);await page.mouse.move(0,0);