MicroProfile Metrics 5.1.1 TCK

The official MicroProfile Metrics 5.1.1 TCK (org.eclipse.microprofile.metrics:microprofile-metrics-api-tck:5.1.1) validates that an implementation honours the whole spec — exposition formats, scopes, types, configuration. Dirac passes it in full: 127/127 PASS (100 %), consolidated in TCK.md. The runner ships in the dirac-tck module, part of the reactor but gated behind the tck Maven profile.

Status

Metric Value

Metric	Value
Official 5.1.1 suite	✅ 127/127 PASS (100 %) — TCK.md
Milestone	M8 — complete (ROADMAP.md)
Smoke test (out of Arquillian)	✅ `DiracTckSmokeTest` operational
M9 jlink smoke	✅ `dirac-image-smoke` image built (`run-jlink-smoke.sh`)

Official 5.1.1 suite

✅ 127/127 PASS (100 %) — TCK.md

Milestone

M8 — complete (ROADMAP.md)

Smoke test (out of Arquillian)

✅ DiracTckSmokeTest operational

M9 jlink smoke

✅ dirac-image-smoke image built (run-jlink-smoke.sh)

The consolidated score lives in TCK.md; each run also regenerates a raw report in dirac-tck/target/tck-report.txt (via run-official-tck-mp-metrics-5.1.sh).

Prerequisites

The artefact org.eclipse.microprofile.metrics:microprofile-metrics-api-tck:5.1.1 is available on Maven Central. The runner first installs the required Dirac modules in the local M2, then runs the reactor on dirac-tck with the tck profile.

sdk env                                              # Java 25 + Maven 3.9.16
./mvnw -ntp install -DskipTests                      # full reactor build

Running the runner

The script run-official-tck-mp-metrics-5.1.sh at the repository root orchestrates every variant.

# Smoke test — DiracTckSmokeTest, no Arquillian
./run-official-tck-mp-metrics-5.1.sh

# Full suite — JUnit 4/Arquillian, tck-official profile
./run-official-tck-mp-metrics-5.1.sh all

# Targeted test — tck-official profile + -Dtest=
./run-official-tck-mp-metrics-5.1.sh -Dtest=CounterTest

The runner installs dirac-api, dirac-core, dirac-cdi-vauban in the local M2 (step 1), then invokes ./mvnw -Ptck,<profile> -pl dirac-tck test (step 2). The summary report lands in dirac-tck/target/tck-report.txt. Direct invocation without the script:

./mvnw -Ptck -pl dirac-tck test                  # smoke
./mvnw -Ptck,tck-official -pl dirac-tck test     # full suite

Runner architecture

dirac-tck is an in-reactor module gated behind the tck Maven profile (TCK harmonisation — Dirac is the pilot brick, mirroring the vidocq-runtime-tck-* pattern of the Vidocq runtime): a plain mvn install neither downloads nor runs anything TCK-related, and the release reactor never sees the module.

Historically dirac-tck was a standalone out-of-reactor POM: ShrinkWrap Maven Resolver 3.3, transitive to the official TCK, could not parse Model 4.1.0 POMs. That constraint disappeared with the workspace-wide migration to Maven 3.9.16 / Model 4.0.0, and the MP Metrics api-tck builds its deployments with addClass/addPackage only (no ShrinkWrap Maven resolver), so it is safe in-reactor — the same verification already backs vidocq-runtime-tck-dirac-metrics.

Stack assembled by the runner:

Layer Component

Layer	Component
Spec	`microprofile-metrics-api` 5.1.1, `jakarta.enterprise.cdi-api` 4.1, `jakarta.interceptor-api` 2.2, `jakarta.annotation-api` 3.0, `jakarta.ws.rs-api` 4.0
Metrics implementation	`dirac-api` + `dirac-core` + `dirac-cdi-vauban` + `dirac-rest`
CDI container	Vauban (`io.vidocq.vauban.core`) embedded
Arquillian container	Dirac container that deploys the archive and exposes `/metrics` via Cassini + Chappe
HTTP transport	Chappe (`io.vidocq.chappe.http`)
Test framework	JUnit 4 + Arquillian (`surefire-junit4` provider) — the MP Metrics api-tck is JUnit-based, not TestNG

Spec

microprofile-metrics-api 5.1.1, jakarta.enterprise.cdi-api 4.1, jakarta.interceptor-api 2.2, jakarta.annotation-api 3.0, jakarta.ws.rs-api 4.0

Metrics implementation

dirac-api + dirac-core + dirac-cdi-vauban + dirac-rest

CDI container

Vauban (io.vidocq.vauban.core) embedded

Arquillian container

Dirac container that deploys the archive and exposes /metrics via Cassini + Chappe

HTTP transport

Chappe (io.vidocq.chappe.http)

Test framework

JUnit 4 + Arquillian (surefire-junit4 provider) — the MP Metrics api-tck is JUnit-based, not TestNG

Arquillian configuration in dirac-tck/src/test/resources/arquillian.xml. Current smoke test: dirac-tck/src/test/java/io/vidocq/dirac/tck/DiracTckSmokeTest.java.

jlink smoke (M9)

The jlink smoke validates that the whole Dirac stack can be assembled into a Java native image without an automatic module lacking a canonical name. The blocker is lifted by dirac-mp-metrics-api, which repackages the MP Metrics spec with an explicit module-info.class (module microprofile.metrics.api { exports …; }).

./run-jlink-smoke.sh           # build + jlink + dirac-image-smoke image
./run-jlink-smoke-ci.sh        # blocking CI wrapper
./mvnw -ntp -N -Pjlink-smoke verify

Details in JLINK.md.

Quality contract

Any structural modification of dirac-core, dirac-cdi-vauban or dirac-rest must preserve the 127/127 TCK score before merge. A TCK regression is a CI-level blocker: the PR does not pass. Any excluded test (if any) must be justified in TCK.md.