Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

nexte.st

Post reply on HN
Print view View original

51–53 of 53 posts

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

#51

Post by sunshowers »

moi2388 wrote: post #50
landr0id wrote: post #10

Earlier 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.

Jesus Christ do we seriously need to limit our speech and get rid of perfectly good analogies for every special little snowflake?

Like all things in life, there is a balance :) I didn't remove the cattle vs pets analogy but I did replace "terminate" with "handle".

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

#52

Post by nixosbestos »

trollbridge wrote: post #12
landr0id wrote: post #10

Earlier 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.

Who here is old enough to know about PetSets, since we're talking this topic and k8s...

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

#53

Post by thejosh »

sunshowers wrote: post #6

Thanks 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.

nextest is one of those things I never have to think about, because it always "just works" and I have no dramas with it. <3
Post reply on HN