Skip to content

test(react): Fix flaky react-router-6 aborted SSE console assertion #25398

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mydea wants to merge 2 commits into
base: develop
Choose a base branch
from
+7 −5
Open

test(react): Fix flaky react-router-6 aborted SSE console assertion #25398

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3999daf
test(react): Fix flaky react-router-6 aborted SSE console assertion
mydea Oct 15, 2026
6a5a62d
test(react): Match the abort error of newer Chromium versions
mydea Oct 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions dev-packages/e2e-tests/test-applications/react-router-6/tests/sse.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,11 +85,13 @@ test('Waits for sse streaming when sse has been explicitly aborted', async ({ pa
expect(durationInSeconds(httpGet)).toBe(0);

// Spans carry no breadcrumbs, so the abort error is validated on the console directly
expect(
consoleMessages.some(
message => message.includes('Could not fetch sse') && message.includes('BodyStreamBuffer was aborted'),
),
).toBe(true);
// The abort error is logged asynchronously after the span is sent, so it may not have arrived yet.
// Older Chromium rejects with "BodyStreamBuffer was aborted", newer with the signal's abort reason.
await expect
.poll(() =>
consoleMessages.some(message => message.includes('Could not fetch sse') && message.includes('AbortError')),
)
.toBe(true);
});

test('Aborts when stream takes longer than 5s, by not updating the span duration', async ({ page }) => {
Expand Down
Loading