Marc-André Bombeck ece9ba90b1 Bound the two settle waits that could never time out ...

`settleBeforeMeasure` ends with a `waitForLoadState("networkidle")` whose
rejection is swallowed and a `page.evaluate` awaiting
`document.fonts.ready`. Both are written to end on their own terms, and
neither had a bound: the config leaves `actionTimeout` and
`navigationTimeout` unset, which Playwright reads as no limit, so a
single sub-resource that never completes consumes the whole test budget
rather than the wait.

The way it surfaces is the worst part. The swallowed timeout hides the
stall, the run reports whichever call was still pending when the fixture
closed the page, and the message reads

  Test timeout of 30000ms exceeded.
  Error: page.evaluate: Target page, context or browser has been closed

which names neither the surface nor the resource. Raising the budget
changes nothing, because no budget bounds an unbounded wait.

Route one font request to a handler that never answers and the current
code reproduces that message exactly; with the bound in place the same
run reaches the spec's own assertion in twelve seconds.

Six seconds is an order of magnitude above the slowest settle measured
across the suite (1.1 s, /insights at a mobile viewport).

2026-08-02 05:37:14 +02:00

..

horizontal-overflow.ts

fix(insights): let a section heading's trailing caption wrap instead of widening the page

2026-07-26 17:44:15 +02:00

mock-dashboard-snapshot.ts

fix(daily-loop): thread the overdue medication id into the digest's Log-dose link

2026-07-18 00:37:24 +02:00

mock-mood-insights.ts

perf(i18n): generate the catalog boot scripts as static assets

2026-07-07 13:15:37 +02:00

mock-populated-insights.ts

Derive score-version fixtures from the SCORE_VERSION constant

2026-08-02 00:15:29 +02:00

settle.ts

Bound the two settle waits that could never time out

2026-08-02 05:37:14 +02:00