Menu
Use when choosing, adding, listing, or running Machina tests, including targeted Rust tests and workspace validation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when building Machina, running cargo check, debugging Rust build failures, or deciding which repository build command to run.
Use when finding Machina definitions, call sites, crate boundaries, device models, target code, or QEMU-inspired subsystem mappings.
Use when reviewing Machina pull requests, local diffs, commits, or mailing-list patch series that may inform Machina changes.
Use when summarizing or preparing to debug Machina GitHub issues, bug reports, feature requests, or reproduction notes.
Use when comparing Machina behavior with QEMU, using difftest/oracle tooling, or debugging CPU, interrupt, memory, or device-model parity.
| name | machina-testing |
| description | Use when choosing, adding, listing, or running Machina tests, including targeted Rust tests and workspace validation. |
| license | MIT |
All tests live in the standalone tests/ crate named machina-tests.
| Scope | Command |
|---|---|
| Full test suite | make test |
| Backend tests | make test-backend |
| Frontend tests | make test-frontend |
| Integration tests | make test-integration |
| One Rust test | cargo test -p machina-tests <filter> |
| Format check | make fmt-check |
| Lint | make clippy |
tests/src/.make fmt-check after code edits.make test before PR submission when behavior changed.#[cfg(test)] mod tests inside individual crates.