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 is to migrate all unit tests to JUnit5. The version to use is defined in top-level pom.xml, but future updates of (for instance) Spring Boot may pull in a newer version.
New/updated code depending on some unit test library (e.g. testfx) should make sure to exclude JUnit4, i.e.
There are some changes developers should be acquainted with. I list them here for the sake of information. It is not an exhaustive list:
Asserthas been replaced byAssertions.@Beforeand@Afterhave been replaced by@BeforeAlland@AfterAll.assertThathas been updated to use the Hamcrest API inMatcherAssert.@Test(expected = SomeExceptionClass.class)are not supported. One may useassertThrowsinstead.@RunWith(SpringRunner.class)is replaced by@ExtendWith(SpringExtension.class)assertEqualshas to be the last parameter, not first.On top the adaptations to the JUnit5 APIs, this PR also includes a few updates to eliminate warnings.