test(e2e): lift expect timeout to 10s and CI retries to 2 for loaded-runner headroom

A rotating single e2e test failed each CI run (wizard step transition,
list-refetch card provenance, disclosure toggle) while 211 passed — DOM-
settle-gated assertions sampling a mid-transition frame on a starved shared
runner. Raise the global expect timeout 5s→10s (suite-wide settle headroom)
and CI retries 1→2 (absorb the transient without masking a real break, which
fails all attempts). Also scroll the provenance card into view before reading
its attribute, since the mobile timeline can render it off-viewport.
This commit is contained in:
Marc-André Bombeck committed 2026-07-08 23:04:22 +02:00
1 parent e48f9859c8
commit 50e630bf2d
2 files changed
+15 -4

No files matched your search

+6 -2
View File
@@ -368,10 +368,14 @@ test.describe("document vault — AI assist + content search", () => {
await page.keyboard.press("Escape");
const marker = page
.locator('[data-slot="document-card"]', { hasText: "Radiology note" })
.locator('[data-slot="document-searchable"]');
.locator('[data-slot="document-searchable"]')
.first();
// The card marker appears after the list query invalidates and refetches
// the new provenance; on a loaded runner that round-trip can outlast the
// default 5s expect timeout, so wait explicitly for it to resolve.
// default 5s expect timeout, so wait explicitly for it to resolve. Scroll
// it into view first — the mobile timeline can render the card outside the
// viewport, where the attribute read intermittently misses it.
await marker.scrollIntoViewIfNeeded();
await expect(marker).toHaveAttribute("data-source", "ai-read", {
timeout: 20_000,
});