Skip to content

How to write independent test suites with nextest #1789

Answered by sunshowers
Nugine asked this question in Q&A
Discussion options

You must be logged in to vote

Thanks for the great question! This is honestly not a use case I'd thought about before.

I think the use case makes sense but I'm worried it's a lot of work. Currently, cargo-nextest (including nextest-runner) is really tied to Cargo and rustc. It uses Cargo to discover binaries, to figure out what environment variables to set, and for a number of other things.

This is not inherent to nextest's model: you could certainly imagine the runner working against a more abstract test discovery and running interface. I think doing so is probably going to make nextest's code better as well, and also expose a bunch of hidden dependencies to Cargo. But in order to achieve this you'd probably need to …

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@Nugine
Comment options

Answer selected by Nugine
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants