This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
feat: reuse worker process between test types #242
Merged
Conversation
This file contains 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
When two test types only differ in the last few environments, and none of them has `beforeAll` or `afterAll`, we can reuse the worker. In this case, the worker won't have to run new `beforeAll`/`afterAll` methods, and will update the list of envs to run `beforeEach`/`afterEach` for the next test.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 two test types only differ in the last few
environments, and none of them has
beforeAllorafterAll,we can reuse the worker. In this case, the worker won't have
to run new
beforeAll/afterAllmethods, and will updatethe list of envs to run
beforeEach/afterEachfor the next test.