ue-automation-and-testing

Use IMPLEMENT_SIMPLE_AUTOMATION_TEST with a dotted path name and EAutomationTestFlags combining one context flag and one filter flag. Implement RunTest using FAutomationTestBase assertions like TestTrue and TestEqual, and place the file in your module's Private/Tests directory.

Run UnrealEditor-Cmd.exe with -ExecCmds="Automation RunTest <dotted.prefix>;Quit" plus -unattended, -nopause, and -nullrhi for headless CI. Add -ReportExportPath to write JSON and HTML results, and check the exit code for pass/fail.

Simple and complex automation tests run in the editor or commandlet for unit and content tests. Specs (DEFINE_SPEC) provide BDD-style Describe/It structure with latent async support. Low-level tests use Catch2 in a thin standalone executable for pure logic with no UObject or world dependency.

The test is missing either a context flag or a filter flag in EAutomationTestFlags. Every test must OR together at least one context (EditorContext, ClientContext, etc.) and one filter (SmokeFilter, EngineFilter, ProductFilter, etc.) to be discovered.

In specs, use LatentIt or LatentBeforeEach with an FDoneDelegate that you execute when the async work completes. In simple automation tests, queue work with ADD_LATENT_AUTOMATION_COMMAND, whose Update method returns false until the operation finishes.

Use AFunctionalTest when the test needs a running world, actors, physics, or AI, such as gameplay integration scenarios. It runs as an actor placed in a dedicated test map, requires calling FinishTest, and uses its own AssertTrue/AssertIsValid assertion family.