gds-e2e-scaffold

Generates end-to-end testing infrastructure for Unity, Unreal, and Godot game projects.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill gds-e2e-scaffold-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-e2e-scaffold
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/gds-e2e-scaffold
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill gds-e2e-scaffold-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up end-to-end testing for a game project requires building test fixtures, scenario builders, input simulators, and async assertion utilities from scratch, which is error-prone and often skipped entirely. ## Core Features & Use Cases - Engine Detection: Automatically detects Unity, Unreal, or Godot projects and generates engine-appropriate test infrastructure. - Infrastructure Generation: Creates GameE2ETestFixture, ScenarioBuilder, InputSimulator, and AsyncAssert components tailored to the project's game state manager and input system. - Working Example Test: Produces a runnable example test plus README documentation proving the infrastructure works. - Use Case: A Unity developer with an existing game runs this workflow to get a complete Tests/PlayMode/E2E directory with a fluent scenario builder, input simulation for the New Input System, and async wait utilities, ready for writing player journey tests. ## Quick Start Ask the AI to set up e2e testing infrastructure for your game project by saying "e2e scaffold" or "set up e2e testing".

Frequently Asked Questions about gds-e2e-scaffold

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

FAQPage Schema
How do I set up E2E testing for a Unity game?

Run this workflow after initializing a test framework. It detects your game state manager, main scene, and input system, then generates a Tests/PlayMode/E2E directory with a test fixture, scenario builder, input simulator, and async assertion utilities.

How to simulate input in Unity end-to-end tests?

The generated InputSimulator uses the New Input System's InputState.Change and StateEvent.From to simulate clicks, drags, and key presses. If your project uses Legacy Input, a simpler UI event triggering version is generated instead.

Does this E2E scaffold support Unreal and Godot?

Yes, the workflow detects the engine from project files and generates equivalent infrastructure. Unreal gets C++ test base classes under Source/Tests/E2E, and Godot gets GDScript files under tests/e2e/infrastructure.

What are the prerequisites for scaffolding E2E game tests?

A test framework must already be initialized, the game must have an identifiable state manager class, and a functional main gameplay scene must exist. The workflow halts if E2E infrastructure already exists to avoid conflicts.

Why do E2E game tests become brittle and how to avoid it?

Brittleness comes from fixed-time waits and hardcoded state setup. The generated AsyncAssert waits for conditions rather than time, and the ScenarioBuilder configures game state through a fluent API instead of fragile manual setup.