Context
PR #962 (jh/test_coverage_20260225_master_pr) explored adding external test coverage infrastructure — coverage matrix, fetch scripts, batch runner, report tooling, and test harnesses for 5 external suites — all at once. That approach is too large for a single PR. We will add tests incrementally instead.
External test suites evaluated
| Suite |
Source |
| miri-pass |
rust-lang/miri tests/pass/ |
| miri-fail |
rust-lang/miri tests/fail/ |
| ui-run-pass |
rust-lang/rust tests/ui/ (run-pass) |
| kani |
model-checking/kani tests/kani/ |
| rustlantis |
cbeuw/rustlantis (generated programs) |
TODO
Workflow
For each test being added:
- Verify
stable-mir-json can compile the Rust file and produce valid SMIR JSON
- Add the test to
mir-semantics prove-rs / integration tests
- Keep PRs small — a handful of tests from one suite per PR
Reference
Context
PR #962 (
jh/test_coverage_20260225_master_pr) explored adding external test coverage infrastructure — coverage matrix, fetch scripts, batch runner, report tooling, and test harnesses for 5 external suites — all at once. That approach is too large for a single PR. We will add tests incrementally instead.External test suites evaluated
rust-lang/miritests/pass/rust-lang/miritests/fail/rust-lang/rusttests/ui/ (run-pass)model-checking/kanitests/kani/cbeuw/rustlantis(generated programs)TODO
stable-mir-jsonUI tests asmir-semanticstestsmiri-passtests to prove-rs suitemiri-failtests to prove-rs suiteui-run-passtests to prove-rs suitekanitests to prove-rs suiterustlantisgenerated programs for potential test coverageWorkflow
For each test being added:
stable-mir-jsoncan compile the Rust file and produce valid SMIR JSONmir-semanticsprove-rs / integration testsReference