gds-e2e-scaffold

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

Updated May 7, 2026
One-click install
npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-e2e-scaffold-jgabriellima
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-e2e-scaffold
Source: https://github.com/jgabriellima/deep-agent-skill/tree/main/skills/gds-e2e-scaffold
Command: npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-e2e-scaffold-jgabriellima

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 infrastructure code. - 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 functions correctly. - Use Case: A Unity developer with an existing game project runs the scaffold to get a complete Tests/PlayMode/E2E directory with a fluent scenario builder, input simulation for the New Input System, and async wait utilities, then immediately writes player journey tests. ## Quick Start Ask the agent to set up e2e testing infrastructure for your game project and answer its questions about your game state class and main scene.

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

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

What game engines does this E2E scaffold support?▼

The scaffold supports Unity, Unreal, and Godot. It detects the engine from project files like ProjectSettings, .uproject files, or project.godot, then generates infrastructure in the appropriate language and directory structure for that engine.

What prerequisites are needed before scaffolding E2E tests?▼

You need an initialized test framework, an identifiable game state manager class, a functional main gameplay scene, and no existing E2E infrastructure. The workflow halts and guides you if any preflight requirement fails.

Does the input simulator work with Unity's New Input System?▼

Yes, when the New Input System is detected, the generated InputSimulator uses InputState.Change and StateEvent.From for clicks, drags, and keyboard input. For Legacy Input, it generates a simpler version using UI event triggering.

What files does the E2E scaffold generate?▼

It generates an assembly definition, GameE2ETestFixture base class, ScenarioBuilder with fluent API, InputSimulator, AsyncAssert utilities, an example test with three verification cases, and a README covering usage, extension, and troubleshooting.