You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
contexts.trace.op becomes getSpanOp(span) plus span.is_segment
contexts.trace.data['x'] becomes span.attributes['x'], which has the shape { value, type }
transaction_info.source becomes the sentry.segment.name.source attribute
Streamed child spans arrive across several envelopes, so use collectStreamedSpans wherever a test asserts on children of a segment span.
Watch the low-cardinality names for http.server and http.client spans.
Reference apps: react-router-7-spa-streaming and nextjs-16-streaming. Worked example: #23797.
Keep static trace lifecycle coverage
Before porting this group, duplicate astro-7 as-is into astro-7-static and leave that copy on the current transaction-based specs. That keeps the static trace lifecycle covered once the rest of the group moves to streaming.
The copy is verbatim; only the app name changes:
package.json -> name
start-event-proxy.mjs -> proxyServerName
every waitForTransaction / waitForError / waitForSession call in tests/
Keep traceLifecycle: 'static' in the copy's Sentry.init calls. The e2e matrix discovers apps by directory, so no CI config change is needed.
The representative is a suggestion: swap it if another app in the list exercises more of this SDK's instrumentation.
Activity
linear-code commentedon Sep 1, 2026
JS-3493
test(e2e): Add `astro-7-static` E2E app (#24075)
test(e2e): Port the astro-5 E2E app to span streaming (#24078)
test(e2e): Port the astro-4 E2E app to span streaming (#24079)
test(e2e): Port the astro-6 E2E app to span streaming (#24077)
test(e2e): Port the astro-6-cf-workers E2E app to span streaming (#24080
test(e2e): Restore dropped url attribute assertions in the astro-4 an…
test(e2e): Port the astro-7 E2E app to span streaming (#24076)
test(e2e): Port Astro 5 Cloudflare to span streaming (#25016)
github-actions commentedon Oct 7, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #25016, which was included in the 11.5.0 release.