-
Let me start by saying, thank you for the great runner. I exclusively use it everywhere.
Maybe I'm just too dumb, but after 30 minutes of trial and error, I couldn't get nextest to run a test calle…
-
### Feature Description
as the title
### Describe The Solution You'd Like
### Code Sample
```rust
/// paste code here
```
-
**Issue summary**
Our tests right now are a bit messy, they're split across
- shell scripts
- coverage
- tests
- rust test
- unit tests
- integration tests
Some tests call out to the…
-
Thank you very much for this crate, which is a huge boon to productivity in testing Rust projects.
I've stumbled across something which looks like an incompatibility between `#[once]` and [`cargo n…
jacg updated
9 months ago
-
### Motivation
I'm already developing for the workers-rs platform (workerd)
1. About 1000 test templates running with wasm-bindgen-test and firefox
2. Almost 400 in a single crate
3. In the heav…
-
### Describe the bug
Processes/`Command`s spawned in tests currently inherit the environment variables of the command running the tests. This can cause tests to fail in certain cases, depending on …
-
For the most part `cargo nextest` is interchangeable with `cargo test`, but not when swapping one out for the other with `cargo-hack`.
For example, the following error is seen when invoking `cargo-…
-
When I run my tests with `datatest-stable` (0.2.9), using `nextest` as the runner, a semi-random number of tests are marked as leaky.
This seems to only depend on how many tests the crate has, and …
-
An existing [sonar rust](https://github.com/elegoff/sonar-rust) plugin [does not accept](https://github.com/elegoff/sonar-rust/issues/67) junit reports without `message` attribute filled. So until bug…
-
If i use the installer script for linux (`curl -LsSf https://get.nexte.st/latest/linux | tar zxf - -C ${CARGO_HOME:-~/.cargo}/bin`) on an `alpine` docker container, i get a glibc build instead of the …