nextest
nextest copied to clipboard
nextest-rs
A next-generation test runner for Rust.
Depends on https://github.com/taiki-e/cargo-llvm-cov/pull/259 (edit: has been released) This is done similarly for miri and makes sense since both increase running times.
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.
When running tests the time they take to execute is output to the console, it would also be valuable to see their maximum memory usage. With large test sets you...
For a Rust project, I need to add a GitHub workflow for tests on OpenBSD OS (using this GH action [vmactions/openbsd-vm](https:/github.com/vmactions/openbsd-vm)). In this workflow, I'm using `nextest` to run tests...
We're considering switching to `nextest` to run our Rust tests in CI over at Ruffle. (Cc: https://github.com/ruffle-rs/ruffle/pull/14461) It's been great so far! The final issue we have is, that compared...
## Summary Github actions recently added the ability to output a Markdown-formatted test summary : https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/ It would be great to have a straightforward Markdown output mode that would populate...
```bash $ cargo nextest --version cargo-nextest-nextest 0.9.66 $ ~/.cargo/bin/cargo-nextest --version cargo-nextest 0.9.66 ``` The output of `cargo nextest --version` is `cargo-nextest-nextest 0.9.66`, I think this is not right?
I saw the Gatekeeper issue described out there, but I'm not sure this is the same. I did add the terminal to developer tools. That didn't help. So, here's the...
* **Initial implementation**: https://github.com/nextest-rs/nextest/pull/977 * **Documentation**: https://nexte.st/book/setup-scripts.html ## Open questions - [ ] How do we support build archive/reuse with Cargo binaries? - [ ] Is the current format for...