test(e2e): Port the nestjs-12 E2E app to span streaming - #24098
Merged
Conversation
Removes the `traceLifecycle: 'static'` pin and rewrites the specs against streamed spans. Ref: #23801 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
size-limit report 📦
|
Member
Author
|
bugbot run |
…wrapper The local `waitForSegmentSpan` only re-expressed what `collectStreamedSpansUntilSegment` and `waitForStreamedSpan` already do, and was copied into every ported app. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Member
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 3dc1fa3. Configure here.
chargome
marked this pull request as ready for review
September 7, 2026 09:35
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
nicohrubec
reviewed
Sep 8, 2026
| const spans = await spansPromise; | ||
| const segmentSpan = spans.find(span => span.is_segment)!; | ||
|
|
||
| expect(segmentSpan).toMatchObject({ |
Member
There was a problem hiding this comment.
did you switch to toMatchObject from toEqual on purpose? might be better sticking to toEqual to be more exhaustive and not accidentally loose any relevant assertions?
Switches the span assertions from `toMatchObject` to `toEqual` so an unexpected field or attribute fails the test, as the transaction-based specs did. Child spans carry a bounded attribute set, so they are matched exhaustively. The segment span also carries the scope contexts, SDK integrations and user IP, which vary by machine, so it keeps `objectContaining`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
CI builds the apps with a release, so every span carries `sentry.release` there and none locally, which the exhaustive attribute matching tripped over. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…ceptor requests The file asserts on streamed spans, not transaction events. Both specs of each interceptor route also produced a trace with the same segment name, so each request now carries a `spec` query marker to tell its own trace apart. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
andreiborza
approved these changes
Sep 8, 2026
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
3 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.
Removes the
traceLifecycle: 'static'pin and rewrites the specs against streamed spans.Ref: #23801
🤖 Generated with Claude Code