gds-e2e-scaffold

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

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill gds-e2e-scaffold-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-e2e-scaffold
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/gds-e2e-scaffold
Command: npx skills add https://github.com/PastaSus/egg-defender --skill gds-e2e-scaffold-pastasus

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. This Skill scaffolds that entire foundation automatically, tailored to the project's engine and architecture. ## Core Features & Use Cases - Engine Detection and Analysis: Detects Unity, Unreal, or Godot projects and identifies the game state manager, input system, and main gameplay scene before generating any code. - Infrastructure Generation: Creates a test fixture base class, fluent ScenarioBuilder, InputSimulator, and AsyncAssert utilities matched to the detected engine and input system. - Working Example Test: Produces a runnable example E2E test plus a README with quick start, best practices, and troubleshooting guidance. - Use Case: A Unity developer with an existing game wants to start writing E2E tests. The Skill generates the Tests/PlayMode/E2E directory with an assembly definition, fixture, and utilities, then verifies setup with a passing infrastructure test. ## Quick Start Ask the assistant to scaffold e2e testing infrastructure for your game project and provide your game state class and main scene name.

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 a test framework. It generates a Tests/PlayMode/E2E directory with an assembly definition, GameE2ETestFixture base class, ScenarioBuilder, InputSimulator, AsyncAssert utilities, and a working example test.

What game engines does E2E test scaffolding support?

The workflow supports Unity, Unreal, and Godot. It auto-detects the engine from project files like ProjectSettings, .uproject, or project.godot, then generates engine-appropriate infrastructure in C#, C++, or GDScript.

Does the InputSimulator work with Unity's New Input System?

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

What prerequisites are required before scaffolding E2E 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 without proper infrastructure?

Tests that rely on fixed delays and direct state manipulation break when timing or scenes change. The generated AsyncAssert waits for conditions instead of time, and the fixture handles scene loading and cleanup guarantees.