ZagalaSpec 1.0.0#
The first release of ZagalaSpec: write what your game should do in plain Given / When / Then sentences, and run those sentences as automation tests in Unreal Engine.
Features as readable sentences#
A Feature asset holds scenarios written the way your team already talks about the game. Designers, producers and QA write them; the sentence is the test, and the test is the status report. Write a feature
Import and export#
Import Gherkin, SpecFlow, Robot Framework, Gauge and FitNesse files, or the ZagalaSpec format, straight from the Content Browser. Export features back to the same formats. Export features
Steps in Blueprint or C++#
Connect each sentence to gameplay once, then reuse it across scenarios. Steps, matching patterns, capture groups and shared data work the same whether you build them in Blueprint or C++. Configure steps
Run anywhere Unreal runs tests#
Run features in the Session Frontend, on your build machine, or headless in CI, through the standard Unreal Automation Framework. Run features
Results you can read#
A green scenario means every step passed. A red one shows the first failing step and the reason, so the report tells you what broke. Read results
Filter scenarios by environment#
Tag a scenario to run only in the editor or in specific build configurations, or to skip it there, with optional AND/OR rules and your own filters. Filter scenarios
Layers when you need them#
Use the full test case, domain language, protocol driver and system layering as a feature grows, or keep everything in one Blueprint step while it is small. The four layers
Worked examples included#
Five ready-to-run examples: BlueprintFeature (Blueprint only), Counter and Inventory (in-memory C++), and Hoverboard and Checkpoint (physics world, multiple actors). Start with the tutorials
Platforms#
Windows, Linux and macOS, in Blueprint-only and C++ projects, on Unreal Engine 5.6 to 5.8. ZagalaSpec is a development tool and is never included in Shipping builds. Requirements