How to reuse JUnit Jupiter @MethodSource for multiple parameterized tests

Question

Let's say I have the following code:

class Testing {

    String[] text() {
        String[] text = { "A", "B" };
        return text;

    }

    @Nested
    class NestedTesting {

        @ParameterizedTest
        @MethodSource("text")
        void A(String text) {

            System.out.println(text);

        }

        @ParameterizedTest
        @MethodSource("text")
        void B(String text) {

            System.out.println(text);

        }
    }
}

When I run this, I get:

No tests found with test runner 'JUnit 5'.

How can I get this to work? I'm a beginner in Java, so I'm probably forgetting something obvious

Sam Brannen · Accepted Answer · 2019-08-23 17:12:55Z

10

The easiest way is to reference a static factory method via its fully qualified method name -- for example, @MethodSource("example.Testing#text()").

To simplify matters even further, you can introduce a custom composed annotation that combines the configuration for @ParameterizedTest and @MethodSource like this:

import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.MethodSource;

@Target(ElementType.METHOD)
@Retention(RetentionPolicy.RUNTIME)
@ParameterizedTest
@MethodSource("example.Testing#text()")
public @interface ParameterizedTextTest {
}

You can then reuse that like this:

package example;

import org.junit.jupiter.api.Nested;

class Testing {

    static String[] text() {
        return new String[] { "A", "B" };
    }

    @Nested
    class NestedTesting {

        @ParameterizedTextTest
        void testA(String text) {
            System.out.println(text);
        }

        @ParameterizedTextTest
        void testB(String text) {
            System.out.println(text);
        }
    }
}

Happy testing!

edited Aug 23, 2019 at 17:12

answered Aug 23, 2019 at 16:12

Sam Brannen

31.5k7 gold badges116 silver badges148 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

daniu Over a year ago

I think the @MethodSource would make a lot of sense with value() == methodName() and an optional className(). Would be a lot more intuitive.

Collectives™ on Stack Overflow

How to reuse JUnit Jupiter @MethodSource for multiple parameterized tests

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related