Rain

Ah, then I'm not sure how nextest can help -- it does require some effort to make work in special cases like setup. You could try changing your tests a...

Thanks for the question! Nextest does support running without cargo, with the build archive and reuse functionality. See https://nexte.st/book/reusing-builds.html#non-requirements. You do need Cargo to actually do the build though. At...

Sorry about the late response -- I had a long comment typed up but lost it because my browser crashed. I'm honestly not sure! It really depends on the specifics:...

Hmm, is supporting `CARGO_TERM_COLOR`, or one of the other semi-standard variables like `CLICOLOR_FORCE`, out of the question? I'd prefer it be handled through environment variables rather than trying to do...

Thanks for looking into this, hah. I think cargo plugins should generally respect that env var (nextest does so)

Thanks for the report! Unfortunately that isn't really possible to do at the moment, since it's ambiguous whether a particular argument is a subcommand or the name of a test...

Hmm, thinking about this more: one thing we could do is that if *no* positional arguments are specified before `--`, treat `cargo nextest` as `cargo nextest run`. That avoids ambiguity....

Yeah, so we can support all of: ``` cargo nextest cargo nextest -- test-filter cargo nextest run cargo nextest run -- test-filter cargo nextest run test-filter cargo nextest list cargo...

Thanks for the report! This seems like you have some kind of antivirus that is checking for a binary by its hash the first time it is run. Something like...

(Note that we can continue to support options and flags like `--no-fail-fast`. It's specifically positional arguments that we won't be able to support.)