test-format-schema

Enforce standardized naming, guard macros, and file structure for UE5 automation tests.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill test-format-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-format-schema
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/test-format-schema
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill test-format-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests in UE5 automation often lack a standard naming, guard macros, and directory structure, leading to inconsistent layouts and harder maintenance. This schema defines the required naming patterns, guard macro usage, and test folder conventions to keep projects aligned.

Core Features & Use Cases

  • Standardized test naming: Resort.<System>.<Feature>.<TestName> with proper F-prefix for class names.
  • Guard macros and file structure guidance: Ensures code is wrapped with WITH_DEV_AUTOMATION_TESTS and lives under the expected Source/Tests layout.
  • Cross-project consistency: Provides a reusable blueprint for UE5 automation tests across multiple UE projects.

Quick Start

Create a new UE5 automation test by applying the standard naming, guard macros, and folder structure defined in this schema.

Frequently Asked Questions about test-format-schema

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

FAQPage Schema
How do I structure UE5 automation tests to maintain consistent naming and file layout?

UE5 automation tests should follow a standardized naming pattern like Resort.<System>.<Feature>.<TestName>, use proper F-prefixes for class names, and reside under the expected Source/Tests directory layout to ensure consistent maintenance.

What is the purpose of WITH_DEV_AUTOMATION_TESTS guard macros in UE5 test files?

WITH_DEV_AUTOMATION_TESTS guard macros wrap your UE5 automation test code to conditionally compile tests only when automation testing is enabled, preventing unnecessary code execution in production builds.

How do I apply a standardized naming convention for UE5 automation test classes?

Apply the Resort.<System>.<Feature>.<TestName> naming pattern and ensure your test class names use the proper F-prefix, keeping your UE5 automation test structure aligned across multiple projects.

Can I use this UE5 test format schema across multiple different Unreal Engine projects?

Yes, this schema provides a reusable blueprint for UE5 automation tests that enforces standardized naming, guard macro usage, and folder conventions to maintain cross-project consistency.

Why do my UE5 automation tests lack a standard directory structure?

UE5 automation tests often lack standard directory structure because projects do not enforce a specific Source/Tests layout, leading to inconsistent file placements and harder maintenance.

What are the limitations of enforcing a schema for UE5 automation test formats?

The schema requires strict adherence to the documented naming patterns, guard macro usage, and folder conventions defined in the SKILL.md, meaning existing tests must be refactored to match the Resort.<System>.<Feature>.<TestName> standard.