gds-test-automate

Generates unit, integration, E2E, and smoke tests for Unity, Unreal, and Godot game projects.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-test-automate-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-test-automate
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/gds-test-automate
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-test-automate-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing automated tests for game code is time-consuming and engine-specific. This Skill analyzes a game codebase, detects the engine in use, and generates structured test suites with correct patterns, fixtures, and cleanup so teams get test coverage without hand-writing boilerplate. ## Core Features & Use Cases - Engine Detection: Automatically identifies Unity, Unreal, or Godot projects from project files and loads engine-specific testing knowledge. - Multi-Level Test Generation: Produces NUnit unit tests, Unreal Automation Tests, GUT tests, scene integration tests, E2E infrastructure (fixtures, scenario builders, input simulators), and critical-path smoke tests. - Validation & Reporting: Applies a completion checklist and writes an automation summary report listing test distribution, files created, and next steps. - Use Case: After designing test scenarios for a Unity RPG's inventory system, run this Skill to generate parameterized NUnit fixtures, scene-load integration tests, and a smoke suite covering launch, new game, and save/load. ## Quick Start Ask the assistant to automate tests for the gameplay systems in this project and generate unit, integration, and smoke tests for the detected engine.

Frequently Asked Questions about gds-test-automate

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

FAQPage Schema
How do I generate automated tests for a Unity game?

Run the test automation workflow after initializing a test framework. It detects Unity via Assets/ and ProjectSettings/ folders, then generates NUnit unit tests, Play Mode integration tests, and smoke tests under the tests/ directory.

How to write unit tests for Unreal Engine C++ gameplay code?

The workflow generates Unreal Automation Test macros using IMPLEMENT_SIMPLE_AUTOMATION_TEST with Arrange-Act-Assert structure and TestEqual assertions. Tests are placed under the project's test directory following Unreal conventions.

Does the test generator support Godot GDScript projects?

Yes, Godot projects are detected via project.godot and .tscn files. Tests are generated for the GUT framework with before_each/after_each lifecycle hooks, parameterized test cases, and scene instantiation integration tests.

What prerequisites are needed before generating game tests?

A test framework must already be initialized in the project, game source code must be accessible for analysis, and test scenarios should exist from a test-design step. If any prerequisite is missing, the workflow halts and guides the user.

What test anti-patterns does the generator avoid?

Generated tests avoid testing engine functionality instead of game logic, hard-coded waits as primary synchronization, execution-order dependencies, and missing teardown cleanup. Async handling uses signals, events, and WaitUntil-style assertions.