test-isolation-slot-hygiene

Test isolation prevents cross-run contamination by detecting leaked state like saved slots, snapshots, caches, and temp dirs between executions. This skill enforces clean-room isolation by automating artifact discovery and standardizing locations to guarantee repeatable results.

Cross-run contamination occurs when leaked state like saved slots or caches persist between test executions. This skill enforces clean-room isolation by automating terminal-based artifact discovery and standardizing locations to ensure repeatable results across CI and local runs.

Enforce clean-room test execution by running a hygiene workflow that initializes a clean per-test environment and applies isolation checks. This prevents leaked state from persistence or replay logic from contaminating subsequent test runs.

Standardize test artifact locations by authoring helper scripts that automate hygiene and enforce per-run isolation. This approach ensures repeatable results by preventing cross-run contamination from misplaced slots, snapshots, caches, and temp directories.

Yes, you can use terminal-based scripts to automate test isolation checks. This skill provides helper scripts for hygiene automation, allowing you to discover leaked artifacts and enforce clean-room execution during test authoring and debugging.

Apply slot hygiene automation during test authoring, when debugging flaky tests, or when modifying slot registry logic. It is essential whenever leaked state from previous runs threatens the repeatability and clean-room execution of your simulation tests.