-
If a test fails due to a signal (e.g. a SIGSEGV), nextest currently just reports it as a generic failure, probably with no stdout:
```
FAIL [ 0.010s] openssl pkey::tests::te…
-
Hi,
I am using **cargo-nextest 0.9.14**
I have a crate with the following test code
```
#[cfg(test)]
mod tests {
#[test]
fn simple() { }
#[test]
fn extended() { }
…
-
Hi there -- thanks for the library! I'm having a lot of fun integrating it into [cargo-nextest](https://nexte.st).
A little issue I'm running into is that currently there's only two ways to format …
-
**Description**
See title.
**Repro steps**
```
METAL_DEVICE_WRAPPER_TYPE=1 cargo nextest run --all --no-fail-fast
```
**Expected vs observed behavior**
Errors out with:
```
…
-
when some of you're tests fail I would like to see a list of all the failed tests like in cargo test. This would help to see witch tests failed without having to scroll up the terminal (when you have …
-
# Steps to reproduce
1. `git clone https://github.com/nextest-rs/nextest`
2. `cd nextest`
3. `cargo +nightly build --release`
# Relevant log output
```shell
➜ cargo +nightly build --release
…
-
Thank you very much for this project, it really makes the testing experience in Rust much more fun and productive.
I've come across what I suspect to be an incompatibility between `nextest` and ano…
-
The Jenkins JUnit XML format includes a `` tag for tests that error:
```xml
type=""
failure description
```
Many tools that ingest JUnit XML expect this ta…
hawkw updated
2 years ago
-
Seems to be a good alternative to `cargo test`. Faster, detect flaky tests (e.g. #320).
-
we're saving 20s with [nextest](https://nexte.st/), might be worth at some point in time.
mimoo updated
2 years ago