Parts of the TCK will be implementation-specific. For example, if an implementation is based on Micrometer then the prometheus output format should strictly match the output expected from known micrometer implementations.
This issue is to add the ability to auto-detect which implementation is present and automatically run the appropriate TCK tests for that implementation. At minimum we should be able to detect Micrometer and Open Telemetry Metrics implementations.
This issue should also add a property that we can use when running the TCK to override the auto-detection in case that auto-detection is getting the wrong answer. For example, it could be mvn test -Dmp.metrics.impl=micrometer-1.8 to specify that micrometer v1.8.x is the implementation.
Parts of the TCK will be implementation-specific. For example, if an implementation is based on Micrometer then the prometheus output format should strictly match the output expected from known micrometer implementations.
This issue is to add the ability to auto-detect which implementation is present and automatically run the appropriate TCK tests for that implementation. At minimum we should be able to detect Micrometer and Open Telemetry Metrics implementations.
This issue should also add a property that we can use when running the TCK to override the auto-detection in case that auto-detection is getting the wrong answer. For example, it could be
mvn test -Dmp.metrics.impl=micrometer-1.8to specify that micrometer v1.8.x is the implementation.