Builds, tests and jobs

Run builds and automation tests, console commands and long jobs, and check the scene.

What it’s for

Ask your assistant to do the engine-level jobs around your project: recompile with Unreal Build Tool, run automation tests and report how many passed, run console commands, and keep track of long-running work.

It can also look at the open level without changing anything. When your assistant only needs to look, for example to count the actors in a level, find every instance of a class, read the viewport camera, or list one object’s properties, it uses this area so nothing in your scene is touched.

Console commands that apply to the whole project or engine run here. Commands aimed at the editor world or viewport go through Editor and Play-In-Editor.

Slow work never blocks your assistant. Builds, test runs and folder dumps keep running in the background, and your assistant checks on them, lists them or cancels them as needed.

Things you can ask

Run automation tests and get the result

The tests run in the background and you get the pass and fail counts when they finish.

You: Run the PinWright automation tests and tell me if anything failed.

All 214 tests passed, with 0 failures.

Set an engine console variable

A project-wide setting changes for the running editor.

You: Bump the texture streaming pool size to 2048.

Set r.Streaming.PoolSize to 2048.

Find actors in the level without touching them

You get a count of what is in the level so you can plan a change.

You: How many StaticMeshActors are in the current level?

There are 12 StaticMeshActors in the level, including Floor and Wall_01.