test-setup

# Test Setup This skill scaffolds the automated testing infrastructure for the project. It detects the configured engine, generates the appropriate test runner configuration, creates the standard directory layout, and wires up CI/CD so tests run on every push. Run this once during the Technical Setup phase, before any implementation begins. A test framework installed at sprint start costs 30 minutes. A test framework installed at sprint four costs 3 sprints. **Output:** `tests/` directory structure + `.github/workflows/tests.yml` --- ## Phase 1: Detect Engine and Existing State 1. **Read engine config**: - Read `.claude/docs/technical-preferences.md` and extract the `Engine:` value. - If engine is not configured (`[TO BE CONFIGURED]`), stop: "Engine not configured. Run `/setup-engine` first, then re-run `/test-setup`." 2. **Check for existing test infrastructure**: - Glob `tests/` — does the directory exist? - Glob `tests/unit/` and `tests/integration/` — do subdirectories exist? - Glob `.github/workflows/` — does a CI workflow file exist? - Glob `tests/gdunit4_runner.gd` (Godot) or `tests/EditMode/` (Unity) or `Source/Tests/` (Unreal) for engine-specific artifacts. 3. **Report findings**: - "Engine: [engine]. Test directory: [found / not found]. CI workflow: [found / not found]." - If everything already exists AND `force` argument was not passed: "Test infrastructure appears to be in place. Re-run with `/test-setup force` t...