What I do
- •Standardize Rust test execution around
cargo nextest run. - •Provide a deterministic fallback to
cargo testwhennextestis unavailable or fails due to environment/tooling constraints.
When to use me
Use this when:
- •A task needs Rust tests run for
tinyverse_clior other Rust crates in this repo. - •An agent would otherwise choose
cargo testby default.
Preferred workflow
- •Run
cargo nextest run(optionally with-p <crate>). - •If command is not found, unsupported, or fails due to environment/tooling setup, run
cargo testwith the same scope. - •Report which path was used and why fallback happened when applicable.
Common commands
- •Workspace:
cargo nextest run - •Crate scoped:
cargo nextest run -p tinyverse_cli - •Fallback crate scoped:
cargo test -p tinyverse_cli
Notes
- •Keep fallback behavior explicit in status updates.
- •Do not treat regular test failures as a reason to silently switch tools without mentioning the fallback.