Earlier quoted context omitted.
The How it works [1] and Why process-per-test? [2] pages should answer your questions. [1] https://nexte.st/docs/design/how-it-works/ [2] https://nexte.st/docs/design/why-process-per-test/
Ah, I see. You're aiming to become the hashbrown of testing.
Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
21–30 of 53 posts
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#22Anybody using this in production? edit: Thanks, will try!
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#23https://github.com/tsz-org/tsz/actions/runs/29002057457/job/...
watch it running 32.5k unit tests without breaking a sweat!
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#24Thanks 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
#25Anybody using this in production? edit: Thanks, will try!
Large projects build with rama use it as well. But those are proprietary from partners so sadly cannot share those.
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#26I love nextest. without it my CI could take hours https://github.com/tsz-org/tsz/actions/runs/29002057457/job/... watch it running 32.5k unit tests without breaking a sweat!
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#27Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#28I love nextest. without it my CI could take hours https://github.com/tsz-org/tsz/actions/runs/29002057457/job/... watch it running 32.5k unit tests without breaking a sweat!
Thanks! BTW you might enjoy setting CARGO_TERM_COLOR=always in your environment :) dtolnay/rust-toolchain does this automatically but it looks like you aren't using that action.
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#29Earlier quoted context omitted.
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.
This is from the Kubernetes saying of "treat servers like cattle, not pets". Of course, some people like me keep cattle as pets, but then again I also name my servers, even the virtual or containerised ones.
Re: Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI
#30I somehow tried to make sense of the name as a superlative form of "next". Perhaps next-test would have been fine?