Ok I know it might some weird at the beginning and your quick answer will be, don't annotate test with QuarkusTest annotation, but today I have done a talk about Quarkus and one attendee raised the next use case.
Then I want to start at dev mode the quarkus application, do a change, this change is reflected to running instance and infinitest runs the the test against the new instance.
I know here there os one problem and it is what's happen if infinitest runs before quarkus update. But assuming that this can be workaround then you have the problem that Quarkus is starting a new instance so you are loosing some time booting up when you already have an instance running (dev mode one).
Of course you might say, "then do not annotate the test with the QuarkusTest" but the idea is that you run infinitest in local development and then the same tests are executed correctly in CI systems.
So the idea would be to have a configuration attribute that if it is set to true, then Quarkus test does not start the application and just assumes that it is running in localhost 8080.
WDYT?