* test(library): read one "now" in the fixture and the page across midnight
The concept fixture recorded each prompt's last use with the database's wall
clock at seeding, while the page computed "today" from its own clock at
render. A run seeded at 23:59:5x UTC and rendered after midnight read "Used
yesterday" against the concept's "Used today" (PR #284, frontend coverage
shard 2/3).
The concept fixture now takes one instant (optional "now" through the
concept reset hook, the wall clock otherwise) for every last use, mtime and
run time it writes and returns it as manifest.now; seedConceptAt fixes the
browser's Date at that instant. The Library and Images concept specs seed
through it, and the two workspace specs that assert "Used today" and the
"Today" caption fix the page clock at the time they patch or seed. A new
test starts the browser at 23:59:58 UTC, seeds at that instant and passes
midnight before either document opens.
* test(activity): judge the lost-server backoff by its gaps, not a timed window
"lost server clears the pill and marks jobs ended" counted failed job-list
re-reads in a 3.5 s waitForTimeout window that started once the test saw
the ended job. Re-reads back off 1 s, 2 s, then 4 s, so the third lands
4 s after the second. A runner that noticed the ended job more than 0.5 s
late moved the window over the third read (firefox shard 1/2 on #287:
3 reads, expected at most 2).
The test now waits for the third failed read and asserts the gaps between
reads: at least 2 s, then at least 4 s, with 100 ms allowed for the
request being reported late.
* test(activity): replace the spec's remaining timer waits with gaps and a run-out clock
Three checks in workspace-activity.spec.mjs waited on wall-clock timers:
- "lost server": waitForTimeout(2500), then at most 2 list reads. The read
after the one that found the restart must be the periodic poll, so the
test now waits for it and asserts the gap is at least POLL_MS (less
100 ms for late request reporting). Any extra read lands in that gap.
- "200-row cap note" (review M12): waitForTimeout(1500), then no detail
read. The page's timers are now Playwright's clock. The test runs one
read-throttle interval out, so any read the counter update scheduled is
sent before the log opens. Once the log's read has answered, exactly one
read must be listed.
- "busy start" (review M14): waitForTimeout(7000), then the link toast is
still visible. The test now runs the page's clock 7 s on, which fires a
6.5 s clear however slowly the runner got there.
RED, each against a temporary product change: POLL_MS 3000 (gap 3004 ms,
expected at least 14900), detail re-read on new log lines while the log is
closed (an unexpected read), LINK_TOAST_MS 6500 (toast link gone), and
BACKOFF_FIRST_MS 200 for the earlier backoff check (gap 407 ms, expected at
least 1900).
Vito
08151ca93d