How to resource lock concurrent parametrized tests?

[PranavMahesh1]

I have a class:

class ExampleTest {
    @ParameterizedTest
    @ValueSource(strings = ["a", "b", "c"])
    @Execution(value = ExecutionMode.CONCURRENT)
    fun testA(input: String) {
        println("First test with $input")
        Thread.sleep(1000)
    }
}

This will execute the parametrized tests in parallel. However, I don't want this class to run at the same time as ExampleTest2 (similar class), so I add a @ResourceLock("test") to both classes. As soon as I add the annotation to one of these classes and run the test class individually, the parametrized tests stop running in parallel. How can I execute the parameters in parallel but stop these two classes from executing at the same time?

[marcphilipp]

We're currently discussing this in #4346. Feel free to chime in there!

In your specific case, you could achieve what you need by annotating both ExampleTest and ExampleTest2 with @Execution(SAME_THREAD) instead of @ResourceLock("test"), couldn't you?

[PranavMahesh1]

Thanks, that looks like it does the trick for me. One last question, there wouldn't be a way to make ExampleTest run last, or after ExampleTest2 in terms of other test classes, unless I use a Suite?

[marcphilipp]

Have you tried configuring a ClassOrderer in junit-platform.properties?

[PranavMahesh1]

Looks like that works, thanks. I'm a bit curious on why it doesn't seem to work unless I mark @Execution(ExecutionMode.SAME_THREAD)? Or, I'm guessing, if that's left out, is it that the classes will start in the order that's defined, but it's only for the start order and doesn't have anything to do with the order it's finished, correct?

Also, random thought, let's say I have the order of ExampleTest with order 1 and ExampleTest2 with order 2, marked with execution on the same thread. Is it supported to declare two more test classes, that run in another order, but in another thread? That way, 'ExampleTest' and 'ExampleTest2' execute in the same thread and order, while 'ExampleTest3' and 'ExampleTest4' execute in order but share another thread, such that both 'groups' are running concurrently?

[marcphilipp]

Is it supported to declare two more test classes, that run in another order, but in another thread?

No, that's not supported. The basic rule of thumb is, as soon as parallel execution is enabled, ordering isn't enforced anymore.