test-setup

Scaffolds engine-specific test directories, runner configs, and GitHub Actions CI workflows.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill test-setup-frabcd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-setup
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/test-setup
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill test-setup-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up automated testing late in a game project is expensive and error-prone. This Skill scaffolds the complete test infrastructure—directory layout, engine-specific test runner configuration, and CI/CD pipeline—during the Technical Setup phase so tests run on every push from day one. ## Core Features & Use Cases - Engine Detection and Gating: Reads the configured engine from .ai-game-studio/project.json and refuses to proceed if the engine is not configured, redirecting to engine setup first. - Per-Engine Scaffolding: Generates GdUnit4 runner scripts for Godot, EditMode/PlayMode test folders for Unity, and Automation test guidance for Unreal Engine. - CI/CD Workflow Generation: Creates .github/workflows/tests.yml using the appropriate action (gdUnit4-action, game-ci/unity-test-runner, or a self-hosted UE runner). - Use Case: Before the first sprint of a Godot project, run this Skill to create tests/unit, tests/integration, tests/smoke/critical-paths.md, and a GitHub Actions workflow that blocks merges on failing tests. ## Quick Start Use $ai-game-studio:test-setup to scaffold the test framework and CI/CD pipeline for this project and report the created files.

Frequently Asked Questions about test-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up automated tests for a Godot project?▼

Run this Skill after configuring your engine to generate a GdUnit4 runner script, tests/unit and tests/integration directories, and a GitHub Actions workflow using gdUnit4-action. You then install GdUnit4 via the Godot AssetLib and enable the plugin.

How do I add CI testing to a Unity game project?▼

The Skill creates EditMode and PlayMode test folders plus a GitHub Actions workflow using game-ci/unity-test-runner. You must manually add a UNITY_LICENSE secret to your GitHub repository before the first CI run.

Does this work with Unreal Engine projects?▼

Yes, it creates a Source/Tests directory with Automation Testing Framework guidance and a CI workflow. Unreal CI requires a self-hosted runner with the Unreal Editor installed and the UE_EDITOR_PATH environment variable set.

Will running test setup overwrite my existing test files?▼

No, the Skill never overwrites existing files. It detects existing test infrastructure and only creates missing files, even when the force argument is passed to skip the early-exit check.

What happens if my game engine is not configured yet?▼

The Skill stops immediately and instructs you to run the engine setup command first. Engine detection is non-negotiable and it will not guess which framework to scaffold.