Move cloud-logging from JUnit4 to JUnit5 #192
Draft
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
|
@aamotharald: Note, that the JUnit 4->5 migration was part of #173 for the release-4 branch. |
|
:-) I think I have learned a lot doing the same thing again. |
KarstenSchnitter
force-pushed
the
main
branch
from
40ac9c9 to
6defb8a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
creating this as a draft-PR first as I have quite a lot to comment what I did in this PR.
Nevertheless:
NO PROD CODE got CHANGED.
ONLY TESTS and maven dependencies.
This PR mitigates technical debt and does NOT add any functionality.