Skip to content

Latest commit

 

History

History
39 lines (30 loc) · 3.72 KB

File metadata and controls

39 lines (30 loc) · 3.72 KB

Recipe & CLI Coverage Matrix

This page is generated by make coverage-docs (tools/coverage) and refreshed weekly by the coverage-matrix-refresh workflow. Do not edit by hand.

It is a structural matrix: it reports which CUJs and CLI verbs are exercised by an in-repo test or demo, on what hardware class, and at what cadence. It does not report live pass/fail — that posture is a link into the AICR TestGrid (which carries aicr_version as a column facet), never embedded here.

This is a different axis from the per-recipe Coverage column in the recipe-health matrix (ADR-009 declared_coverage): that column counts declared named checks per validation phase for a single recipe, whereas this matrix answers "which journeys and CLI verbs are exercised, where, and how often." The recipe-health page cross-links the other way through its presence-gated Evidence column (RQ1, #1283): a recipe with a published dashboard coordinate deep-links to it, and shows pending only when none exists. See also the CLI reference.

AICR-version axis. The nightly UAT batch runs every enrolled reservation against tip-of-main, built from source, plus the previous stable release, installed from its release artifacts. Each version is a full provision, CUJ and teardown cell per intent. The rows below are version-independent: per-version pass/fail posture is a TestGrid link, not a cell here.

Legend. covered = exercised by an executable journey signal — a chainsaw/KWOK test or a wired nightly UAT runner; not-yet-covered = a shipping capability no such journey touches yet; stubbed = UAT assets exist but nothing scheduled executes the journey, for the reason the row's note gives. This tracks CUJ/CLI journey coverage — per-package Go unit-test coverage is a separate gate (make test-coverage), not reflected here.

Critical user journeys (CUJs)

Item Exercised by Hardware Cadence Status Notes
cuj1-training-kubeflow chainsaw, uat, demo GPU (H100, real) nightly covered
cuj2-inference-dynamo demo GPU (unwired) stubbed the intent runs nightly and its stack is deployed and validated, but the journey's own workload step is disabled in the per-cloud UAT pipelines

CLI verbs

Item Exercised by Hardware Cadence Status Notes
bundle chainsaw, uat, demo GPU (H100, real) nightly covered
diff not-yet-covered
evidence digest not-yet-covered
evidence publish demo docs not-yet-covered documented in demos only; no executable test yet
evidence sign not-yet-covered
evidence verify uat, demo GPU (H100, real) nightly covered
mirror list not-yet-covered
query demo docs not-yet-covered documented in demos only; no executable test yet
recipe chainsaw, uat, demo GPU (H100, real) nightly covered
recipe list not-yet-covered
recipe verify-catalog not-yet-covered
skill demo docs not-yet-covered documented in demos only; no executable test yet
snapshot chainsaw, uat, demo GPU (H100, real) nightly covered
trust update chainsaw, uat, demo GPU (H100, real) nightly covered
validate chainsaw, uat, demo GPU (H100, real) nightly covered
verify chainsaw, demo simulated / none per-PR covered