Refactor JUnit 3 and JUnit 4 tests to JUnit 5, remove JUnit 4 dependency#6214
Merged
vlsi merged 2 commits intoapache:masterfrom Dec 29, 2023
Merged
Refactor JUnit 3 and JUnit 4 tests to JUnit 5, remove JUnit 4 dependency#6214vlsi merged 2 commits intoapache:masterfrom
vlsi merged 2 commits intoapache:masterfrom
Conversation
It is a step towards removing junit:junit:4.x dependency
…dency Now we have only JUnit 5 on the test compilation classpath, and IDE no longer suggests multiple different @test and assertEquals implementations.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Currently, we have multiple
@TestandassertEqualson the classpath which is inconvenient.Removing JUnit 4 makes the maintenance easier.