abb754e6a5
The SSE connection to /api/events (added with notifications) keeps the network in-flight forever, so `networkidle` never resolves. Each save in the affected helpers timed out at 30s × 3 retries, which both broke the run and made it suspiciously long. Switched to explicit waits: - "Profile saved." text after settings save (notifications + public-content + social) - "No pending follow requests." after Approve (social.test.ts) - toBeHidden poll for the Mark all read button (notifications) - toBeVisible poll for the empty-state copy after Approve (notifications) These are all the affected `networkidle` call sites in e2e. The fetcher.Form pattern stays — once the action commits, the page revalidates and the post-state element appears. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| fixtures | ||
| auth.test.ts | ||
| demo-bot.test.ts | ||
| integration.test.ts | ||
| journal.test.ts | ||
| notifications.test.ts | ||
| planner.test.ts | ||
| public-content.test.ts | ||
| settings.test.ts | ||
| social.test.ts | ||