Repository navigation
node-integration-tests: port HTTP and outgoing request suites to span streaming #24135
Description
Follow the porting recipe in the parent issue.
Highest churn group, because http.server and http.client span names became low cardinality. Do this one first, since the other groups inherit its patterns.
Suites
tracing/requests/*(15 dirs)tracing/http-client-spans/*(8 dirs)tracing/httpIntegrationtracing/tracePropagationTargetsandtracing/tracePropagationTargets/baggage-org-idproxyipv6
Twins to fold back
tracing/httpIntegration-streamedintotracing/httpIntegrationtracing/http-client-spans/fetch-basic-streamedintotracing/http-client-spans/fetch-basic
tracing/http-client-span-streamed, tracing/httpServerSpans-streamed-unrouted and tracing/requestData-streamed have no static original. Rename them to drop the -streamed suffix once nothing collides.
Activity
linear-code commentedon Sep 7, 2026
JS-3605
test(node): Port HTTP propagation and transport suites to streaming (#…
test(node): Port incoming HTTP behavior to span streaming (#25194)
test(node): Port HTTP options and hooks to span streaming (#25195)
test(node): Port outgoing HTTP client spans to streaming (#25192)
test(node): Port HTTP request suites to span streaming (#25191)
test(node): Port fetch request suites to span streaming (#25189)