Skip to Content
AwakenQA runs

QA runs

A QA run is one execution of a QA agent on a project’s task. Awaken does not run QA itself. It shows the status of the QA runs that the project’s daemon already records, in two places.

What a QA run is

When you work on a game in GameGen, a task moves through stages. When a task reaches Review, a QA agent runs against it. For an Unreal game the QA agent is unreal-simulation. The daemon records each run as an execution with an id, an agent type, a status and the task it belongs to.

Awaken reads those execution records. The daemon has no state dedicated to QA verdicts.

What Awaken shows is the status of the execution, such as running or completed. It is not a parsed test report. To see what a run did, open the run in GameGen.

Where QA runs appear

PlaceWhat it listsDetail
GameGen, Awaken (NPCs & QA), QA tabThe recent runs of unreal-simulation for the selected project.You can open each run and its task.
Awaken app, QA strip in the overlay panelThe five most recent executions whose agent type names QA, for example qa-tester.Status only.

The two lists are built differently, so they can differ. GameGen lists runs of one named agent. The Awaken app matches any agent whose type names QA.

See QA runs in GameGen

Open the view

In GameGen, choose Awaken in the sidebar. The Awaken (NPCs & QA) view opens on the QA tab.

Read the list

QA runs lists the recent runs. Choose Refresh to read them again now.

Open a run

Choose Open run on a row, or Open task #N to open its task.

With no runs, the tab reads No QA runs yet. QA runs start when a task reaches Review. See GameGen view.

See QA runs in the Awaken app

Connect to the project’s daemon

Open the project in Awaken. The strip needs a connected daemon; it is not drawn when Awaken reads the game file directly.

Find the QA strip

In the overlay panel, look for the label QA. Each run is one entry with a coloured dot:

#42 completed (task 7)

That is the execution id, the status and the task. An execution with no task shows only the id and the status.

See more

Hover over an entry to see the agent type and, for a failed run, its error message.

The strip is not drawn when no daemon is connected or when the project has no QA executions.

Not yet verified

A populated QA strip has not been verified on screen with a real project. Its logic is covered by the app’s tests.

What Awaken does not show

  • Test names, pass and fail counts, or logs.
  • Unreal automation results. In the Floppy Bird tutorial, node Scripts/ue.mjs test writes those to the project’s Saved/Automation/ folder.
  • Recorded play runs. Those are reviewed in GameGen’s Lou view; the QA tab links to it with Open Lou.

Next steps

Last updated on