test-environment

Run tests in isolated containers by executing the Skill's script, which provisions separate test databases and containers, runs your unit, integration, and end-to-end tests independently, then cleans up automatically. This prevents test interference and ensures repeatable results without affecting your development environment.

Yes. The Skill supports both .NET unit and integration tests alongside Playwright E2E tests in the same isolated container setup. Use `--mode all` to run all test types sequentially in fresh, separate containers with dedicated test databases.

Containers and images are automatically removed after test runs to prevent leftovers and resource bloat. Use the `--keep-containers` flag if you need to preserve containers for debugging or inspection after test execution.

Use container isolation when dev containers are busy, test isolation is critical for reliability, or you need guaranteed clean environments. It's essential for integration and end-to-end tests where test order or state dependencies could cause failures in shared environments.

The Skill requires Docker, Docker Compose for orchestration, Node.js and npm for Playwright, psql for database operations, jq for JSON processing, and .NET for unit and integration tests. All dependencies must be installed and accessible in your environment.

The Skill includes automated health-checks during container startup to ensure databases and services are ready before tests execute. This prevents flaky tests caused by services not fully initialized and is handled automatically without manual intervention.