- Home
- Skills
- Game Development
- automated game qa test case architect
Works with the AI Agents you already use
automated game qa test case architect
Architect structured, risk-based game QA test cases and automation plans for Unity, Unreal, and Godot.
$14.99
automated game qa test case architect
Example session with this skill installed
Create a test suite for a new 'Fast Travel' feature in a Unity open-world game. Include save/load persistence, UI interaction, and edge cases like traveling while taking damage.
- Read your context and instructions
- Compiled the automated game qa
I have architected a risk-based test suite for the Fast Travel feature. This suite covers functional happy paths, boundary conditions, and persistence requirements.
Fast Travel Test Suite
| Test ID | Title | Priority | Type | Preconditions | Expected Result | Automation |
|---|---|---|---|---|---|---|
| FT-001 | Successful Travel to Discovered Node | Critical | Functional | Player at Node A; Node B is 'Discovered' | Player teleports to Node B; Loading screen clears < 2s. | Yes |
| FT-002 | Travel Attempt to Undiscovered Node | High | Negative | Player at Node A; Node C is 'Undiscovered' | Node C is unselectable in UI; 'Travel' button disabled. | Yes |
| FT-003 | Interruption: Damage During Warmup | High | Boundary | Player initiates travel; 3s warmup timer starts | Taking damage cancels warmup; UI notification appears. | Partial (Hooks needed) |
| FT-004 | Persistence After Save/Load | Medium | Regression | Player travels to Node B; Game auto-saves | Upon reload, Player remains at Node B coordinates. | Yes |
| FT-005 | Low Mana/Currency Requirement | Medium | Functional | Travel cost > Current Player Balance | UI shows 'Insufficient Funds'; Travel action fails. | Yes |
Automation Strategy
- Setup: Use a seeded save state with specific nodes unlocked.
- Assertions: Monitor
PlayerController.PositionvsTargetNode.Positionpost-load. - Cleanup: Reset player coordinates and clear temporary travel flags in the
TearDownphase.
Next steps
- Review the requirement for "travel while falling" to determine if it should be a blocked state.
- Define the specific Unity
InputSystemactions for triggering the map UI. - Confirm if fast travel cost scales with distance for boundary testing.
Connects securely to your tools. The creator never sees your data.
About this skill
Writing effective test cases for games requires more than just listing features. Vague steps and manual-only plans lead to missed regressions, broken save files, and untestable multiplayer logic. This skill converts requirements and design docs into structured, risk-based QA architectures ready for both manual testers and automation engineers.
What it does
- Requirement Traceability maps every test case back to specific user stories or design rules to ensure full coverage.
- Risk Assessment prioritizes testing based on player impact, progression blockers, and data loss potential.
- Multi-domain Coverage architects tests for gameplay mechanics, UI navigation, save/load persistence, and network replication.
- Automation Strategy identifies high-value automation candidates and defines stable setup, teardown, and assertion logic.
- Engine-Specific Guidance tailors test logic to the lifecycles and input systems of Unity, Unreal Engine, and Godot.
How it works
- Analyze Inputs by parsing your design docs, build notes, and engine requirements.
- Assess Risks to categorize features from Critical to Low priority based on player impact.
- Build Test Suites organized by type, including Smoke, Regression, Integration, and Performance.
- Define Architecture by outlining the necessary test data, environment hooks, and automation feasibility.
Frameworks & tools
Support for Unity (Input System, Scene lifecycle), Unreal Engine (Gameplay Framework, Blueprints/C++), Godot (Scene Tree, Signals), and custom engines with established automation hooks.
Why this beats prompting it yourself
Generic prompts often result in "verify it works" steps that manual testers can't follow and scripts can't execute. This skill enforces atomic steps, deterministic setup, and measurable expected results while accounting for engine-specific state transitions.
Use cases
- Drafting a Smoke Test suite for a new multiplayer hero ability.
- Creating a regression plan for a complex inventory and save/load system.
- Auditing a feature spec to identify missing edge cases and boundary conditions.
- Mapping out automation hooks for a UI-heavy menu system in Unity or Unreal.
Known limitations
Requires detailed design specs or feature descriptions to avoid assumptions. Does not execute tests or provide runtime results without external execution evidence.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.
Requires detailed design specs to avoid assumptions. Does not execute tests or provide runtime results. Engine-specific code is limited to provided stack versions.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago