NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI (nexte.st)
sunshowers 2 hours ago [-]
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.
mrec 19 minutes ago [-]
Have there been any discussions about upstreaming this into cargo proper? Are there any significant downsides to nextest compared to its predecessor?
sunshowers 17 minutes ago [-]
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/

mrec 15 minutes ago [-]
Ah, I see. You're aiming to become the hashbrown of testing.
sunshowers 10 minutes ago [-]
Oh gosh, were we to be so lucky :) just aiming to solve problems my coworkers and users see, and doing it with care, is all.
landr0id 2 hours ago [-]
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.

trollbridge 2 hours ago [-]
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.
sunshowers 2 hours ago [-]
Yeah that was indeed the inspiration (though I'm pretty sure it predates Kubernetes!) but the juxtaposition with "terminate" is unfortunate.
wojciii 54 minutes ago [-]
I liked the way it was phrased. You can't make everybody happy. :)
sunshowers 2 hours ago [-]
That's fair! I'll find a way to rephrase it.

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

weinzierl 52 minutes ago [-]
The "execution model" page[1] is documentation at its best!

It answered 90% of the questions I had at the monent. Thank you!

[1] https://nexte.st/docs/design/how-it-works/

satvikpendem 2 hours ago [-]
I love nextest, it's been great. This along with bacon catches a lot of issues.
patates 3 hours ago [-]
I somehow tried to make sense of the name as a superlative form of "next". Perhaps next-test would have been fine?
sunshowers 2 hours ago [-]
That is indeed the pun =)
patates 56 minutes ago [-]
Oh, sorry then, thanks for the clarification :)
esafak 4 hours ago [-]
Anybody using this in production?

edit: Thanks, will try!

tekacs 3 hours ago [-]
Yes, for a long while – I believe it's fairly widely used (and it's absolutely excellent!)
aabhay 60 minutes ago [-]
Yep. Tokio uses it for their tests in CI as well last I checked.
DennisL123 2 hours ago [-]
Yes, been using it for 18’ish months. Works great.
merqurio 3 hours ago [-]
Happy user here !
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 08:07:26 GMT+0000 (Coordinated Universal Time) with Vercel.