enclosedtonested.md

JUnit 4 @RunWith(Enclosed.class) to JUnit Jupiter @Nested

org.openrewrite.java.testing.junit5.EnclosedToNested

Removes the Enclosed specification from a class, and adds Nested to its inner classes.

Source

GitHub, Issue Tracker, Maven Central

• groupId: org.openrewrite.recipe
• artifactId: rewrite-testing-frameworks
• version: 2.0.2

Example

{% tabs %} {% tab title="RootTest.java" %}

Before

{% code title="RootTest.java" %}

import org.junit.Test;
import org.junit.experimental.runners.Enclosed;
import org.junit.runner.RunWith;

@RunWith(Enclosed.class)
public class RootTest {
    public static class InnerTest {
        @Test
        public void test() {}
    }
}

{% endcode %}

After

{% code title="RootTest.java" %}

 import org.junit.Test;
 import org.junit.jupiter.api.Nested;

 
 
 public class RootTest {
     @Nested
     public class InnerTest {
         @Test
         public void test() {}
     }
 }

{% endcode %}

{% endtab %} {% tab title="Diff" %} {% code %}

--- RootTest.java
+++ RootTest.java
@@ -1,3 +1,2 @@
-import org.junit.Test;
-import org.junit.experimental.runners.Enclosed;
-import org.junit.runner.RunWith;
+import org.junit.Test;
+import org.junit.jupiter.api.Nested;

@@ -5,7 +4,9 @@
import org.junit.runner.RunWith;

-@RunWith(Enclosed.class)
-public class RootTest {
-   public static class InnerTest {
-       @Test
-       public void test() {}
-   }
-}
+
+
+public class RootTest {
+    @Nested
+    public class InnerTest {
+        @Test
+        public void test() {}
+    }
+}

{% endcode %} {% endtab %} {% endtabs %}

Usage

This recipe has no required configuration options. It can be activated by adding a dependency on org.openrewrite.recipe:rewrite-testing-frameworks:2.0.2 in your build file or by running a shell command (in which case no build changes are needed): {% tabs %} {% tab title="Gradle" %} {% code title="build.gradle" %}

plugins {
    id("org.openrewrite.rewrite") version("6.1.4")
}

rewrite {
    activeRecipe("org.openrewrite.java.testing.junit5.EnclosedToNested")
}

repositories {
    mavenCentral()
}

dependencies {
    rewrite("org.openrewrite.recipe:rewrite-testing-frameworks:2.0.2")
}

{% endcode %} {% endtab %} {% tab title="Maven POM" %} {% code title="pom.xml" %}

<project>
  <build>
    <plugins>
      <plugin>
        <groupId>org.openrewrite.maven</groupId>
        <artifactId>rewrite-maven-plugin</artifactId>
        <version>5.2.4</version>
        <configuration>
          <activeRecipes>
            <recipe>org.openrewrite.java.testing.junit5.EnclosedToNested</recipe>
          </activeRecipes>
        </configuration>
        <dependencies>
          <dependency>
            <groupId>org.openrewrite.recipe</groupId>
            <artifactId>rewrite-testing-frameworks</artifactId>
            <version>2.0.2</version>
          </dependency>
        </dependencies>
      </plugin>
    </plugins>
  </build>
</project>

{% endcode %} {% endtab %}

{% tab title="Maven Command Line" %} {% code title="shell" %} You will need to have Maven installed on your machine before you can run the following command.

mvn -U org.openrewrite.maven:rewrite-maven-plugin:run \
  -Drewrite.recipeArtifactCoordinates=org.openrewrite.recipe:rewrite-testing-frameworks:RELEASE \
  -Drewrite.activeRecipes=org.openrewrite.java.testing.junit5.EnclosedToNested

{% endcode %} {% endtab %} {% endtabs %}

Contributors

• Nick McKinney
• Knut Wannheden
• Sam Snyder
• Jonathan Schnéider
• Kyle Scully

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.