test-setup

Scaffolds test directories, engine-specific test runners, and GitHub Actions CI workflows for game projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up automated testing infrastructure for a game project is repetitive and engine-specific, and teams often delay it until technical debt makes it expensive. This Skill scaffolds the complete test framework and CI/CD pipeline in one pass, before the first sprint begins. ## Core Features & Use Cases - Engine Detection and Scaffolding: Reads the configured engine (Godot, Unity, or Unreal) from the project config and generates the matching test runner, directory layout, and documentation. - CI/CD Workflow Generation: Creates a GitHub Actions workflow that runs tests on every push and pull request, using GdUnit4, Unity Test Framework, or UE Automation as appropriate. - Smoke Test Seed and QA Gates: Generates a critical-path smoke test checklist and a story-type-to-test-evidence mapping so QA requirements are defined from day one. - Use Case: A team starting a new Godot game runs this once during Technical Setup and gets a tests/ directory, a GdUnit4 runner, a CI workflow, and a smoke checklist without writing any configuration by hand. ## Quick Start Ask the AI to run the test-setup skill to scaffold the test framework and CI pipeline for the configured game engine.

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 game project?

Run this skill after configuring your engine; it creates a tests/ directory with unit and integration subfolders, a GdUnit4 runner script, and a GitHub Actions workflow using the gdUnit4-action. You then install GdUnit4 from the Godot AssetLib and enable the plugin.

How do I add CI/CD testing to a Unity project with GitHub Actions?

The skill generates a GitHub Actions workflow using game-ci/unity-test-runner that runs Edit Mode and Play Mode tests on every push. You must add a UNITY_LICENSE secret to your repository settings before the first CI run.

Does this test setup support Unreal Engine projects?

Yes, it creates a Source/Tests/ directory with UE Automation Testing Framework documentation and a CI workflow that runs automation tests headlessly. Unreal CI requires a self-hosted runner with the Unreal Editor installed and a UE_EDITOR_PATH environment variable.

Will running test setup overwrite my existing test files?

No, the skill never overwrites existing files. It detects existing test infrastructure, reports what is already present, and only creates missing files, even when the force flag is passed.

What happens if my game engine is not configured yet?

The skill stops and instructs you to run the setup-engine skill first. Engine detection is mandatory because the generated test runner, directory layout, and CI workflow differ per engine.