Rain
It would be really nice to have a way for us to sign nextest's binary releases to ensure they're authentic.
Easiest to do this with a per-test override (as long as we restrict the language to non-test predicates).
**Help wanted!** It would be wonderful if someone picked this up and drove it to completion. See https://github.com/clap-rs/clap/issues/3869 for the blocker I ran into.
Followup from #319. Looks like `cargo test` sets these env vars at runtime so nextest should as well.
Antivirus and Gatekeeper checks can cause performance issues with nextest on Windows and macOS, respectively. I've [added a note about them](https://nexte.st/book/antivirus-gatekeeper) to the nextest site, but I'm going to leave...
Add support to run a single test multiple times in parallel. This is a somewhat different mode of operation from nextest as usual (the runner should be fed the same...
Currently, nextest doesn't support Rust doctests. This is because doctests are not exposed in stable Rust the way regular test binaries are, and are instead treated as special by `cargo...
Add filtering for packages (`-p` can be overloaded to mean this). This would accept the `package`, `deps` and `rdeps` functions, but not `test`. The point of this would be to...
We could try to parse the output as the format used by cargo test, and just fall back to printing out the whole test output if it fails to parse.
This needs to be done with a little care: * The initial, simpler use requires keeping track of which Cargo arguments the build was run with -- this is relatively...