Rain
Hi there! So this is a really fun issue I spent some time debugging. I had written an adapter that sits on top of a `Peekable`. I had some code...
Gated behind an environment variable for now. TODO: - [ ] Code to read test runs (probably in a separate PR) - [ ] Tests - [ ] Docs -...
- **Initial implementation:** #1086 - **Nextest version:** 0.9.65 and above - **Enable with:** Set `NEXTEST_EXPERIMENTAL_LIBTEST_JSON=1` in the environment Still to do before stabilizing the format: - [x] Include stderr and...
This is quite tricky to do because there are a number of different permutations involved. Putting up this WIP to get back to at some point in the future (or...
This isn't done yet, and I'd love if someone else picked up this work.
* **Initial implementation**: https://github.com/nextest-rs/nextest/pull/977 * **Documentation**: https://nexte.st/docs/configuration/setup-scripts/ ## Open questions - [ ] How do we support build archive/reuse with Cargo binaries? - [ ] Is the current format for...
# Summary Currently, test name filters can be specified both with and without `--`: ``` cargo nextest run my_test # ... (format 1) cargo nextest run -- my_test # ......
In #926, it took almost 20 minutes to fully yank the bad version. We need to improve our story here -- yanking a bad release should take under 5 minutes...
If: * A test binary has a custom test harness, and * Listing tests fails (e.g. #908) Then, we should print an error and suggest https://nexte.st/book/custom-test-harnesses.html to users.
Rust 1.64 includes support for multiple `--target` or `build.target` arguments. Nextest should support them. Some challenges: 1. Cargo's JSON messages don't contain the name of the target. However, it can...