Remove JUnit 4 @RunWith annotations that do not require an @ExtendsWith replacement
org.openrewrite.java.testing.junit5.RemoveObsoleteRunners
Some JUnit 4 @RunWith
annotations do not require replacement with an equivalent JUnit Jupiter @ExtendsWith
annotation. This can be used to remove those runners that either do not have a JUnit Jupiter equivalent or do not require a replacement as part of JUnit 4 to 5 migration.
Recipe source
GitHub, Issue Tracker, Maven Central
groupId: org.openrewrite.recipe
artifactId: rewrite-testing-frameworks
version: 2.7.0
Options
Usage
This recipe has required configuration parameters. Recipes with required configuration parameters cannot be activated directly. To activate this recipe you must create a new recipe which fills in the required parameters. In your rewrite.yml
create a new recipe with a unique name. For example: com.yourorg.RemoveObsoleteRunnersExample
. Here's how you can define and customize such a recipe within your rewrite.yml:
Now that com.yourorg.RemoveObsoleteRunnersExample
has been defined activate it and take a dependency on org.openrewrite.recipe:rewrite-testing-frameworks:2.7.0 in your build file:
Add the following to your
build.gradle
file:
Run
gradle rewriteRun
to run the recipe.
See how this recipe works across multiple open-source repositories
The community edition of the Moderne platform enables you to easily run recipes across thousands of open-source repositories.
Please contact Moderne for more information about safely running the recipes on your own codebase in a private SaaS.
Contributors
Tyler Van Gorder, Knut Wannheden, Sam Snyder, Jonathan Schneider, Michael Keppler, Aaron Gershman, Patrick Way
Last updated