Classloader issue running test with QuarkusMainLauncher

[ebullient]

This is another issue w/ classloaders and tests, specifically when running QuarkusMain tests in VSCode (which still show up as if they are running in Eclipse):

%TSTTREE2,dev.ebullient.convert.Tools5eDataConvertTest,true,1,false,1,Tools5eDataConvertTest,,[engine:junit-jupiter]/[class:dev.ebullient.convert.Tools5eDataConvertTest]
%TSTTREE3,testLiveData_homebrew(dev.ebullient.convert.Tools5eDataConvertTest),false,1,false,2,testLiveData_homebrew(QuarkusMainLauncher),io.quarkus.test.junit.main.QuarkusMainLauncher,[engine:junit-jupiter]/[class:dev.ebullient.convert.Tools5eDataConvertTest]/[method:testLiveData_homebrew(io.quarkus.test.junit.main.QuarkusMainLauncher)]
%ERROR  2,dev.ebullient.convert.Tools5eDataConvertTest
%TRACES 
org.junit.jupiter.engine.execution.ConditionEvaluationException: Failed to evaluate condition [io.quarkus.test.junit.QuarkusMainTestExtension]: Could not execute test class because it was loaded with the wrong classloader by the Eclipse test runner. Try running test methods individually, or edit the run configuration and add `-uniqueId [engine:junit-jupiter]/[class:dev.ebullient.convert.Tools5eDataConvertTest]` in the program arguments. 
        at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
        at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
        at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
        at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
        at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
        at java.base/java.util.ArrayList$ArrayListSpliterator.tryAdvance(ArrayList.java:1602)
        at java.base/java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:129)
        at java.base/java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:527)
        at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:513)
        at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
        at java.base/java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:150)
        at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
        at java.base/java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:647)
        at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: java.lang.IllegalStateException: Could not execute test class because it was loaded with the wrong classloader by the Eclipse test runner. Try running test methods individually, or edit the run configuration and add `-uniqueId [engine:junit-jupiter]/[class:dev.ebullient.convert.Tools5eDataConvertTest]` in the program arguments. 
        at io.quarkus.test.junit.AbstractJvmQuarkusTestExtension.evaluateExecutionCondition(AbstractJvmQuarkusTestExtension.java:201)
        at io.quarkus.test.junit.QuarkusMainTestExtension.evaluateExecutionCondition(QuarkusMainTestExtension.java:400)
        ... 14 more
Caused by: java.util.NoSuchElementException: SRCFG00027: Could not find a mapping for io.quarkus.deployment.dev.testing.TestConfig
        at io.smallrye.config.SmallRyeConfig.getConfigMapping(SmallRyeConfig.java:647)
        at io.smallrye.config.SmallRyeConfig.getConfigMapping(SmallRyeConfig.java:637)
        at io.quarkus.test.junit.AbstractJvmQuarkusTestExtension.evaluateExecutionCondition(AbstractJvmQuarkusTestExtension.java:161)
        ... 15 more

attn: @holly-cummins

[geoand]

@holly-cummins Is this the same as the issues you've already dealt with?

[ebullient]

Not quite. Holly asked me to open this one

[holly-cummins]

@holly-cummins Is this the same as the issues you've already dealt with?

Yes and no. "Yes," as in "I already fixed this in #48014!", and no as in "... but it's not fixed!". It might be the same as #48537 but I'm not sure.

The "does not detect VS Code" was supposed to be fixed by #48277 but that I think that went into 3.23.3 and the reproducer is using 3.24.

[holly-cummins]

Ah, apparently the VS Code detection depends on the version of VS Code. With @ebullient's reproducer, even without changing the Quarkus version, I get

Jun 30, 2025 6:49:45 PM io.quarkus.logging.Log error
ERROR: Could not read configuration while evaluating whether to run a test. It looks like you're probably running tests with VS Code. This is a known issue when running tests in the VS Code IDE. To work around the problem, run individual test methods.

[holly-cummins]

I've just had a play with a reproducer @ebullient pointed me to, and I can reproduce with 3.23.x, but with 3.24, the tests run cleanly. So I think this is a duplicate of #48295, and we can close it.

[ebullient]

I'll update all the things.