test(server-utils): Remove hapi unit test that replicated SDK async-context logic#22100
Merged
Conversation
…ontext logic The suite stubbed the SDK's async context strategy via `setAsyncContextStrategy` to drive spans, duplicating SDK internals in the test layer. The hapi node integration suite already covers the orchestrion path end to end. `hapi-utils.test.ts` (pure metadata formatting, no async-context stubbing) is kept. Co-Authored-By: Opus 4.8 <noreply@anthropic.com>
andreiborza
requested review from
JPeer264,
chargome,
isaacs,
logaretm,
mydea and
s1gr1d
and removed request for
a team
logaretm
approved these changes
Jul 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
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.
Removes the hapi unit test that stubbed the SDK's async context strategy to drive spans, which replicated SDK internals in the test layer. Per the review thread in #21885, we rely on the integration tests instead.
The orchestrion path is covered by the
hapinode integration suite.hapi-utils.test.tsstays (pure metadata formatting, no async-context stubbing). The remaining unit-only assertions checked internal implementation details (setup only wrapping once when called twice, no span without an active span, accepting the ext handler as a tuple or an object) rather than the spans a user actually sees, so there was nothing meaningful to move into an integration test.Ref: #21885 (comment)