Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
1–10 of 53 posts
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#2Anybody using this in production?
edit: Thanks, will try!
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#3Anybody using this in production? edit: Thanks, will try!
Yes, for a long while – I believe it's fairly widely used (and it's absolutely excellent!)
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#4I somehow tried to make sense of the name as a superlative form of "next". Perhaps next-test would have been fine?
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#5Anybody using this in production? edit: Thanks, will try!
Happy user here !
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#6Thanks for posting about this! I'm the main author of nextest, and it represents my best foot forward for how Rust testing should be done. Happy to answer questions though I might be a bit intermittent.
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#7I somehow tried to make sense of the name as a superlative form of "next". Perhaps next-test would have been fine?
That is indeed the pun =)
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#8Anybody using this in production? edit: Thanks, will try!
Yes, been using it for 18’ish months. Works great.
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#9I love nextest, it's been great. This along with bacon catches a lot of issues.
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#10Thanks for posting about this! I'm the main author of nextest, and it represents my best foot forward for how Rust testing should be done. Happy to answer questions though I might be a bit intermittent.
Big fan of nextest and this is my first time seeing this site. I'll be real I feel a bit ridiculous commenting this but you might want to consider rephrasing this:
>Treat tests as cattle, not pets. Detect and terminate slow tests.
Not sure saying, "hey, treat your tests as an animal you can kill at will" paints the right image.