nextest-targeted-testing
Use this to run the Rust suite quickly with `cargo nextest`, starting targeted and widening to full CI parity.
When & Why to Use This Skill
This Claude skill optimizes the Rust development workflow by leveraging `cargo nextest` for high-performance, targeted testing. It enables developers to minimize feedback loops by focusing on specific test subsets before expanding to full CI-parity validation, ensuring robust code quality and efficient debugging.
Use Cases
- Rapid Debugging: Quickly isolate and run a single failing test using substring filters to verify fixes in real-time without executing the entire suite.
- CI Parity Checks: Execute the Rust test suite using CI-specific profiles locally to ensure code behavior matches the remote continuous integration environment.
- Advanced Test Inspection: Utilize specialized flags like `--nocapture` and exact test listing to gain deeper insights into complex test failures and output.
- Incremental Regression Testing: Systematically widen testing scope from targeted units to full smoke and UI suites to ensure overall system stability after a fix.
| name | nextest-targeted-testing |
|---|---|
| description | Use this to run the Rust suite quickly with `cargo nextest`, starting targeted and widening to full CI parity. |
Fast loop
- Rust-only (CI-like profile):
npm run test:rust
Target a subset
NPM passes args through after --:
Filter by substring (common case):
npm run test:rust -- <substring>
If you need exact names, list tests:
cargo nextest list --cargo-profile ci
If you need test binary args (e.g.,
--nocapture):cargo nextest run --cargo-profile ci <filter> -- --nocapture
Strategy
- Start as narrow as possible (one failing test), then widen.
- After fixing the immediate issue, run the full suite:
npm test(Rust + UI)npm run smoke
Policy
- Do NOT use
cargo testin this repo.