junitlauncher - Added fork mode support #174
Open
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
azotcsit
force-pushed
the
junitlauncher-fork-mode
branch
from
5808e79
to
df9d846
Compare
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.
Context
I'm working on migration of Cassandra to JUnit5 (https://issues.apache.org/jira/browse/CASSANDRA-16630). Our test running code is heavily customized and relies onto forkMode property. Unfortunately, junitlauncher task does not have any equivalent. The purpose of this change is to introduce a way to run tests independently (in separate JVMs).
Behavior
This PR does not change any existing behavior. By default, the tests will be run in the same forked JVM (aka mode="once").
Summary of the changes
nodeattribute toforkelementJUnitLauncherTaskI'm not sure
JUnitLauncherTaskTestis run during./build clean test, hence the test might be broken.