menu
what we do
who we work withcase studieshow it workswho we areblog insightsfaq contact
get in touch
all case studies

case study 17 / 17

next →

AI + AUTOMATED TESTING · UNITY · CI · IOS SIMULATOR

AURA

AI Testing Agent for Unity Projects

AURA is our own product: an AI agent that tests Unity games and apps the way a person would. You write a test case in plain English; AURA plays the build – tapping, typing, swiping, listening – and comes back with a verdict and the evidence behind it. We designed and built it in-house, and it ships as standard on every Unity Developers client project.

Services
Software Testing, AI Agent Development, Developer Tooling
Platforms
Unity Editor, headless CI, iOS Simulator
Industry
Software Testing & QA
See also
Software testing
AURA’s launch film: one instruction, a fleet of agents, verdicts coming home.

The challenge

Every Unity project reaches the point where someone has to sit down and check the thing actually works – on every screen, every device shape and every build. Test automation has always meant scripts: brittle selector chains that break when a button moves, and stay green while the product quietly breaks.

Our projects don't look much alike – AR and VR experiences, cross-platform apps, WebGL configurators, training and simulation tools, and games. We wanted one tester that works on anything Unity can build, checks what a user actually sees and hears, and never reports a pass it can't prove.

A real run, replayed

Plain English in. Proof out.

AURA’s notes and actions from a real run on Owee, our own app, shown on real Owee screens: the test case it was given, what the agent wrote before each step and each tap on the control it aimed at, up to the last onboarding page.

onboarding_value_prop.aura.mdAURA test case 
id: onboarding_value_prop
title: Parent can page through the value-proposition onboarding screens
story: As a parent, I can preview what Owee offers before signing up
tags: [onboarding, smoke]
---
1. Wait for loading to finish and the Welcome screen to appear.
2. Tap the Get Started call-to-action.
3. Read the first onboarding page; note its heading.
4. Advance to the next page (Next button or swipe).
5. Read the second onboarding page; confirm it is different from the first.
6. Continue advancing until an account-creation screen or a final Get Started appears.
7. Verify the sequence completed without errors.
aura · run console

▶ aura run onboarding_value_prop.aura.md · Owee

  1. 01

    wait 15 s

  2. 02

    The Welcome screen has loaded. Now I’ll tap Get Started.

    tap Get Started call-to-action button

  3. 03

    First onboarding page: “You Control Learning Subjects”. Let me scroll down to see if there’s a Next button, or check hierarchy.

    inspect_hierarchy

  4. 04

    There’s a Back/Next at the bottom (offscreen below likely). Let me screenshot to see if visible, then tap Next.

    tap Next button to advance onboarding

  5. 05

    The carousel animation continued but the header/page is still the same (“You Control Learning Subjects”). Let me tap Next again to actually advance.

    tap Next button to advance to next onboarding page

  6. 06

    Second page confirmed: “Watch Your Child’s Knowledge Base Grow!” - distinct heading and imagery.

    tap Next button to advance to third onboarding page

  7. 07

    Third page: “Meet Owee - Your Child’s Wise Companion”. This shows Next, not “Get Started” yet.

    tap Next button to proceed further

  8. 08

    This looks like a transitional/loading screen. Let me wait and check further.

    wait 3 s

  9. 09

    The onboarding advanced to a “Welcome Back!” sign-in screen rather than the expected “CREATE YOUR PARENT ACCOUNT” screen. Let me check the “Create Account” link…

    tap Create Account link

  10. 10

    The “CREATE YOUR PARENT ACCOUNT” screen appeared successfully, confirming the sequence completed as expected. Let me check logs for any errors.

    read_logs severity error, last 30

    (no matching log entries)

  11. 11

    No errors found in the logs. The full sequence completed successfully.

    report_result passed

✓ passed

“…tapping ‘Create Account’ successfully reached the ‘CREATE YOUR PARENT ACCOUNT’ screen, matching the expected terminal screen in the success criteria. No errors were found in the logs…”

Our approach

AURA is a Unity package you add to an existing project. Test cases are short files written in natural language and grouped under user stories. On every run a vision model looks at the screen, decides what to do and acts – tapping, typing into the real input fields, swiping, pinching, tilting, rotating the device or sending the app to the background – then judges the result from screenshots, the UI hierarchy, exact layout measurements, performance figures and the audio that played.

It runs interactively in the editor or headless on CI, where test cases appear as Unity Test Framework PlayMode tests, and it can run a suite across several Unity instances in parallel. On an iOS Simulator build the screenshot comes from the OS, so permission dialogs and keyboards are in the picture and AURA can tap them. A local web app ties it together: write test cases in conversation, launch runs behind a cost estimate, watch progress live and review the history.

How a run works

Evidence behind every verdict.

Every AURA run goes the same way. In AURA’s own words:

  1. Describe

    Write the user story in plain English, in a small file that lives with your code.

  2. Run

    AURA runs it on the real build – seeing, deciding and acting like a real user.

  3. Evidence

    Every step is captured as it happens: screenshots, logs, measurements, audio.

  4. Verdict

    A pass you can trust, or a failure with the proof attached – tracked across versions.

The results

AURA is live at aura.unitydevelopers.co.uk. It ships as standard on every Unity Developers client project, new and existing, and a small number of external teams can bring it to Unity projects we didn't build.

We proved it on Owee, our own kids' learning app, by pointing it at the app's full suite of 291 test cases overnight. The run found real defects in the app – and some in AURA itself, each fixed with a regression test that fails if the fix is ever undone. Every run ends in a branded HTML report grouped by user story, with screenshots, findings and the full step timeline.

Technical highlights

  • Plain-English test cases

    a short .aura.md file is the whole test, with no code and no selectors

  • Full device simulation

    tap, rapid tap, type, drag, drag and drop, swipe, long press, scroll, pinch, tilt, shake, rotate, back button, deep links and background/resume

  • Evidence behind every verdict

    screenshots, UI state, layout measurements, performance, visual regression and which voice-over, music or sound effect played

  • Layout and brand audits

    safe areas, notches, touch targets, text size, contrast, overflow and untranslated strings across simulated devices, judged against a brand book

  • Catches what nobody wrote a test for

    unhandled exceptions, main-thread freezes and screens that stop responding

  • Built for the pipeline

    headless PlayMode tests on CI, parallel runs, and multiplayer sessions played by several editors at once with cross-device sync checked

Have a project in mind, or want to explore what’s possible? Talk to us.

get in touchhello@unitydevelopers.co.uk

Next case study

Owee

Kids Learning Quiz App

next →