Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI

A new Rust testing tool called cargo-nextest is strutting in with a huge promise: run tests up to 3 times faster, keep each test in its own little bubble so they don’t trip over each other, and play nicely with automated build systems. In normal-person terms, it’s trying to make the boring but important job of checking code feel quicker, cleaner, and less chaotic. The catch? It still can’t handle documentation tests on stable Rust, so users have to do those separately for now.

But let’s be honest: the real action was in the comments, where the vibe was a mix of “this rules”, “that name is strange”, and “is anyone actually trusting this in real life?” One of the first reactions was the classic cautious internet side-eye: “Anybody using this in production?” That’s developer-speak for, “Looks cool, but am I brave enough to bet my job on it?” Then came the name discourse, because of course it did. One commenter admitted they tried to parse “nextest” like some kind of grammar puzzle and suggested “next-test” might have saved everyone a headache.

Meanwhile, fans showed up hard. One user said they love nextest, and another practically gave the docs a standing ovation, calling the execution model page “documentation at its best.” Even better, the main author popped into the thread with a calm, confident “happy to answer questions” energy, which instantly turned the whole thing from product pitch into community hangout. So yes, the tool is fast — but the comments proved the bigger story is that people are already arguing, praising, and memeing it like it matters