Fix junit jupiter test set up #374
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
Contributor
|
CC: @mikegajda |
Contributor
|
Can take a look at the failing test right now and see what I can do there |
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.
Having
junit-platform-runneron the classpath prevents maven from running junit 5 tests. As a result, none of the tests are currently being run. You confirm this by looking at Blazar build 487. With these changes, the tests are once again run via maven.It seems as though
BaragonServicehas broken tests that need to be fixed.@ssalinas @jonathanwgoodwin @kmclarnon @Xcelled @snommit-mit