fix(jest): properly parent beforeAll/afterAll hooks to suite span #7078
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.
Description
This PR implements proper span parenting for Jest's
beforeAllandafterAllhooks to ensure they are traced as children of the test suite span, similar to the Mocha implementation in PR #2167.Problem
Currently, Jest's
beforeAllandafterAllhooks are not properly instrumented with spans that are parented to the test suite span. This means that any work done in these suite-level hooks is not visible in the trace hierarchy, making it difficult to debug setup/teardown performance issues.Solution
This implementation follows the same pattern used in the Mocha integration:
beforeAll/afterAll) and test-level hooks (beforeEach/afterEach)Changes
Core Implementation
getHookType()andisSuiteLevelHook()functions to identify hook typessuiteFnChfor suite hook executionsuiteSpanContextto DatadogEnvironment andsuiteContextsmapci:jest:suite:fnchannel handlingTesting
Related Issues
Fixes #5677
Testing
Notes
This is a draft PR for initial review. The implementation has been tested locally and follows the established patterns from the Mocha integration.