Live data from Hacker News

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

nexte.st

11–20 of 53 posts

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

#11

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.

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.

That's fair! I'll find a way to rephrase it.

edit: Updated to "Detect and handle slow tests". Thanks again!

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

#12

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.

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

#13

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.

Yeah that was indeed the inspiration (though I'm pretty sure it predates Kubernetes!) but the juxtaposition with "terminate" is unfortunate.

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

#16

Earlier quoted context omitted.

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.

Yeah that was indeed the inspiration (though I'm pretty sure it predates Kubernetes!) but the juxtaposition with "terminate" is unfortunate.

I liked the way it was phrased. You can't make everybody happy. :)

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

#18

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.

Have there been any discussions about upstreaming this into cargo proper? Are there any significant downsides to nextest compared to its predecessor?

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

#19
post #18

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.

Have there been any discussions about upstreaming this into cargo proper? Are there any significant downsides to nextest compared to its predecessor?

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/

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

#20
post #18

Earlier quoted context omitted.

Have there been any discussions about upstreaming this into cargo proper? Are there any significant downsides to nextest compared to its predecessor?

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.
Post reply on HN