The number of threads can be specified when you run a test. Running tests in parallel can be disabled by running: cargo test -- --test-threads=1 This disables it for all tests. Is there a way to specify a certain test module, or integration test, must be ran in a single thread but the rest can be…

The only time I've seen a need for this is when accessing the file system during tests. If many tests use the same file name it causes problems when they run in parallel. I've fixed this by using the tempdir crate so that every test has it's own workspace when running. I'm not sure if that will hel…

Isolating tests to avoid this problem is the best. Global mutex sounds like an OK option too. Rust on principle assumes everything is thread-safe, so it's a good practice to keep code under test thread-safe too. --test-threads=1 is useful for discovering which test causes crash of the test suite (b…

I agree that having the tests being isolated is ideal. I'm working on a wrapper for a project created by another team. I am already using temporary files where possible (which enables most tests to be run in parallel). The problem is that they have a global config variable that can be set. Test A ca…

Disable parallel testing for module

help

cuviper September 6, 2018, 8:37pm 2

If you put it in a standalone file in tests/, it will run on its own.

Topic		Replies	Views
How tests are run: threads	6	1549	January 5, 2019
How to run FFI tests individually help	7	984	October 31, 2018
Passing --test-threads=1 to cargo test by default? help	12	9059	March 27, 2023
How are cargo tests run (serially or in parallel)? help	10	7381	July 20, 2017
Is disabling parallel testing a bad code design? code review	7	323	April 16, 2025

Disable parallel testing for module

Related topics