This repository was archived by the owner on Oct 7, 2025. It is now read-only.
Run each class in it's own instrumentation (#531) #532
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
This parameter will be used to run tests from each class in a separate instrumentation instance.
…e instrumentations.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Lately, I've been using the feature of running each test in it's own instrumentation a lot.
It really helps with test isolation, but also greatly increases the run time.
As a solution, I added a parameter to run a different instrumentation for each test class, as opposed to each test method (#531).
If you are also interested in this feature, feel free to review and request changes where necessary.