Rain
Yes, that looks right. So it seems like it should be easy to do, we just need to figure out the configuration UI surface for this.
Ah yes, didn't realize the install-action had picked it up already. Taiki needs to update it on his end: https://github.com/taiki-e/install-action/issues/178
You can check in an empty `.config/nextest.toml` as a temporary workaround.
Thanks for the kind words! You should be able to set a per-test override with the `success-output = "immediate"` parameter: https://nexte.st/book/per-test-overrides.html
Ah, we currently don't have a way to say "show stdout but not stderr" or vice versa. As a workaround you can write logs to a file and just print...
I think in CI (though not in local runs), it is ~always a bug to run 0 tests. We should: * always produce a warning if no tests are run...
> Is there a standard way to tell cargo-nextest that it's running in the CI? I wasn't aware of it. Yes, we already use [`is_ci`](https://crates.io/crates/is_ci) for this purpose. > It...
Thanks for the suggestion! It's definitely thought-provoking -- it's kind of like a meta-level test that you're running the right set of tests. Are there prior implementations of this anywhere?
Hi there -- Thanks for the feature request! This is currently not supported, and the way I'd like to add support for it is by logging previous runs and letting...
Nextest doesn't currently support this, but it should definitely be possible to add it! I think the main blocker for this is the UI design more than the implementation. Some...