-
**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…
-
I wanted to do some simple tests of how much improvement this repo could get from basically two interventions:
1. Drop in `nextest` for the unit tests task
2. Use 4vcpu or 8vcpu buildjet runners
…
-
- [x] improve CLI for nicer output: #28
- [x] add generators for entity (add example load/create functions, changeset with validations, etc.), entity test helpers, middleware, controller + controller…
-
We currently run all, or at least most, of the TSS tests serially. This is done to avoid
having different tests write conflicting state to the same DBs, and to ensure each test
is using a "clean" envi…
-
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 at most.
- [ ] Add test for #926.
- [ ] Mov…
-
Hello 👋🏼
We are experiencing some `nextest` related test failures here: https://github.com/ratatui-org/ratatui/pull/981
In a nutshell, initializing a terminal with [ratatui](https://github.com/…
orhun updated
5 months ago
-
### 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 …
-
Currently, nextest doesn't support Rust doctests. This is because doctests are not exposed in stable Rust the way regular test binaries are, and are instead treated as special by `cargo test`.
One …
-
- Issue: https://github.com/napi-rs/napi-rs/issues/1405
- Found on: #274
- Workaround: `cargo nextest run` → `cargo test` for Windows
-
I switched to nextest from cargo test because it's 50% faster, which is great for local development. However, when I landed the change upstream, my code coverage dropped significantly. You can see the…