-
### Description about the bug
There was a case that nextest failed by timeout found on github workflow. When I reruned the code without modifing any code, the failure disappeared.
It's a rare err…
-
I find both `bacon` and [`cargo nextest`](https://nexte.st/) to be very useful, and I would like to use them together.
I can persuade `bacon` to run tests via `cargo nextest` by specifying this in …
-
```sh
$ cargo +nightly careful --help
fatal error: `cargo careful` supports the following subcommands: `run`, `test`, `build`, `nextest`, and `setup`.
```
but then
```sh
$ cargo +nightly carefu…
-
[cargo-nextest](https://nexte.st/) provides better interface and faster execution speed to rust tests, we should move to it to improve developer experience.
-
#### Description
This issue occurs with numerous tests ran within a suite of 415 other tests. The vast majority of these tests are of the same complexity as the test shown below (i.e.: simple methods…
-
Nextest currently suppose grouping tests to run exclusively.
However, the filter DSL works in a irrelevant way, so that when I'd like to run a specific test group, I have to write the filter DSL tw…
-
Nextest has some features that might be helpful but which we do not yet use:
1) marking tests as needing multiple threads
Currently, we run all of the tests with a single thread in our nighly ru…
-
[Cargo Nextest](https://nexte.st/) has a different test execution model where each test is compiled into a separate binary. This causes issues with macrotest- it seems that it assumes that each crate …
-
We're using hyper-rustls with the `webpki-tokio` feature enabled. The intention behind this is that we vendor the CA via webpki and make this explicitly extensible with custom CAs in the future.
Ru…
-
### Feature description
more of a question than a feature request, is it possible to pass --show-output/--no-capture to cargo/nextest somehow like in https://github.com/rouge8/neotest-rust or get te…