Skip to content

Make Rust-vs-Micro-Rust testing a coverage-auditable CI gate#108

Open
DominicPM wants to merge 1 commit intoawslabs:mainfrom
DominicPM:micro-rust-conformance
Open

Make Rust-vs-Micro-Rust testing a coverage-auditable CI gate#108
DominicPM wants to merge 1 commit intoawslabs:mainfrom
DominicPM:micro-rust-conformance

Conversation

@DominicPM
Copy link
Contributor

Establish a full conformance testing strategy that validates Rust behaviour against evaluated Micro Rust definitions and blocks CI on coverage regressions.

  • expand the conformance suite across core categories: arithmetic, bitwise, comparison, conversion, panic behaviour, stdlib arithmetic, option, result, range, ordering, and tuple
  • generate a single Rust harness from HOL-driven expectations rather than handwritten expected semantics
  • add/standardize panic-path testing so failure behaviour is checked, not only success paths
  • introduce unified generation orchestration and required-category checks
  • add coverage reporting infrastructure with machine-readable JSON and human-readable Markdown summaries
  • wire conformance coverage verification into CI so missing ownership/coverage fails the pipeline
  • update framework/session wiring and docs to reflect the conformance strategy and audit process

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@dominic-mulligan-aws dominic-mulligan-aws self-assigned this Feb 18, 2026
@dominic-mulligan-aws dominic-mulligan-aws added enhancement New feature or request CI labels Feb 18, 2026
@DominicPM DominicPM force-pushed the micro-rust-conformance branch from 56577d9 to b406607 Compare February 18, 2026 19:15
@DominicPM DominicPM force-pushed the micro-rust-conformance branch from d80c007 to 0027806 Compare February 18, 2026 21:33
@dominic-mulligan-aws dominic-mulligan-aws force-pushed the micro-rust-conformance branch 3 times, most recently from f013b6a to f665477 Compare February 19, 2026 08:29
Establish a full conformance testing strategy that validates Rust behaviour
against evaluated Micro Rust definitions and blocks CI on coverage regressions.

- expand the conformance suite across core categories:
  arithmetic, bitwise, comparison, conversion, panic behaviour,
  stdlib arithmetic, option, result, range, ordering, and tuple
- generate a single Rust harness from HOL-driven expectations rather than
  handwritten expected semantics
- add/standardize panic-path testing so failure behaviour is checked, not
  only success paths
- introduce unified generation orchestration and required-category checks
- add coverage reporting infrastructure with machine-readable JSON and
  human-readable Markdown summaries
- wire conformance coverage verification into CI so missing ownership/coverage
  fails the pipeline
- update framework/session wiring and docs to reflect the conformance strategy
  and audit process

Signed-off-by: Dominic Mulligan <dominic.p.mulligan@gmail.com>
@DominicPM DominicPM force-pushed the micro-rust-conformance branch from f665477 to 53aa5e2 Compare February 19, 2026 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants