Run junit tests in parallel #599
Open
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
…g junit tests in parallel. Allow tests to use at most half the available cores. Add annotation to the CuteNetlibCase class to make it run in parallel. `@Execution(ExecutionMode.CONCURRENT)`
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 PR shows how junit can use many cores and threads to run tests in parallel. This make running tests use less wall clock time. This should not be added to benchmarks, because their result are affected by running in parallel.
The relevant junit settings are located in the added file junit-platform.properties.
Present settings let tests use at most half of the available cores while running in parallel.
The present default for classes are to run in one thread (default=SAME_THREAD in properties file).
The annotation
@Execution(ExecutionMode.CONCURRENT)was added to CuteNetlibCase.java as an example of how to enable parallel run when it is not on by default. It is possible to make running in parallel the default for all classes by setting default=CONCURRENT in properties file.If running tests in parallel is a good idea, then the above annotation can be added to all none benchmark tests.
And the properties in the properties file can be modified to suit the project better.
junit documentation:
https://junit.org/junit5/docs/snapshot/user-guide/#writing-tests-parallel-execution