Support for non-mock @ConfigMapping in @QuarkusComponentTest

[yrodiere]

Description

It would be nice if config mappings (@ConfigMapping-annotated interfaces) could be supported in @QuarkusComponentTest, either by default or as an opt-in feature.

Currently they seem to always be mocked, while I'd like them to be handled as they would in a normal application.

For example, if I have a component like this:

@ApplicationScoped 
public class Foo {

    @Inject
    Charlie charlie; 

    @Inject
    FooConfig config;

    @ConfigMapping(prefix = "foo")
    interface FooConfig {
        boolean bar();
    }

    public String ping() {
        return config.bar() ? charlie.ping() : "nok";
    }
}

And a test like this:

@QuarkusComponentTest 
@TestConfigProperty(key = "foo.bar", value = "true") 
public class FooTest {

    @Inject
    Foo foo; 

    @InjectMock
    Charlie charlieMock; 

    @Test
    public void testPing() {
        Mockito.when(charlieMock.ping()).thenReturn("OK"); 
        assertEquals("OK", foo.ping());
    }
}

... then the test won't pass because FooConfig is always injected as a mock, and as a result config.bar() returns false by default.

Using new QuarkusComponentTestExtension(Foo.FooConfig.class) doesn't seem to help.

Implementation ideas

Quote from @mkouba (taken out of context, as all good quotes are):

it should be doable ;-)