Feature
Catch bugs before your testers do.
Your Blueprint functional tests and C++ automation tests run after every build, in the cloud. A failing test fails the build, so a bug gets caught the day it's written, not the day someone plays it.
Blueprint and C++
Functional tests placed in your maps and C++ tests registered with Unreal's automation framework both run. No extra test framework to set up.
A failing test fails the build
If a test fails, the build fails, right there on the pull request. Nobody downloads a broken build by mistake.
A report you can actually read
Every test, its result, how long it took and what it logged, in a report on the build. Expand a test to see exactly where it went wrong.
Run just what matters
A filter picks which tests run, from everything in your project down to a single category.
Set it up
- Turn on Run tests in a preset
- Adjust the test filter if you need to
- Push, and read the report on the build
Questions
Do tests run on Shipping builds?
No. Unreal Engine compiles automation tests out of Shipping builds, so tests run on non-Shipping builds.
What makes a test work in CI?
Tests run headless on a cloud machine, so avoid tests that need a display, user input or online services you haven't mocked.
Do I still get a build if a test fails?
The packaged build may still be there, but the build is marked failed, so nobody mistakes it for a good one.
Get started · No contract
Start automating Unreal Engine today.
Set up your first build pipeline in minutes.