fix(jest): preserve custom environment handleTestEvent#1461
Merged
Conversation
3371d13 to
cd8fb03
Compare
epszaw
approved these changes
May 4, 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
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.
This fixes createJestEnvironment overwriting handleTestEvent from custom Jest environments. That broke integrations such as jest-environment-puppeteer, where users rely on handleTestEvent to react to Circus events, for example taking screenshots on test_fn_failure.
The factory now captures any existing environment event handler, calls it first, and then runs Allure’s own event handling. Sync handlers, async handlers, and thrown/rejected errors are all preserved: Allure still processes the event, and Jest still receives the original failure.
Closes #1289
Checklist