test(e2e): Add a static trace lifecycle Next.js 16 test app - #23834
Merged
Conversation
Contributor
size-limit report 📦
|
chargome
force-pushed
the
test/e2e-nextjs-16-static
branch
from
September 1, 2026 12:46
27f4b3c to
5f23236
Compare
chargome
changed the title
Adds `nextjs-16-static`, a copy of `nextjs-16` that keeps the `traceLifecycle: 'static'` pins and the transaction-based specs, so the static trace lifecycle keeps end-to-end coverage once the main Next.js suites move to span streaming. Its `sentryTest` variants are dropped, so it adds one CI row rather than four. The webpack, latest and canary dimensions stay covered by `nextjs-16` itself. Ref #23802 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
chargome
force-pushed
the
test/e2e-nextjs-16-static
branch
from
September 2, 2026 10:58
5f23236 to
c2fe5e4
Compare
chargome
marked this pull request as ready for review
September 2, 2026 12:40
chargome
requested review from
JPeer264,
Lms24,
RulaKhaled,
andreiborza and
s1gr1d
September 2, 2026 12:41
JPeer264
approved these changes
Sep 2, 2026
chargome
added a commit
that referenced
this pull request
Sep 2, 2026
Ports `nextjs-16` to span streaming: removes the `traceLifecycle: 'static'` pins and rewrites the specs onto streamed spans, using `collectStreamedSpans` where a test asserts on children of a segment span. Route-handler specs match the server span on the event's own trace so batching cannot pair spans across specs. `http.client` span names are low cardinality under streaming (`GET localhost`), which also mattered for the old name being used as a matcher. The middleware isolation-scope and breadcrumb assertions were dropped, having no span v2 equivalent. `nextjs-16-static` (#23834) keeps the transaction-based versions of these specs. Ref #23802 Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
nextjs-16-static, a copy ofnextjs-16that keeps thetraceLifecycle: 'static'pins and the transaction-based specs, so the static trace lifecycle keeps end-to-end coverage once the main Next.js suites move to span streaming.Ref #23802