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.
Finally paving the way for JUnit5. In order to proof that we are not forced to migrate all tests at once I updated only two tests showcasing that JUnit5 support works. All the other tests remain on JUnit4 for now and will be migrated over time while new tests can already be written based on JUnit5.
Since JUnit5 became the default in
Spring Boot 2.2.x
(cf. #14736) I decided to wait for theSpring Boot 2.3.x
migration (#1018) to be finished. This simplify required changes and we don't have to remove handcrafted switch from JUnit4 to JUnit5 later on. However as a expected consequence CircleCI will fail and PR is blocked untilSpring Boot 2.3.x
is available on master