如何使用Gradle和JUnit 5运行指定测试？JUnit 5插件是否支持？

Absolutely! The Gradle integration for JUnit 5 does support running specific tests—you just might be missing the right syntax or configuration tweaks that differ a bit from JUnit 4. Let’s break down the correct approaches:

1. Command-Line Filtering with --tests (Works for Both test and junitPlatformTest) #

The --tests flag is fully supported for JUnit 5 tests, but you need to make sure your pattern matches correctly. Here are common use cases:

• Run a single test class:

  ./gradlew test --tests "com.yourpackage.YourTestClass"
  

• Run a specific test method within a class:

  ./gradlew test --tests "com.yourpackage.YourTestClass.yourTestMethod"
  

• Use wildcards to match multiple tests:

  # Match all test classes ending with "Test" in a package
  ./gradlew test --tests "com.yourpackage.*Test"
  # Match any test method containing "login" in its name
  ./gradlew test --tests "*login*"
  

If you’re still using the legacy junitPlatformTest task (instead of the built-in test task with JUnit 5 support), the same --tests syntax applies—just replace test with junitPlatformTest.

2. Permanent Filtering in Build Script #

If you want to persist test filters instead of passing them via the command line, you can configure them directly in your build script:

For Groovy DSL (build.gradle):

test {
    // Enable JUnit 5 support (required for Gradle 4.6+)
    useJUnitPlatform()
    filter {
        // Include a specific test class
        includeTestsMatching "com.yourpackage.YourTestClass"
        // Include all methods with names containing "validate"
        includeTestsMatching "*validate*"
    }
}

For Kotlin DSL (build.gradle.kts):

tasks.test {
    useJUnitPlatform()
    filter {
        includeTestsMatching("com.yourpackage.YourTestClass")
        includeTestsMatching("*validate*")
    }
}

3. Troubleshooting "Silent Ignoring" Issues #

If your --tests flag seems to be ignored, check these common pitfalls:

• Wrong Test Annotation: Ensure your tests use JUnit 5’s @Test from org.junit.jupiter.api.Test, not JUnit 4’s org.junit.Test.
• Incorrect Pattern: Double-check the package path, class name, and method name—capitalization and typos are easy to miss.
• Gradle Version: Make sure you’re using Gradle 4.6 or newer (Gradle 7+ is recommended for better JUnit 5 compatibility). Older versions may have limited support for JUnit 5 filtering.
• Missing useJUnitPlatform(): If you’re using the standard test task, you must add useJUnitPlatform() to your build script to enable JUnit 5 execution—otherwise, Gradle will default to JUnit 4 and skip your JUnit 5 tests entirely.

内容的提问来源于stack exchange，提问作者Michael Piefel