Facing an issue with mapping configuration

[soheil1987]

In building my quarkus application I am facing the following exceptions.

Caused by: java.util.NoSuchElementException: SRCFG00028: Could not find a mapping for io.quarkus.deployment.dev.testing.TestConfig with prefix at io.smallrye.config.SmallRyeConfig.getConfigMapping(SmallRyeConfig.java:636) at io.smallrye.config.SmallRyeConfig.getConfigMapping(SmallRyeConfig.java:621) at io.quarkus.test.junit.AbstractJvmQuarkusTestExtension.evaluateExecutionCondition(AbstractJvmQuarkusTestExtension.java:287)

I have defined two Converters as following

@Priority(100) public class TestConfigProfileConverter implements Converter<TestConfig.Container> {

@Inject
@ConfigMapping(prefix = "quarkus.test")
ConfigMapInterface configMapInterface;

@Override
public TestConfig.Container convert(String s) throws IllegalArgumentException, NullPointerException {
    return new TestConfig.Container();
}
}

and

@Priority(100) public class TestConfigContainerConverter implements Converter<TestConfig.Profile> { @Inject @ConfigMapping(prefix = "quarkus.test") ConfigMapInterface configMapInterface;

@Override
public TestConfig.Profile convert(String s) throws IllegalArgumentException, NullPointerException {
    return new TestConfig.Profile();
}
}

I also have my application.properties defined in resources directory with all required quarkus.test configuration fields. What am i missing here?

[quarkus-bot]

/cc @radcortez (config)

[soheil1987]

to debug the issue I put a breakpoint in line 677 of https://github.com/smallrye/smallrye-config/blob/main/implementation/src/main/java/io/smallrye/config/SmallRyeConfig.java which hits getConfigMapping method. what i observed is the parameter prefix is passed as an empty string to this method. while the expectation is "quarkus.test". how can i make sure this parameter is populated with correct value?

[radcortez]

Converters are not CDI Beans, so they do not support @Inject. Also, Converters are a sub-component of the configuration (as are mapping), and we don't support accessing mappings in a Converter because it can lead to circular dependencies.

A Converter usually works on a single configuration value, so accessing mappings for it is unnecessary.

Could you tell me what you are trying to accomplish? It seems you are trying to access Quarkus TestConfig. In a testing context, that should already be available to you by calling ConfigProvider.getConfig().unwrap(SmallRyeConfig.class).getMapping(TestConfig.class).

[soheil1987]

We have a quarkus application for which github detected a couple of vulnerabilities and we had to upgrade certain libs including quarkus-core. we upgraded it to 3.2.12.Final. that triggered upgrades on a couple of other libs such as io.smallrye.config. now the build complains about two specific things.

a) lack of certain properties all starting with quarkus.test. this can be fixed by adding them to application.properties file.
b) No Converter registered for class io.quarkus.deployment.dev.testing.TestConfig$Profile and No Converter registered for class io.quarkus.deployment.dev.testing.TestConfig$Container.
This is where I registered them in META-INF/services/org.eclipse.microprofile.config.spi.Converter but exception changed to
Could not find a mapping for io.quarkus.deployment.dev.testing.TestConfig with prefix

[radcortez]

Usually a Quarkus version only works with specific SmallRye Config versions (same with other libraries used by Quarkus). Updating libraries used by Quarkus to other versions other than the ones set by Quarkus itself have unpredictable results and it is not a supported use case.

Quarkus takes vulnerabilities very seriously and these are usually fixed in each Quarkus release. Can you let me know which vulnerabilities did you discover? Also, did you try to update to the latest Quarkus version (3.19.x)?

[soheil1987]

yes I did. upgraded quarkus core to 3.19.0 along with using io.smallrye.config:smallrye-config-core:3.11.2 but still getting the error SRCFG00028: Could not find a mapping for io.quarkus.deployment.dev.testing.TestConfig with prefix . i bet something is off with small rye config.

[radcortez]

Can you please provide us with a reproducer so we can look into the issue?

[fabricepipart1a]

Hi !

On my side I can provide an easy reproducer. Indeed I faced the same issue. Or at least I suppose that's the same one since I receive the same error message.
My use case is any QuarkusMainTest for a command line application. Tests run fine in IDE, run fine in Maven. But fail in dev mode.

To reproduce take quarkus-quickstarts/getting-started-command-mode
And add a test:

package org.acme.getting.started.commandmode;

import org.junit.jupiter.api.Assertions;
import org.junit.jupiter.api.Test;

import io.quarkus.test.junit.main.Launch;
import io.quarkus.test.junit.main.LaunchResult;
import io.quarkus.test.junit.main.QuarkusMainTest;

@QuarkusMainTest
public class GreetingMainTest {

    @Test
    @Launch(value = {}, exitCode = 0)
    public void testLaunchCommand(LaunchResult result) {
        Assertions.assertNotNull(String.valueOf(result.getOutput()));
    }
}

Then when you do mvn test it works fine.
But if you do quarkus test you get an error

2025-08-29 10:52:18,314 ERROR [io.qua.test] (Test runner thread) >>>>>>>>>>>>>>>>>>>> Summary: <<<<<<<<<<<<<<<<<<<<
GreetingMainTest Failed to evaluate condition [io.quarkus.test.junit.QuarkusMainTestExtension]: Internal error: Test class was loaded with an unexpected classloader or the thread context classloader was incorrect.
testLaunchCommand(LaunchResult) Failed to evaluate condition [io.quarkus.test.junit.QuarkusMainTestExtension]: Internal error: Test class was loaded with an unexpected classloader or the thread context classloader was incorrect.

2025-08-29 10:52:18,314 ERROR [io.qua.test] (Test runner thread) >>>>>>>>>>>>>>>>>>>> 1 TEST FAILED <<<<<<<<<<<<<<<<<<<<