Update processor tests to use JUnit 5 #10379
Merged
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.
Hey @sebersole, @gavinking
I was looking at where we still have junit 4 rules/runners and noticed that the entire suite for the processor is junit4 based. This PR changes that 😃.
I'm looking at Envers tests now, and I think I found how to make those work with "parameterized classes extension". I'll experiment a bit more with those and then see if I can convert them all 🙈
with Envers and processor tests converted it seems we would only need to update core tests to get it all on JUnit 5 🤞🏻 😄
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.