Skip to content

test(e2e): Port the React Router instrumentation API E2E app to span streaming - #23845

Draft
andreiborza wants to merge 2 commits into
ab/js-3482/framework-appsfrom
ab/js-3482/instrumentation-api
Draft

test(e2e): Port the React Router instrumentation API E2E app to span streaming#23845
andreiborza wants to merge 2 commits into
ab/js-3482/framework-appsfrom
ab/js-3482/instrumentation-api

Conversation

@andreiborza

@andreiborza andreiborza commented Sep 1, 2026

Copy link
Copy Markdown
Member

What

Ports react-router-7-framework-instrumentation to span streaming.

Why

Span streaming is the default now, so the E2E suite has to exercise it. Loader, action, middleware and fetcher assertions walk the streamed trace instead of a transaction's spans array, and the orchestrion mysql spec matches on db.query.text, since a streamed mysql span is named after its query summary.

Part of #23798

@linear-code

linear-code Bot commented Sep 1, 2026

Copy link
Copy Markdown

JS-3482

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

size-limit report 📦

Path Size % Change Change
@sentry/browser 28.57 kB - -
@sentry/browser - with treeshaking flags 26.94 kB - -
@sentry/browser - with treeshaking flags tracing without tracing 26.83 kB - -
@sentry/browser (incl. Tracing) 48.87 kB - -
@sentry/browser (incl. Tracing + Span Streaming) 48.88 kB - -
@sentry/browser (incl. Tracing, Profiling) 51.8 kB - -
@sentry/browser (incl. Tracing, Replay) 88.36 kB - -
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 77.76 kB - -
@sentry/browser (incl. Tracing, Replay with Canvas) 93.05 kB - -
@sentry/browser (incl. Tracing, Replay, Feedback) 106.02 kB - -
@sentry/browser (incl. Feedback) 46.06 kB - -
@sentry/browser (incl. sendFeedback) 33.64 kB - -
@sentry/browser (incl. FeedbackAsync) 38.74 kB - -
@sentry/browser (incl. Metrics) 29.52 kB - -
@sentry/browser (incl. Logs) 29.81 kB - -
@sentry/browser (incl. Metrics & Logs) 30.45 kB - -
@sentry/react 30.32 kB - -
@sentry/react (incl. Tracing) 51.08 kB - -
@sentry/vue 35.74 kB - -
@sentry/vue (incl. Tracing) 51.14 kB - -
@sentry/svelte 28.6 kB - -
CDN Bundle 30.36 kB - -
CDN Bundle (incl. Tracing) 49.52 kB - -
CDN Bundle (incl. Logs, Metrics) 32.59 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) 51.43 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) 73.19 kB - -
CDN Bundle (incl. Tracing, Replay) 87.01 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) 88.88 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) 92.94 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) 94.84 kB - -
CDN Bundle - uncompressed 89.97 kB - -
CDN Bundle (incl. Tracing) - uncompressed 147.58 kB - -
CDN Bundle (incl. Logs, Metrics) - uncompressed 96.27 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed 153.27 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed 225.43 kB - -
CDN Bundle (incl. Tracing, Replay) - uncompressed 267.07 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed 272.75 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 280.77 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed 286.44 kB - -
@sentry/nextjs (client) 53.7 kB - -
@sentry/sveltekit (client) 49.3 kB - -
@sentry/core/server 40.74 kB - -
@sentry/core/browser 13.42 kB - -
@sentry/node 123.87 kB +0.02% +18 B 🔺
@sentry/node/import (ESM hook with diagnostics-channel injection) 81.4 kB - -
@sentry/node - without tracing 88.2 kB +0.03% +22 B 🔺
@sentry/node - without channel injection 103.3 kB +0.02% +16 B 🔺
@sentry/aws-serverless 96.56 kB +0.03% +23 B 🔺
@sentry/cloudflare (withSentry) - minified 201.23 kB - -
@sentry/cloudflare (withSentry) 500.94 kB - -

View base workflow run

@andreiborza
andreiborza force-pushed the ab/js-3482/instrumentation-api branch 2 times, most recently from 2f982ae to a9e6808 Compare September 1, 2026 14:56
@andreiborza
andreiborza force-pushed the ab/js-3482/instrumentation-api branch 3 times, most recently from cf5c7f9 to 9e03698 Compare September 1, 2026 16:05
@andreiborza
andreiborza force-pushed the ab/js-3482/instrumentation-api branch from 9e03698 to edd1076 Compare September 1, 2026 16:37
…streaming

Removes the `traceLifecycle: 'static'` pin from
`react-router-7-framework-instrumentation` and rewrites its specs against
streamed span v2.

Loader, action, middleware and fetcher assertions now walk the streamed trace
instead of a transaction's `spans` array. The orchestrion mysql spec matches on
`db.query.text`, since a streamed mysql span is named after its query summary.
Left the fetcher test on collectStreamedSpans: it already scopes children by
walking down from the fetcher span, and whether that span is a segment under
streaming is not something to assume.
@andreiborza
andreiborza force-pushed the ab/js-3482/instrumentation-api branch from edd1076 to 7d44686 Compare September 1, 2026 16:51

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 7d44686. Configure here.


const transactionEvent = await transactionEventPromise;
const spans = transactionEvent.spans || [];
const spans = await spansPromise;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Child span collection can flake

Medium Severity

collectStreamedTrace is used without an isDone predicate in tests that then assert on child spans. That helper resolves as soon as the segment arrives, and streamed children can flush after it, so loader, middleware, redis, and mysql assertions can fail even when the spans are later sent. The same PR already waits for those children in collectUntilSegment, and the sibling react-router-7-framework tests do too. This is flagged because the review rules call out races when waiting on telemetry that can arrive in arbitrary order, including in lazy.server.test.ts.

Additional Locations (2)
Fix in Cursor Fix in Web

Triggered by project rule: PR Review Guidelines for Cursor Bot

Reviewed by Cursor Bugbot for commit 7d44686. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant