Skip to content

Apply the JUnit 5 best practices to the tests - #176

Merged
slachiewicz merged 1 commit into
masterfrom
agent/junit5-best-practices
Oct 12, 2026
Merged

slachiewicz merged 1 commit into
masterfrom
agent/junit5-best-practices

Conversation

@slachiewicz

Copy link
Copy Markdown
Member

Applies OpenRewrite's JUnit5BestPractices recipe (rewrite-testing-frameworks 3.44.0) to the tests: package-private test classes and methods, no unused throws clauses, expected-then-actual assertEquals arguments and the dedicated JUnit 5 assertions. Only test sources change.

Verified: same test count per class before and after, 27 tests, mvn -B test green.

Part of mojohaus/.github#15.

Generated with OpenRewrite's org.openrewrite.java.testing.junit5.JUnit5BestPractices
(rewrite-testing-frameworks 3.44.0), formatted with Spotless.
@slachiewicz slachiewicz added the maintenance Cleanup, refactoring or other internal change label Oct 12, 2026
@slachiewicz
slachiewicz marked this pull request as ready for review October 12, 2026 09:42
@slachiewicz
slachiewicz merged commit 40082d6 into master Oct 12, 2026
11 checks passed
@slachiewicz
slachiewicz deleted the agent/junit5-best-practices branch October 12, 2026 09:42
@github-actions github-actions Bot added this to the next-release milestone Oct 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Cleanup, refactoring or other internal change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant