JUnit 4 @RunWith to JUnit Jupiter @ExtendWith

org.openrewrite.java.testing.junit5.RunnerToExtension

Replace runners with the JUnit Jupiter extension equivalent.

Recipe source

GitHub, Issue Tracker, Maven Central

  • groupId: org.openrewrite.recipe

  • artifactId: rewrite-testing-frameworks

  • version: 2.6.0

Options

TypeNameDescriptionExample

List

runners

The fully qualified class names of the JUnit 4 runners to replace. Sometimes several runners are replaced by a single JUnit Jupiter extension.

org.springframework.test.context.junit4.SpringRunner

String

extension

The fully qualified class names of the JUnit Jupiter extension.

org.springframework.test.context.junit.jupiter.SpringExtension

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.RunnerToExtensionExample. Here's how you can define and customize such a recipe within your rewrite.yml:

rewrite.yml
---
type: specs.openrewrite.org/v1beta/recipe
name: com.yourorg.RunnerToExtensionExample
displayName: JUnit 4 `@RunWith` to JUnit Jupiter `@ExtendWith` example
recipeList:
  - org.openrewrite.java.testing.junit5.RunnerToExtension:
      runners: org.springframework.test.context.junit4.SpringRunner
      extension: org.springframework.test.context.junit.jupiter.SpringExtension

Now that com.yourorg.RunnerToExtensionExample has been defined activate it and take a dependency on org.openrewrite.recipe:rewrite-testing-frameworks:2.6.0 in your build file:

  1. Add the following to your build.gradle file:

build.gradle
plugins {
    id("org.openrewrite.rewrite") version("6.11.2")
}

rewrite {
    activeRecipe("com.yourorg.RunnerToExtensionExample")
}

repositories {
    mavenCentral()
}

dependencies {
    rewrite("org.openrewrite.recipe:rewrite-testing-frameworks:2.6.0")
}
  1. 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

Jonathan Schneider, Greg Adams, Sam Snyder, Knut Wannheden, Scott Jungling, Aaron Gershman, Tyler Van Gorder, Patrick Way, Tim te Beek, Michael Keppler, Patrick

Last updated