JUnit 5自定义参数化测试注解失效问题求助

Got it, let's work through why your @CustomParametrizedTest annotation is being ignored. The core issue is missing critical meta-annotations that JUnit Jupiter needs to detect and process your custom annotation at runtime. Here's how to fix it:

1. Add Required Meta-Annotations #

Your custom annotation is missing two key meta-annotations that make it visible and usable for JUnit:

• @Retention(RetentionPolicy.RUNTIME): Ensures the annotation sticks around in the JVM during test execution (JUnit can't process annotations that get discarded after compilation).
• @Target(ElementType.METHOD): Explicitly tells Java this annotation should only be applied to test methods (the only place you'll use it anyway).

Also, note that @Inherited does nothing for method annotations—it only applies to class-level annotations passed down through class inheritance, so you can safely remove it.

2. Revised Custom Annotation Implementation #

Here's the corrected version of your annotation, assuming your PARAMETERIZED_TESTS_NAME_PLACEHOLDER lives in a utility class like TestUtils:

import java.lang.annotation.*;
import org.junit.jupiter.params.ParameterizedTest;

@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.METHOD)
@ParameterizedTest(name = TestUtils.PARAMETERIZED_TESTS_NAME_PLACEHOLDER)
public @interface CustomParametrizedTest { }

Make sure you import the correct utility class where your name placeholder is defined, or use the fully qualified class name (e.g., com.yourpackage.TestUtils.PARAMETERIZED_TESTS_NAME_PLACEHOLDER) if there's any ambiguity.

3. Test It Out in Your Test Cases #

Now you can use your custom annotation exactly like you would use @ParameterizedTest:

import org.junit.jupiter.params.provider.ValueSource;

class SampleTest {

    @CustomParametrizedTest
    @ValueSource(strings = {"apple", "banana"})
    void testWithCustomAnnotation(String fruit) {
        // Your test logic here
    }
}

Why Your Original Annotation Failed #

• Without @Retention(RetentionPolicy.RUNTIME), the annotation was thrown away after compilation—JUnit never even saw it during test execution.
• @Inherited was irrelevant here because it doesn't propagate method annotations from parent classes or interfaces.
• While missing @Target isn't a hard failure, it's best practice to restrict annotations to the elements they're meant for (methods, in this case).

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