mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-06 21:12:55 +00:00
doc(README): note cargo-nextest usage (#7122)
We have been using #5681 for quite some time, and at least since #6931 the tests have assumed `cargo-nextest` to work around our use of global statics. Unlike the `cargo test`, the `cargo nextest run` runs each test as a separate process that can be timeouted. Add a mention of using `cargo-nextest` in the top-level README.md. Sub-crates can still declare they support `cargo test`, like `compute_tools/README.md` does.
This commit is contained in:
@@ -238,6 +238,14 @@ If you encounter errors during setting up the initial tenant, it's best to stop
|
|||||||
|
|
||||||
## Running tests
|
## Running tests
|
||||||
|
|
||||||
|
### Rust unit tests
|
||||||
|
|
||||||
|
We are using [`cargo-nextest`](https://nexte.st/) to run the tests in Github Workflows.
|
||||||
|
Some crates do not support running plain `cargo test` anymore, prefer `cargo nextest run` instead.
|
||||||
|
You can install `cargo-nextest` with `cargo install cargo-nextest`.
|
||||||
|
|
||||||
|
### Integration tests
|
||||||
|
|
||||||
Ensure your dependencies are installed as described [here](https://github.com/neondatabase/neon#dependency-installation-notes).
|
Ensure your dependencies are installed as described [here](https://github.com/neondatabase/neon#dependency-installation-notes).
|
||||||
|
|
||||||
```sh
|
```sh
|
||||||
|
|||||||
Reference in New Issue
Block a user