MakeGameWithAI
中文
Menu

AltTester

Object-level Unity and Unreal UI automation, with a Pro CLI and local MCP for agent-assisted regression work.

Evidence statusPublic-evidence reviewMedium confidenceLast checked Sep 16, 2026By MakeGameWithAI
Visit official websiteSee the evidenceTesting & Optimization

PRODUCT OVERVIEW

What AltTester is—and how it works.

AltTester is runtime UI and end-to-end test infrastructure for Unity and Unreal—not an AI service that discovers every game bug. A team adds the matching SDK to a development or test build, runs AltTester Desktop as the connection server, then uses the Inspector, Recorder, C#, Python, Java or Robot Framework drivers to find objects, inspect state, perform input and assert outcomes.

That object-level path can be more stable and informative than screen coordinates alone because tests can address the scene hierarchy, components and properties. It also creates an engineering dependency: the team needs source access, a separate instrumented build, compatible SDK/Desktop/driver versions and a maintained connection path for local, mobile, WebGL or device-cloud execution.

Pro adds the CLI, a local stdio MCP server and Robot/Helper AI Skills. An agent can inspect live hierarchy, operate the game, draft a reviewed plan, generate Robot tests and diagnose failures. Deterministic suites should still own repeated release checks, while people retain exploratory testing, visual acceptance and release judgment.

HOW YOU USE IT

Start with the 30-day Pro trial, or request Lite if the broad trailing-twelve-month financial threshold applies. Install AltTester Desktop, add the matching Unity or Unreal SDK to a dedicated development/test build, start the server, then connect one of the supported drivers. CLI, MCP and AI Skills require Pro and an external AI client; mobile and cloud devices need routing or port forwarding.

Runtime object access

Find scene objects with selectors, inspect component properties, call methods, load scenes and control game speed against an instrumented build.

O01O07O14

Input and repeatable regression

Drive mouse, keyboard, touch and joystick interactions from C#, Python, Java or Robot Framework, then run locally, in CI or through supported device-cloud routes.

O01O09O15

Inspector and Recorder

Explore the hierarchy and turn recorded actions into a script starting point; stable selectors, assertions and state control remain the test author's responsibility.

O01U01U04

Pro agent entry points

Use the CLI directly or expose it through local stdio MCP. Official client configurations and two Skills support inspection, planning, generation, execution and debugging.

O06O20O21

INTERFACE & EXAMPLES

See how it works

3 images
AltTester's official example places the running game, object hierarchy, properties, and recorded steps in one desktop window.Open larger
Interface

AltTester's official example places the running game, object hierarchy, properties, and recorded steps in one desktop window.

Official documentation image showing Desktop v2.2.2; retrieved September 2026.Source: AltTester Documentation
AltTester's official example places the running game, object hierarchy, properties, and recorded steps in one desktop window.
Source: AltTester Documentation
REVIEW SCOPE

This page evaluates object-level functional UI and end-to-end regression for game development builds. It does not evaluate anti-cheat, load testing, visual-quality scoring, game balance, fun, accessibility conformance, autonomous unknown-bug discovery or production security of an instrumented player build.

Beginner friendlinessSome basics needed
Inspector, Recorder, a desktop GUI, examples and object-level selectors make a first stable flow more approachable than building an engine test harness from scratch or relying on raw screen coordinates. The developer still needs an instrumented test build, compatible Desktop and SDK versions, a server-app-driver connection, selectors, waits, assertions, repeatable state and enough Unity or Unreal knowledge to diagnose failures.
Agent integrationEasy to integrate
Pro documents a local stdio MCP server, a CLI, Robot and Helper skills, and configurations for Claude Desktop, Claude Code, VS Code or Copilot, Cursor, JetBrains and Windsurf. Those interfaces can expose live hierarchy and properties, input actions, scenes, screenshots and deterministic Robot execution to an external orchestrator; the four supported test-driver languages remain an additional scripted route.
Scope, integration requirements and sourcesChecked

Beginner scope: A developer with basic Unity or Unreal project and testing concepts automates one deterministic login, menu, purchase-sandbox or level-transition flow in a build they control; not a complete beginner asking the product to discover every bug automatically.

Agent scope: Let Codex, Claude Code or another external development agent inspect a connected test build, draft a bounded test plan, generate or repair Robot tests and run a deterministic suite before a human reviews failures and release impact.

Confidence: learning Medium · Agent High

Access
MCP, CLI and both AI skills require Pro and a compatible AltTester Desktop, while the target game must include the matching Unity or Unreal SDK and connect through the correct local or forwarded route. Start the local server with alttester mcp and configure a supported stdio client; Codex has no vendor-specific setup page, so its compatibility is a standards-based inference rather than certified support.
Billing
The 30-day Pro trial is EUR 0. Approved Lite is EUR 0 but GUI-only with one connection and no CLI or MCP. One-engine Pro is EUR 900 per seat yearly or EUR 109 monthly, includes two concurrent application-and-driver connections, and excludes extra connections or MCP instances, the second engine, device clouds, CI hosts and the external model or agent subscription.
Getting results
Instrument a non-production build, connect the correct SDK and Desktop versions, let the agent inspect the hierarchy and propose a narrow plan, require a human to approve selectors and assertions, generate Robot tests, then run them deterministically in CI and route screenshots, logs and unstable failures back to a human. Keep release builds and credentials outside the automation surface.
Limitations
Easy describes a documented interface, not autonomous game QA or proven cost savings. Lite has no MCP or CLI, Unreal AI-extension support is limited, ports and mobile routing still need setup, protected folders can block local MCP, Codex is not named in the official client list, and current independent evidence does not establish long-run MCP reliability, maintenance savings or cost per accepted regression check.

These are independent editorial judgments, not an overall score or a claim of hands-on agent integration testing.

KEY FINDINGS

What the evidence supports—and what it does not.

01
Official factHigh confidence

Object-level access is the real product

The SDK exposes hierarchy, components and properties to external drivers. That can make failures more actionable than coordinate-only scripts, but it requires source integration and a protected test build.

O01O07O08O14
02
Editorial inferenceMedium confidence

The beginner path still needs engineering basics

GUI, Recorder, examples and the Robot Skill lower the start, but independent records show that server topology, ports, iOS, input systems, waits, state and diagnostics remain real learning work.

O01O06U01U04U07
03
Official factHigh confidence

Agent composability is documented, not magic

Pro exposes a local MCP and broad CLI, with official client configurations and review-before-code guidance. It does not remove instrumentation, permissions, device routing or human acceptance; Unreal support is explicitly limited.

O06O20O21
04
User reportsMedium confidence

Automation complements exploration

Academic and community cases favor stable known flows. Random outcomes, unknown issues and changing complex mechanics still need repeats, targeted tools and people who can notice unexpected behavior.

U02U03U05U06
05
Editorial inferenceMedium confidence

License and telemetry boundaries matter

Lite Unity uses GPL-3.0 while Pro offers a non-GPL route. Logs and CLI snapshots can stay local, but license checks and anonymized product analytics leave the machine, and the visible privacy policy is older than the current telemetry terms.

O02O04O05O06O10O11

EDITORIAL VERDICT

Our take

Medium confidence

AltTester is a credible option for teams that own a Unity or Unreal project and need repeatable checks over stable, expensive-to-retest flows. Its strongest current differentiator is the combination of object-level runtime access and a documented Pro CLI/MCP path. The trade-off is not hidden: reliable automation still needs instrumentation, test design, state setup, selectors, assertions, failure triage and maintenance. Start with one stable flow rather than promising broad autonomous QA.

Conclusion scopeMedium confidence. Current product, interfaces, prices, licenses and known limitations are well documented; independent work supports practical Unity automation and a controlled agent architecture, but current MCP longevity, Unreal AI coverage, maintenance savings and cost per accepted regression check are not established.

BETTER FIT

Worth auditioning when

  • Unity or Unreal teams that can create a dedicated instrumented development or test build.
  • Stable, repeated flows such as login, menus, shop, level entry and state changes with clear assertions.
  • Teams comfortable maintaining selectors, fixtures, waits, reports and CI around engine changes.
  • Pro users who want Claude Code, Cursor, Copilot or another MCP client to inspect live game state and assist with Robot tests.

POORER FIT

Do not depend on it yet when

  • Testing a third-party release binary when you cannot add the SDK or produce a test build.
  • Expecting one natural-language prompt to discover every gameplay, visual, balance and device-specific bug.
  • A highly volatile project with no budget to maintain state, selectors, assertions and diagnostics.
  • A Lite user expecting free CLI, MCP, unattended agents or a non-GPL Unity distribution path.

WORKFLOW FIT

Where it fits in a production workflow.

01

Isolate the test build

Create a dedicated development or test configuration, pin compatible Desktop/SDK/driver versions and keep instrumentation out of the player release.

GuardrailTreat the SDK connection as privileged test infrastructure, not a feature to ship.
02

Choose one stable expensive flow

Begin with login, menu navigation, shop state or level entry where inputs, prerequisites and expected results are already understood.

GuardrailAvoid a first test that depends on physics timing, random combat or frequently changing UI.
03

Make state and assertions explicit

Use stable selectors, reset accounts or saves, wait for observable state and assert the business outcome—not only that a click command returned.

GuardrailA test without a meaningful assertion can repeat activity without detecting a regression.
04

Let the agent draft, then run deterministically

Use Pro MCP or Skills to inspect the game and propose a plan. Review it before generation, commit the Robot suite and run releases without an LLM in the critical path when practical.

GuardrailSeparate product failures, test-maintenance failures and infrastructure failures in every report.

RECOMMENDED WORKFLOW

Use this tool inside a complete production workflow.

Start from a testable brief, then move through prototyping, assets, audio, testing, and release with an explicit handoff and human check at every step.

Open the complete method

SHORTEST RESPONSIBLE PATH

Automate one five-minute regression before expanding coverage

This is a low-risk starting workflow synthesized from the evidence.

  1. 01

    Use the 30-day Pro trial on a branch and create a dedicated instrumented development build; never begin with the release binary.

  2. 02

    Run Desktop Server and connect the build plus one driver locally before adding mobile, CI or an AI client.

  3. 03

    Select one stable flow with a clear start state, three to eight actions and an observable end assertion.

  4. 04

    Inspect the hierarchy, choose stable selectors and wrap screens or flows so object names are not scattered through every test.

  5. 05

    Run the test repeatedly, classify every failure and record authoring, maintenance and triage time alongside manual replay time.

  6. 06

    Only then enable MCP or a Skill for plan and code assistance; expand if accepted regression cost and false-failure rate are useful.

PRICING & RIGHTS

EUR 900 buys one Pro seat and two connections—not a promised number of stable tests

Pricing and terms last checked: Sep 16, 2026

  • The Pro trial lasts 30 days, costs EUR 0 and does not require a credit card. It is an evaluation path, not a permanent production tier.
  • Lite costs EUR 0 only after request and approval. Eligibility uses a broad trailing-twelve-month total-finances ceiling of EUR 500,000; service providers may need to count a client's finances. Lite has one connection, GUI only, no CLI or MCP, and the Unity SDK uses GPL-3.0.
  • Pro annual billing is EUR 75 per seat per month, charged as EUR 900 per year plus VAT. It includes one selected engine by default, a non-GPL SDK, two simultaneous app/driver connections, Recorder, CLI, MCP, two AI Skills, CI/CD and WSS.
  • Pro monthly billing is EUR 109 per seat per month plus VAT. Twelve consecutive monthly payments total EUR 1,308, which is EUR 408 more than annual billing.
  • The Unity plus Unreal bundle, more connections or CLI/MCP instances, Nintendo support, priority support, training, services and custom engines require add-ons without public prices.
  • An external AI client or model subscription, implementation, CI machines, device clouds, test data, maintenance, failure triage and release review are not included in the seat price.
COST TO OUTPUT

What the public price actually unlocks

Arithmetic from the current September 16, 2026 list prices. Connection-month figures allocate license capacity only; they do not use an assumed test count or success rate.

O02O03O04O06O18O19
30-day Pro trialEUR 0 → temporary Pro evaluation

Enough to validate one real instrumented flow without a card. Do not infer perpetual rights or every paid add-on from the trial label.

Lite if approvedEUR 0 → 1 GUI connection, no MCP/CLI

The cash fee is zero only while broad tier eligibility is maintained. Unity's GPL-3.0 route and the absence of agent interfaces materially change what the user receives.

One annual Pro seatEUR 900/year → 1 engine + 2 concurrent connections

Nominally EUR 37.50 per included connection-month, plus VAT. The seat also unlocks the non-GPL SDK, CLI, MCP, Skills, Recorder and CI path.

Twelve monthly Pro paymentsEUR 1,308/year equivalent → same core plan

Nominally EUR 54.50 per included connection-month. The EUR 408 flexibility premium is 31.19% of the twelve-month monthly total.

Accepted regression checkUnknown

No public average covers authoring, maintenance, false failures, device infrastructure and stable accepted runs. Divide total team cost by checks that reliably protect a release only after measuring your own flow.

Actual accepted-regression cost = license and add-ons, AI client, instrumented-build work, fixtures and test data, CI/devices, authoring, maintenance, triage and human release review divided by stable checks that catch or prevent relevant regressions. Keep this value unknown until a fixed flow is repeated across real project changes.

Commercial-use condition

Commercial use appears allowed with conditions. Pro explicitly offers a non-GPL SDK. Lite's Unity SDK is GPL-3.0, and the current documentation sends users to the LICENSE inside the package for the full terms. Keep AltTester out of the production player build, review the current package or order form, and do not use the historical license page as legal clearance. Tier eligibility, renewal, refunds and transfer rules also apply. This is not legal advice.

AltTester says logs and CLI snapshots stay local, while the license key goes to its domain and anonymized product analytics include functions, connections, errors, durations, versions, commands, engine and platform details. The visible privacy policy is dated 2019 and a current public product DPA or subprocessor list was not located. Local stdio MCP also does not prevent the chosen AI client from processing the context it receives; assess that provider separately.

PRODUCTION RISKS

Resolve these before production use.

Instrumentation changes the build and threat model

The SDK exposes internal hierarchy and methods for testing. Keep separate configurations, control connectivity and verify that release artifacts do not contain the test entry point.

O08O04

Selector and state drift creates maintenance

Hierarchy, object names, timing, saves, accounts and random systems can change without a player-visible regression. Page objects, explicit waits, fixtures and useful assertions reduce—not eliminate—that cost.

U01U04U06

Mobile and IL2CPP paths need their own proof

Port forwarding, input differences, device clouds and IL2CPP can behave differently from the Editor or Mono. Reproduce every target platform before calling a suite release-ready.

O09O15U01U08U10

Unreal AI support is explicitly limited

The core Unreal SDK exists, but current AI Extension documentation warns of limited support and known issues include property paths, Recorder output and minimized rendering. Do not transfer a Unity MCP conclusion unchanged.

O06O14O16O17

Agent prototypes add a second cost stack

The AWS example proves a possible architecture, not AltTester's bundled economics. Models, orchestration, retrieval, cloud devices, filtering, prompts and observability sit outside the Pro seat.

O06U11

NOT VERIFIED

Claims this page does not make

RESEARCH METHOD

Research-reviewed from public evidence

Research-reviewed from public evidence. We checked twenty-one official product, pricing, license, Desktop, Unity, Unreal, CLI, MCP and training sources, then coded eleven external records across an independent testing company, game-development communities, two academic or university reports, Stack Overflow, GitHub Issues, Sauce Labs and AWS Games. Reddit contributes three records but only two threads; partner implementation documents establish architecture, not user satisfaction. No registration, download, installation, instrumentation, device connection, test execution or MCP call was made or required.

Research windowCurrent product, pricing, terms, Desktop 2.3.3, Unity SDK 2.3.2, Unreal SDK 1.2.1 and AI Extension material were checked September 16, 2026. Eleven external records span 2020–2026; current independent MCP production evidence remains sparse.
OFFICIAL SOURCES21
  1. O01
    Official
    AltTester tools

    Official Inspector, Recorder, Unity/Unreal, driver-language, platform and device-cloud scope.

    Checked Sep 16, 2026
  2. O02
    Official
    AltTester pricing

    Current Trial, Lite, Pro, connection, engine and add-on entitlements.

    Checked Sep 16, 2026
  3. O03
    Official
    Pricing update effective July 1, 2026

    Current EUR 109 monthly and EUR 900 yearly Pro prices, Lite rename and modular add-ons.

    Checked Sep 16, 2026
  4. O04
    Official
    AltTester terms and conditions

    Subscription, renewal, refund, transfer, telemetry and broad Lite tier-eligibility terms.

    Checked Sep 16, 2026
  5. O05
    Official
    AltTester privacy policy

    Website-oriented policy effective February 28, 2019; it does not consolidate the newer product telemetry terms.

    Checked Sep 16, 2026
  6. O06
    Official
    AltTester CLI and AI Extension

    Current CLI, local stdio MCP, Robot and Helper skills, client configurations, workflows and limitations.

    Checked Sep 16, 2026
  7. O07
    Official
    AltTester Unity SDK

    Current Unity SDK 2.3.2 documentation and object-level automation scope.

    Checked Sep 16, 2026
  8. O08
    Official
    Unity SDK setup

    Package installation, instrumentation, server and test-project setup; intended for debug builds.

    Checked Sep 16, 2026
  9. O09
    Official
    Unity SDK FAQ

    Unity version, platform, language, input-system, IL2CPP and device-cloud guidance.

    Checked Sep 16, 2026
  10. O10
    Official
    Current Unity SDK license page

    Current documentation defers detailed license terms to the LICENSE inside the downloaded SDK package.

    Checked Sep 16, 2026
  11. O11
    Official
    Historical Unity SDK 2.2.0 license explanation

    Historical GPL explanation used only as context, not as a substitute for the current package license.

    Checked Sep 16, 2026
  12. O12
    Official
    Official Unity SDK repository

    GPL-3.0 repository, current release activity and public issue history.

    Checked Sep 16, 2026
  13. O13
    Official
    Desktop compatibility matrix

    Current Desktop, Unity SDK and Unreal SDK version compatibility.

    Checked Sep 16, 2026
  14. O14
    Official
    AltTester Unreal SDK

    Current Unreal SDK 1.2.1 documentation.

    Checked Sep 16, 2026
  15. O15
    Official
    Unreal SDK FAQ

    Documented Unreal versions, platforms, languages and device-cloud boundaries.

    Checked Sep 16, 2026
  16. O16
    Official
    Unreal SDK known issues

    Current rendering, BrowserStack, property-path and Recorder limitations.

    Checked Sep 16, 2026
  17. O17
    Official
    Unreal SDK release notes

    Unreal SDK 1.2.1 release and compatibility history.

    Checked Sep 16, 2026
  18. O18
    Official
    AltTester order configuration

    Engine, billing period and seat selection; both engines and more connections require contact.

    Checked Sep 16, 2026
  19. O19
    Official
    AltTester product updates

    Product-update record for the 30-day trial and current releases.

    Checked Sep 16, 2026
  20. O20
    Official
    AI-assisted automation workshop

    Vendor workflow that uses an LLM to author tests under review, then runs deterministic Robot suites.

    Checked Sep 16, 2026
  21. O21
    Official
    AltTester CLI release article

    CLI positioning for AI tools, CI/CD and custom agent workflows.

    Checked Sep 16, 2026
INDEPENDENT EVIDENCE RECORDS11
  1. U01
    Independent walkthrough
    TestDevLab practical mobile-game automation guide

    A concrete Unity game workflow reports strong object access and execution speed alongside setup, iOS, diagnostics and long-session friction.

    Checked Sep 16, 2026
  2. U02
    Community case
    r/gamedev automation research thread

    A research account questions whether E2E setup and maintenance repay manual-regression effort; author affiliation lowers independence weight.

    Checked Sep 16, 2026
  3. U03
    Community case
    AltTester historical user reply

    A different user keeps stable login, level-screen and payment flows automated while leaving complex volatile features manual.

    Checked Sep 16, 2026
  4. U04
    Community case
    Unity automation setup advice

    An automation specialist recommends repository-version discipline, page objects, explicit waits, assertions and useful failure messages.

    Checked Sep 16, 2026
  5. U05
    Academic case
    Automated testing in video game development

    A small Unity experiment found all four seeded bugs at least partly, while randomness and an unexpected manual finding support complementary coverage.

    Checked Sep 16, 2026
  6. U06
    Academic case
    NAU game-testing feasibility report

    A student team rated setup and maintenance moderate, then selected a narrower framework plus manual smoke testing for its available bandwidth.

    Checked Sep 16, 2026
  7. U07
    Community case
    AltTester waiting-to-connect question

    A beginner's stalled connection was resolved by learning that the Desktop Server must be running.

    Checked Sep 16, 2026
  8. U08
    Technical repository
    Unity SDK issue 1922

    Open report of a Python component-method path working under Mono but failing under IL2CPP on Android and macOS.

    Checked Sep 16, 2026
  9. U09
    Community case
    Historical AltUnity iOS simulator integration issue

    A historical simulator failure came from a Selenium and AltUnity namespace collision; retained only as integration-friction context.

    Checked Sep 16, 2026
  10. U10
    Independent walkthrough
    Sauce Labs AltTester integration

    Current partner documentation confirms real-device execution and lists tunnel, port, version and instrumentation prerequisites.

    Checked Sep 16, 2026
  11. U11
    Independent walkthrough
    AWS Games AI testing-agent prototype

    A controlled Android prototype uses AltTester object state in an agent loop; larger titles still require new tools, prompts and perception strategies.

    Checked Sep 16, 2026

DISCLOSURE

How this research was supported

Independent editorial research. MakeGameWithAI has no affiliate link, sponsorship, vendor-provided account, trial extension, license, training, device-cloud access, interview or technical support for this review. Owner Review approved the object-level automation positioning, some_basics / medium beginner decision, easy / high Pro agent decision, price-to-entitlement framing, conditional commercial/data boundary and no Editorial Recommendation on September 16, 2026.

Research review and Owner Review are complete.

This public research review will be revisited when pricing, terms, product versions, or material new evidence changes.