test-setup

To set up automated testing and CI for Unity or Godot, you can scaffold engine-specific test directories and a GitHub Actions workflow that runs unit, integration, and smoke tests on every push and pull request. This detects your engine configuration and generates the appropriate runner artifacts.

The best way to structure test directories for game engine projects is to create a standard layout with unit, integration, smoke, and evidence subdirectories. This supports automated tests, cross-system validation, and manual QA evidence workflows to catch regressions early.

Yes, this test scaffolding tool works with Unreal Engine, as well as Godot and Unity. It reads your engine configuration to detect the specified engine and only creates the appropriate engine-specific runner artifacts for your project.

To generate a GitHub Actions workflow that runs tests on push and PR, you can use a guided setup that wires a `.github/workflows/tests.yml` file to your repository. This workflow executes your test suites and uploads results or artifacts appropriate to your engine.

Scaffolding tests will not overwrite your existing CI files and test runners. The setup process detects existing test and CI state, asks for approval before file creation, and only creates missing files, refusing to overwrite existing ones even when using the force argument.

The difference between unit, integration, and smoke testing in CI is scope: unit tests validate individual components, integration tests check cross-system functionality, and smoke tests verify critical basic functionality. Scaffolding these directories ensures repeatable verification across all levels.