CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/unreal-automation-system

Author and run Unreal Engine's Automation Test Framework - Epic's C++ test framework for UE 4.x / 5.x, documented at dev.epicgames.com/documentation/en-us/unreal-engine. Covers the five test categories Epic defines (Unit / Feature / Smoke / Content Stress / Screenshot Comparison), the IMPLEMENT_SIMPLE_AUTOMATION_TEST and IMPLEMENT_COMPLEX_AUTOMATION_TEST macros, the BDD-style Automation Spec API (DEFINE_SPEC / BEGIN_DEFINE_SPEC / Describe / It / BeforeEach / LatentIt / xIt), latent commands (ADD_LATENT_AUTOMATION_COMMAND), the Automation Driver for UI input simulation (IAutomationDriverModule::Get().CreateDriver(), By::Id / By::Path locators), running via Session Frontend (Window > Test Automation) and command line (-ExecCmds="Automation RunTests …"), and CI integration. Use when the unit under test is C++ Unreal code that needs the UE runtime, editor, or UMG UI surface.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with a clear sequenced workflow, explicit CI validation, and clean progressive disclosure into two reference files. The main improvement opportunities are deduplicating repeated doc URLs and surfacing a minimal inline authoring snippet.

Suggestions

In the anti-patterns table, cite each Epic doc URL once (e.g. in a table footnote or the References section) instead of repeating it on most rows, to trim redundant tokens.

Include one small inline C++ snippet (e.g. a minimal IMPLEMENT_SIMPLE_AUTOMATION_TEST + RunTest) so the body is copy-paste actionable for authoring without requiring a jump to the reference.

Consider consolidating the repeated references/authoring-macros-and-apis.md and references/running-and-reporting.md links into a single References pointer to reduce link repetition.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence without explaining basic concepts, but the anti-patterns table restates the same Epic documentation URL on nearly every row, which is trimmable redundancy.

4 / 5

Actionability

Provides a concrete executable -ExecCmds bash command, tables of specific macros and APIs, and a worked example with real test names and flags; the actual authoring C++ is deferred to references rather than given inline, leaving a minor gap for copy-paste authoring.

4 / 5

Workflow Clarity

A clear six-step 'How to use' sequence and a five-step worked example include an explicit validation checkpoint — parsing the -ReportOutputPath JSON and treating any "state": "Fail" as a failed build — for this batch CI operation.

5 / 5

Progressive Disclosure

The body declares itself 'the decision surface' and splits full authoring code and running/reporting into two real, one-level-deep reference files (verified present in ./references/), with well-signaled navigation throughout.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, complete, and distinctive description that names concrete capabilities and gives an explicit use-when clause. Its only weakness is a slight lean on technical macro/API jargon over natural user phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — authoring via IMPLEMENT_SIMPLE_AUTOMATION_TEST/IMPLEMENT_COMPLEX_AUTOMATION_TEST, the BDD Spec API (DEFINE_SPEC/Describe/It), latent commands, the Automation Driver, running via Session Frontend and command line, and CI integration — giving comprehensive coverage of the framework's capabilities.

5 / 5

Completeness

Clearly answers 'what' (author and run the framework across its categories, macros, Spec API, Driver, running, and CI) and explicitly answers 'when' with the concrete trigger phrase 'Use when the unit under test is C++ Unreal code that needs the UE runtime, editor, or UMG UI surface.'

5 / 5

Trigger Term Quality

Good coverage of natural terms ('Unreal Engine', 'Automation Test Framework', 'C++', 'UE 4.x / 5.x', 'UMG UI') with synonyms, but several listed identifiers (e.g. IMPLEMENT_SIMPLE_AUTOMATION_TEST, IAutomationDriverModule::Get().CreateDriver()) are technical jargon rather than phrases a user would naturally say, and no file extensions appear.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Unreal Engine C++ automation testing) with distinct, specific triggers tied to the UE runtime/editor/UMG, leaving minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents