QuarkusTestResources all started no matter what

Describe the bug I have 2 quarkus test and 2 seperate test resources (1 for starting a MySQL container and another for starting a LocalStack container). Each of the test classes are annotated with @QuarkusTestResource for there resource.

Expected behavior Since each test class is independent and has different resources I would expect to only see the resource assigned to that class to start

Actual behavior No matter which test I seem to run both QuarkusTestResourceLifecycleManager seems to start up

To Reproduce Steps to reproduce the behavior: 1. 2. 3.

Configuration

# Add your application.properties here, if applicable.

Screenshots (If applicable, add screenshots to help explain your problem.)

Environment (please complete the following information):

• Output of uname -a or ver:
• Output of java -version:
• GraalVM version (if different from Java):
• Quarkus version or git rev:
• Build tool (ie. output of mvnw --version or gradlew --version):

Additional context (Add any other context about the problem here.)

[famod]

Btw, back in 2017 there was an attempt to add custom sorting strategies to surefire: https://github.com/apache/maven-surefire/pull/169

[geoand]

It already works, take a look at the examples in the codebase.

What isn’t there is integration with QuarkusTestResourceLifecycleManager (which I doubt I’ll have time to get in for 1.6, but you never know)