Skill

unreal-testing

Guides Unreal Engine test strategies: deterministic C++ logic tests, automation for subsystems/editor, targeted integration over brittle map-level tests. Use when adding tests or addressing weak coverage/replication bugs.

testing

npx claudepluginhub mrcalderon3d/everything-game-dev-code

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Choose effective Unreal automation and integration test layers without over-relying on brittle map-level tests.

SKILL.md

Similar Skills

using-git-worktrees

169.2k

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

subagent-driven-development

169.2k

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

3 files

superpowers

dispatching-parallel-agents

169.2k

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

Stats

Stars20

Forks3

Last CommitMar 28, 2026

Actions

View Source View Plugin View on GitHub View README

Unreal Testing

Purpose

Choose effective Unreal automation and integration test layers without over-relying on brittle map-level tests.

Use When

adding Unreal tests
automation coverage is weak
replication and asset integration bugs are recurring

Inputs

feature risk profile
automation support
map dependencies
CI capacity

Process

use deterministic tests for C++ logic where possible
use automation tests for subsystem and editor validation
reserve heavier integration tests for real risk areas
stabilize map and asset assumptions
label gating versus informational test suites clearly

Outputs

Unreal test strategy
automation opportunities
fixture cautions
CI notes

Quality Bar

respects Unreal framework ownership, packaging, and content pipeline realities
keeps C++, Blueprints, plugins, and content boundaries intentional
makes replication, map setup, and packaging risk explicit

Common Failure Modes

Blueprint graph sprawl hiding ownership
using Tick where event-driven logic is clearer
packaging or plugin state changing without documentation

Related Agents

unreal-reviewer
qa-lead
build-engineer

Related Commands

unreal-review
verify
qa-plan

Notes

Keep this skill aligned with the relevant rules layer and current project documentation.
If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.