test-setup

To scaffold automated testing infrastructure, this setup creates a standardized tests directory and a GitHub Actions CI workflow. It detects your engine, generates unit, integration, and smoke test folders, and wires CI to execute the appropriate engine test runner.

Yes, the test scaffold supports Godot, Unity, and Unreal engine detection. It creates the correct engine-aware test runner and supporting files, satisfying engine detection requirements while safely skipping or creating missing artifacts.

The best way to organize tests is using a standardized taxonomy that creates tests/unit/, tests/integration/, tests/smoke/, and tests/evidence/ directories. It includes an engine-agnostic README explaining how to write and categorize tests within these paths.

Yes, you can safely regenerate the GitHub Actions workflow because updates are non-destructive. It never overwrites existing files and only creates missing paths, with an optional force mode to rerun the plan without clobbering your current artifacts.

You need to run the test setup pass after your engine is configured. This ensures the scaffolding correctly detects Godot, Unity, or Unreal to generate the proper tests/ structure and the .github/workflows/tests.yml workflow.

The CI workflow triggers on every push and pull request, so if it does not trigger, ensure your tests/ structure and .github/workflows/tests.yml were generated after engine configuration. Missing engine artifacts can cause the setup to skip wiring the test runner.