Medkit test-execution results¶
Executed-test results for the medkit crates, ingested from the
cargo-nextest JUnit file that the ci-test-records workflow produces
(Execution results ingested ... (REQ_1011)). Each ingested case is a test-case need carrying its
result and time; the build joins them to the verification cases each test declares with a @need-ids: marker (Executed-test to verificati... (REQ_1013))
and emits test-execution-record.json next to this page (Build-identity-stamped reco... (REQ_1014),
Coverage-gap enumeration (REQ_1015)).
The results below are regenerated on every code-changing CI run and are not committed: a plain documentation build has no JUnit to ingest and renders a note here instead. The record itself is the validation evidence for the commit it names; this page is its human-readable companion.
Note
No executed test results were ingested in this build. The medkit test-execution results appear here when the spec is built after the cargo-nextest leg (CI test-records workflow).