test-helpers

Generate engine-specific test helper libraries with assertions, factories, and mocks for game projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing game tests involves repeating the same setup, teardown, and assertion boilerplate across every test file. This Skill reads your existing test patterns and generates a tailored tests/helpers/ library so developers write more assertions and less scaffolding. ## Core Features & Use Cases - Engine-Specific Generation: Produces helper code for Godot 4 (GDUnit4/GDScript), Unity (NUnit/C#), and Unreal Engine (C++ automation tests), matching the project's configured engine and language. - Pattern Matching: Scans up to five existing test files to extract setup, assertion, object creation, and mock patterns so generated helpers match the project's actual style. - GDD-Traced Constants: Derives bounds and constants in generated factories from GDD Formulas sections rather than invented values. - Use Case: After scaffolding a test framework for a Godot project, run the skill in scaffold mode to create game_assertions.gd, game_factory.gd, and scene_runner_helper.gd, then generate a combat-specific factory traced to the combat GDD. ## Quick Start Ask the AI to generate engine-specific test helper libraries for this project using the test-helpers skill and report which files were created.

Frequently Asked Questions about test-helpers

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

FAQPage Schema
How do I generate test helper libraries for a Godot game project?

Run the skill in scaffold mode on first use to create base helpers like game_assertions.gd and game_factory.gd, or pass a system name such as combat to generate system-specific factories. The skill reads your engine configuration from .ai-game-studio/project.json and existing test files to match your style.

What game engines does test helper generation support?

The skill supports Godot 4 with GDUnit4 and GDScript, Unity with NUnit and C#, and Unreal Engine with C++ automation test macros. It detects the engine and language from the project configuration file before generating helpers.

Will generating test helpers overwrite my existing helper files?

No, the skill never overwrites existing files. If a helper file already exists, it reports that the file is being skipped and asks you to remove it manually if you want it regenerated, protecting hand-written customizations.

How do generated test factories stay consistent with game design values?

The skill reads the relevant GDD files, including Formulas sections and Edge Cases, to extract data types, variable bounds, and test scenarios. Constants like damage ranges in generated factories trace back to GDD specifications rather than invented values.

When should I run test helper generation in my workflow?

Run it after the test framework has been scaffolded, when multiple test files repeat the same setup boilerplate, or when starting tests for a new system. If no engine is configured, you must run the engine setup step first.