fix: propagate outer plugins into multi-suite sub-suites#5
Merged
Conversation
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
1 participant
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.
When a plugin was registered at the outer config level alongside
multiSuite(), its per-file hooks (runner, onTestProcess, ipc) were not applied to sub-suite test files because the innerpoku()call only receivedconfig.pluginsfrom each sub-suite.This PR forwards outer plugins into each sub-suite with
setup,teardown, anddiscoverFilesstripped, so lifecycle keeps running exactly once at the outer level while per-file hooks now fire for every sub-suite file.