This does not allow for testing use cases in which the above mentioned property is set just at the application level.
This issue is a proposal for adding TCK tests that assume the mp.health.disable-default-procedures MP Config property is not set via a system property pr environment variable, but just at application level.
Such category of tests should be excluded from the default TCK execution, and executed optionally by vendors, within a separate TCK execution.
Description
Currently the TCK must be run with the
mp.health.disable-default-procedures
MP Config property set totrue
, see https://github.com/eclipse/microprofile-health/tree/main/tck#disabling-default-vendor-proceduresThis does not allow for testing use cases in which the above mentioned property is set just at the application level.
This issue is a proposal for adding TCK tests that assume the
mp.health.disable-default-procedures
MP Config property is not set via a system property pr environment variable, but just at application level.Such category of tests should be excluded from the default TCK execution, and executed optionally by vendors, within a separate TCK execution.
Use cases