Run unit tests by overriding single config properties

[sNiXx]

I was reading a lot about unit testing in Quarkus and am now wondering if it is possible to run unit tests by overriding single properties only (and not whole configurations, as in the case of QuarkusTestProfile).

While looking at another topic I saw this: https://github.com/stuartwdouglas/quarkus/blob/c5bd959845cb4096abb7239e1cea3f749e68bb52/extensions/vertx-http/deployment/src/test/java/io/quarkus/vertx/http/security/MtlsRequestBasicAuthTest.java#L36 and was wondering if something like this would be possible in my case as well? However, I could not find much about QuarkusUnitTest in the documentation (it explicitly states "not intended for end user consumption" in the source)

What I would like to achieve is something like this, where each method checks a different license file:

@QuarkusTest
class LicenseManagerTest {

    @Inject
    LicenseManager licenseManager;

    @Test
    void testCheckLicensedModuleWithOneModule() {
        assertDoesNotThrow(() -> licenseManager.checkLicensedModule("Module1"));
        assertThrows(LicenseException.class, () -> licenseManager.checkLicensedModule("Module2"));
        assertThrows(LicenseException.class, () -> licenseManager.checkLicensedModule("Module3"));
    }

    @Test
    void testCheckLicensedModuleWithAllModules() {
        assertDoesNotThrow(() -> licenseManager.checkLicensedModule("Module1"));
        assertDoesNotThrow(() -> licenseManager.checkLicensedModule("Module2"));
        assertDoesNotThrow(() -> licenseManager.checkLicensedModule("Module3"));
    }

}

Thanks in advance :-)

[quarkus-bot[bot]]

/cc @radcortez (config)

[radcortez]

QuarkusTestProfile also works by overriding the supplied configuration (there is no need to provide the full configuration).

Yes, QuarkusUnitTest is for internal Quarkus tests and is not intended for application testing.

You can also check some other strategies here:
https://quarkus.io/blog/overriding-configuration-from-test-code/

[sNiXx]

Thank you, @radcortez, that is quite an interesting blog post :-)