Replace JUnit 4 Assertions with JUnit Jupiter

This new jSparrow release brings the final step on transitioning to JUnit 5!

Replace JUnit 4 Assertions with JUnit Jupiter

This rule contributes to a stepwise transition to JUnit 5 by replacing the JUnit 4 assertion methods by the equivalent JUnit 5 ones. For more details, visit our online documentation.

Here is a short example, the following test class:

is transformed to:

This new rule brings jSparrow to a total of 93 automatic refactoring rules.

Find out more information in the Release Notes for jSparrow Eclipse and jSparrow Maven!

“Simple things should be simple, complex things should be possible.”
― Alan Kay

Happy Coding!

Promotion pop-up

jSparrow 22% off promotion image