xUnit 4 ParallelMode.All: Protect Shared State from Test Races

xUnit 4.0.0 introduces ParallelMode.All, which enables full test-case parallelization. This change has significant implications for test suites, as tests within the same class, including different rows of a theory, may now run concurrently and compete for shared resources. These shared resources can include static fakes, fixtures, temporary files, or database records that were previously safe under collection-level parallelism.

Enabling ParallelMode.All without proper consideration can introduce race conditions and concurrency issues. To safeguard against these problems, it is essential to audit and protect shared state explicitly. This involves checking for mutable static fields, IClassFixture and ICollectionFixture implementations, fixed file names, environment variable changes, tests bound to fixed ports, and records addressed by shared IDs within the test data sources.

Once the inventory of shared resources is established, each should be evaluated for concurrency safety. If a resource requires concurrency safety, it should either receive a unique per-test identity or remain behind an explicit opt-out. For tests that must not overlap, the DisableParallelization attribute can be used to prevent parallel execution.

This approach ensures that the verifier can reliably detect lost updates and concurrency issues, rather than relying on timing-only tests that may pass under specific conditions. By carefully auditing shared resources and applying targeted opt-outs, developers can maintain test isolation and prevent unintended interactions between concurrent test cases.