You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Quarkus Integration Tests the quarkus.configuration.build-time-mismatch-at-runtime defaults to warn if no test profiles are activated, but defaults to fail if test profiles are activated. If the test profile exists, having quarkus.configuration.build-time-mismatch-at-runtime = warn in neither the application properties file nor in the test profile can change the behavior to warn.
It would be helpful if this property can be set with the test profile itself or application properties file. This would simplify running integration tests in specific use cases where the setting to warn is necessary.
Example use case:
Artemis Test Resource (from quarkus-artemis) binds several properties both at build and run time. A broker.xml is needed to use the test resource and it changes the values of the build time properties. When this test resource is used, test profiles currently cannot be easily used in integrration tests, otherwise the application would fail to start.
This was not an issue in Quarkus 3.17 but seems to be a problem in Quarkus 3.18 and after (although I only tested 3.17 -> 3.22).
Implementation ideas
I think moving the properties.put("quarkus.config.build-time-mismatch-at-runtime", "fail"); line to the first line after if (profile != null) would in IntegrationTestUtil could do the job. I'm not sure if it would cause other unintended regressions - remains to be tested.
The text was updated successfully, but these errors were encountered:
Description
In Quarkus Integration Tests the
quarkus.configuration.build-time-mismatch-at-runtime
defaults to warn if no test profiles are activated, but defaults to fail if test profiles are activated. If the test profile exists, havingquarkus.configuration.build-time-mismatch-at-runtime = warn
in neither the application properties file nor in the test profile can change the behavior to warn.It would be helpful if this property can be set with the test profile itself or application properties file. This would simplify running integration tests in specific use cases where the setting to warn is necessary.
Example use case:
Artemis Test Resource (from quarkus-artemis) binds several properties both at build and run time. A broker.xml is needed to use the test resource and it changes the values of the build time properties. When this test resource is used, test profiles currently cannot be easily used in integrration tests, otherwise the application would fail to start.
This was not an issue in Quarkus 3.17 but seems to be a problem in Quarkus 3.18 and after (although I only tested 3.17 -> 3.22).
Implementation ideas
I think moving the
properties.put("quarkus.config.build-time-mismatch-at-runtime", "fail");
line to the first line afterif (profile != null)
would in IntegrationTestUtil could do the job. I'm not sure if it would cause other unintended regressions - remains to be tested.The text was updated successfully, but these errors were encountered: