Provide marker annotation for tests to be repeated that are already meta-annotated with `@Test`

[LeggoMahEggo]

I occasionally have tests that I need to repeat a number of times. My tests are marked with an annotation that is already meta-annotated with @Test, so adding @RepeatedTest causes the tests to be run an additional time, and my IDE complains about the suspicious combination of @Test and @RepeatedTest. While this isn't a pressing issue (since I am not prevented from having my tests be run multiple times), it would be nice to take meta-annotations into account without needing to duplicate the @RepeatedTest feature set.

[kaipe]

By using LazyParams you can achieve it with this kind of hack:

import java.util.stream.IntStream;
import org.lazyparams.LazyParams;

public class Repeat {
    public static void untilCount(int endCount) {
        LazyParams.pickValue(
                count -> String.format("repetition %s of %s", count, endCount),
                IntStream.rangeClosed(1, endCount)
                        .mapToObj(Integer::valueOf)
                        .toArray());
    }
}

Then just call method untilCount from your test execution:

    @MetaMeta
    void metaAnnotatedTest() {
        Repeat.untilCount(3);
        /* ... test execution continues ... */
    }

// Test-Result on success:
//    ├─ metaAnnotatedTest() ✔
//    │  ├─ metaAnnotatedTest repetition 1 of 3 ✔
//    │  ├─ metaAnnotatedTest repetition 2 of 3 ✔
//    │  └─ metaAnnotatedTest repetition 3 of 3 ✔

[LeggoMahEggo]

By using LazyParams you can achieve it with this kind of hack:

import java.util.stream.IntStream;
import org.lazyparams.LazyParams;

public class Repeat {
public static void untilCount(int endCount) {
LazyParams.pickValue(
count -> String.format("repetition %s of %s", count, endCount),
IntStream.rangeClosed(1, endCount)
.mapToObj(Integer::valueOf)
.toArray());
}
}

Then just call method untilCount from your test execution:

@MetaMeta
void metaAnnotatedTest() {
    Repeat.untilCount(3);
    /* ... test execution continues ... */
}

// Test-Result on success:
// ├─ metaAnnotatedTest() ✔
// │ ├─ metaAnnotatedTest repetition 1 of 3 ✔
// │ ├─ metaAnnotatedTest repetition 2 of 3 ✔
// │ └─ metaAnnotatedTest repetition 3 of 3 ✔

This is quite nice, but not an ideal solution in my eyes -- it would be better to avoid using external dependencies and use native solutions instead. I can achieve the same effect as your library by writing my own implementation of @RepeatedTest and creating a new annotation that uses it, but as stated above, I would prefer to not do that.

[sbrannen]

My tests are marked with an annotation that is already meta-annotated with @Test,

Can you please explain why that is the case?

In other words, what purpose does your custom composed annotation serve?

[LeggoMahEggo]

My tests are marked with an annotation that is already meta-annotated with @Test,

Can you please explain why that is the case?

In other words, what purpose does your custom composed annotation serve?

I write tests for my company's web tools -- they have features which are applicable to desktop, mobile, and both. So I have composed annotations for each mode, which allows me to implement logic applicable to the mode being tested.