test-setup

To set up GitHub Actions CI for Unity tests, this scaffolding tool detects your engine configuration, generates a standard tests directory structure with unit and integration folders, and wires up a GitHub Actions workflow to run tests on every push.

If the engine is not configured, the test setup instructs you to run /setup-engine first and only creates missing files while preserving existing ones, ensuring no current project configurations are overwritten during the scaffolding process.

Yes, this test scaffolder generates a standard tests layout that includes separate directories for both unit and integration tests, alongside the engine-specific test runner configuration needed to execute them within your continuous integration pipeline.

Yes, you can run this CI workflow setup repeatedly because it preserves existing files and only creates missing infrastructure components, making it safe to execute multiple times during technical setup without overwriting your current tests.

You should run the test infrastructure scaffolding once during the Technical Setup phase to accelerate sprint kickoff, providing a guided and repeatable process for wiring up continuous integration and engine-specific test runners.

The best way to scaffold automated testing infrastructure is using a tool that detects your configured engine, builds the tests directory structure automatically, and wires up GitHub Actions workflows to ensure tests run on every push.