Rain
Thanks for the request! Some thoughts about this: **Group scope.** So there's three potential choices of group units: 1. Individual tests. 2. Individual test binaries. 3. Workspace packages (aka crates)....
Hi @arxanas -- thanks for expressing your interest! The `[env]` field is part of `.cargo/config.toml` -- nextest already parses these files to emulate Cargo somewhat, so it's a matter of...
Like the other cargo configs, the env should be set for every test in a test run, so it's a property of the entire run. (For example, see how the...
I've left a few comments there, thanks!
I think we should provide a hint for this -- this seems to be a common issue. Reopening for that.
Down that way lies a lot of pain, e.g. what happens if you want to filter based on tests called "run" or "list". In general nextest tends to prefer teaching...
Thanks for reporting this! I think the easiest thing to do would be to make criterion support the --format terse option and output lines in the format nextest accepts: https://nexte.st/book/custom-test-harnesses.html...
There's also https://github.com/nextest-rs/nextest/issues/38 which might be useful.
I think we can support this with a `--run-benches` option, similar to `--run-ignored` today.
I looked at this a bit more and it seems like criterion binaries built with cargo test don't appear to behave with `--list`: ``` /home/rain/dev/cargo-guppy/target/debug/deps/package_graph-4455225dc7640272 --list WARNING: HTML report generation...