Sequential Test Execution

Ensures test runs execute one at a time to prevent resource conflicts.

Core Principle

One Test Run at a Time

Test environments share databases, ports, and network resources. Concurrent test execution causes migration conflicts, port collisions, and flaky test results.

Detection Method

Uses Docker container state (not file locks) to detect running tests:

• Self-recovering: docker compose run --rm auto-removes containers on exit
• No stale locks: docker ps reflects actual running state
• Graceful degradation: If Docker is unavailable, tests proceed normally