From 658ce57ed56bdd87f9aba6edc38c0217d07501c8 Mon Sep 17 00:00:00 2001 From: Jason Robinson Date: Thu, 7 Aug 2025 13:33:59 +0300 Subject: [PATCH] Docs: Run local tests via `cargo-nextest` Mention this specifically in contributing.md since CI also uses this test runner. My attempt to use `cargo test` failed due to PG connection pooling. In any case, unless there are reasons not to, we should keep close to mirroring what we do in CI. --- docs/development/contributing.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/development/contributing.md b/docs/development/contributing.md index abf91c2e4..00ecf6fea 100644 --- a/docs/development/contributing.md +++ b/docs/development/contributing.md @@ -89,7 +89,9 @@ While you're developing and before submitting a patch, you'll want to test your ### Run the tests -- Run the tests to the backend by running `cargo test --workspace`. This requires a connection to a PostgreSQL database, set via the `DATABASE_URL` environment variable. +If you haven't already, install [Cargo-Nextest](https://nexte.st/docs/installation/pre-built-binaries/). + +- Run the tests to the backend by running `cargo-nextest nextest run --workspace`. This requires a connection to a PostgreSQL database, set via the `DATABASE_URL` environment variable. - Run the tests to the frontend by running `npm run test` in the `frontend` directory. ## 8. Submit a pull request