{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/desktop-automation.test-suite-run/",
    "json": "https://www.anchorterminal.com/niches/desktop-automation.test-suite-run/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/desktop-automation.test-suite-run/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/desktop-automation.test-suite-run/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 2 | 13 | 12 | 8 |\n\n## What counts as done\n\nA machine-readable result per test or goal (pass, fail, error) with the step and evidence for each failure, an exit status that is never success when nothing ran, and cost reported per run.\n\nHow agents ask for it: write tests for the desktop app; run the regression suite; playtest the new level and tell me what broke\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Aura Autopilot (TribeVR Inc. (named in Aura's terms of service and privacy policy), trading as Ramen)**: Verify, goal and explore runs end in a report and exit 0 confirmed, 2 denied, 3 inconclusive or 1 not achieved; regress --json writes per-regression results headless for CI. Cost shows only after a run (acc-18, open), and acc-16 hit a registration failure before any run.\n- **Robot Framework (Robot Framework ry (Robot Framework Foundation), business ID 2754775-1, Helsinki)**: Per-test PASS, FAIL or SKIP with messages in output.xml or JSON matching result.json, distinct return codes, and no matching tests fails unless --RunEmptySuite. acc-14 saw TestSuite.run return 0 with no tests, closed not planned; no cost is reported, though local runs cost nothing.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **UiPath (UiPath Inc.)**: UiPath has a separate Test Cloud doc set that wasn't read, so test-set execution and result formats from outside are unknown.\n\n- not this job: AutoCua (Ashish Yadav and contributors (ComputerUseAgent on GitHub)): No test runner, per-test result format or exit status for suites.\n- not this job: AutoHotkey (AutoHotkey Foundation LLC): No test runner, per-test result format or run report; an agent would have to build one in script.\n- not this job: AutoIt (AutoIt Consulting Ltd): No test runner or per-test result format.\n- not this job: Automation Anywhere (Automation Anywhere, Inc.): No test runner or per-test result format among the Control Room API groups listed.\n- not this job: Beam (beam.win) (Noats, Inc.): No test runner, results or exit status.\n- not this job: Mage-VL-Cowork (Microsoft): No test runner or result format; OSWorld scoring is Microsoft's evaluation harness, not a product feature.\n- not this job: Robocorp (Sema4.ai (full legal name not confirmed)): Supplies keyword libraries; test execution and result formats come from Robot Framework, listed separately.\n\n3 listings in the category were added after this reading and aren't marked yet.\n\n## What stops agents finishing\n\n- run start hangs pending when the sandbox fails\n- account sign-up step before the first run\n- exit code 0 when no test matched\n\n## Around it\n\nBefore: code.write-feature. After: code.open-issue, agent-observability.trace-run.\n\n## Where this comes from\n\nWeight 12 of 100 in Desktop \u0026 mobile app control: 8 of 45 accounts (Robot Framework and Aura Autopilot issues)\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/desktop-automation.test-suite-run.json, or the MCP tool get_use_case with id desktop-automation.test-suite-run. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Write and run a UI test suite or game playtest and report results",
        "url": ""
      }
    ],
    "description": "Write and run a UI test suite or game playtest and report results: 0 companies fully do it, 2 with a limit, 13 carry the tag. Every listing in Desktop \u0026 mobile app control with the reason and a source.",
    "facts": null,
    "h1": "Write and run a UI test suite or game playtest and report results",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/desktop-automation.test-suite-run/",
    "published": "",
    "section": "agents",
    "title": "Write and run a UI test suite or game playtest and report results |…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/desktop-automation.test-suite-run/"
  },
  "tokens": {
    "markdown": 1050,
    "slim": 280
  },
  "version": 1
}
