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
test(e2e): Tell the two nestjs-basic interceptor specs traces apart (#24211)
Both specs of each interceptor route produce a trace with the same
segment name, and `collectStreamedSpans` resolves with any trace
satisfying the predicate, so a leftover trace from the preceding spec
could satisfy it instead. Each request now carries a `spec` query
marker, which lands in `url.query` and not in the span name.
This was meant to ship with #24099 but landed on the branch after it
merged.
Ref: #23801
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
@@ -328,9 +340,9 @@ test('API route trace includes nest interceptor spans before route execution. Sp
328
340
test('API route trace includes exactly one nest interceptor span after route execution. Spans created in controller and in interceptor are nested correctly',async({
@@ -356,9 +368,12 @@ test('API route trace includes exactly one nest interceptor span after route exe
356
368
test('API route trace includes nest async interceptor spans before route execution. Spans created in and after async interceptor are nested correctly',async({
@@ -384,9 +399,12 @@ test('API route trace includes nest async interceptor spans before route executi
384
399
test('API route trace includes exactly one nest async interceptor span after route execution. Spans created in controller and in async interceptor are nested correctly',async({
0 commit comments