ln-635-test-isolation-auditor

To detect test isolation issues, you audit test suites for state leakage across APIs, databases, file systems, time, random number generators, and network interactions. This identifies hidden dependencies causing flaky tests.

Common testing anti-patterns that degrade reliability include shared mutable state, uncontrolled time, and network dependencies. Detecting these seven specific anti-patterns helps improve test maintainability and determinism.

Intermittent CI failures often stem from poor test isolation and non-deterministic execution. Auditing reveals state leakage across databases or file systems and detects order-dependent tests causing inconsistent results.

To audit database and file system state leakage, you scan test suites for residual mutations and uncleaned records. This verifies tests do not leak state between each other across these storage boundaries.

Test isolation auditing explicitly covers random number generators and network interactions. It checks whether these external dependencies introduce non-determinism, ensuring your tests remain predictable across different environments.