liveBook · Manning

Parallel test execution

Parallel test execution is the concurrent execution of multiple eligible tests rather than their sequential execution, typically to reduce total testing time.

How 2 Manning books explain it

Code Like a Pro in Rust

Parallel test execution runs multiple tests concurrently, typically on separate threads, to reduce total testing time.

How it is used
Handles shared global state and fixtures when Cargo executes Rust unit tests concurrently.
How deep it goes
Works through compiler failures, atomic counters, Arc initialization, lazy_static expansion, and mutex-based serialization.
Examples
Uses a mutable static counter, AtomicI32, Arc, lazy_static, and two mutex-guarded tests.
What you can do after
Configure and debug concurrent Rust tests by selecting atomics, lazy initialization, mutexes, or a custom harness.

Read how Code Like a Pro in Rust explains parallel test execution →

The Art of Unit Testing 3e

Parallel test execution is the concurrent execution of multiple tests to reduce total test execution time.

How it is used
Speeds unit-test feedback, pipeline stages, test layers, and large end-to-end suites.
How deep it goes
Descends from execution patterns to shared-state failure modes, but stops short of detailed runner configuration.
Examples
Uses Jest beforeEach() setup, a shared verifier, fake validation rules, parallel E2E suites, and dynamic environments.
What you can do after
Operate/configure parallel tests and pipelines while isolating mutable state and reducing feedback delays.

Read how The Art of Unit Testing 3e explains parallel test execution →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.