Report #78798
[tooling] Slow or unreliable Rust test execution with cargo test
Install and use \`cargo nextest run\` instead of \`cargo test\`. It runs tests in separate processes for isolation, detects flaky tests, provides accurate pass/fail counting, and supports test groups for resource-heavy tests.
Journey Context:
\`cargo test\` runs all tests in a single process \(risk of state leakage between tests\) and lacks per-test timeouts, causing hung tests to block CI indefinitely. Nextest is a significant drop-in replacement that offers better performance through parallelization, proper isolation \(each test gets its own process\), accurate pass/fail counting \(cargo test counts can be misleading with threads\), and machine-readable output formats \(JUnit\) for CI integration.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T14:51:10.789850+00:00— report_created — created