For AI agents and LLMs: a machine-readable index is available at llms.txt. A plain-Markdown version of any documentation page is available by appending .md to its URL.
Skip to main content

Mobilewright Testing on TestMu AI

Real Device

Mobilewright is an open-source mobile UI test framework with a Playwright-style API. You write tests in TypeScript or JavaScript against the device, screen, and expect fixtures, and Mobilewright drives your Android or iOS app with auto-waiting locators and retrying assertions.

With the TestMu AI driver for Mobilewright, you can run your existing Mobilewright suite on real Android and iOS devices in the TestMu AI cloud by changing one line of configuration. Your tests stay the same.

Currently in BETA

Mobilewright testing on TestMu AI is currently in Beta. To share feedback or report an issue, contact our support team.

Driver package

The TestMu AI driver is published on npm as @testmuai/mobilewright. Add it to your Mobilewright project with npm i -D @testmuai/mobilewright.

Why run Mobilewright tests on TestMu AI​

  • Real devices: Run your tests on real Android and iOS phones and tablets instead of local simulators and emulators.
  • Parallel execution: Each Mobilewright worker gets its own device, so you can spread a suite across many devices and cut the run time.
  • No test changes: Point mobilewright.config.ts at the TestMu AI driver. Locators, assertions, and fixtures work as they do locally.
  • Debugging artifacts: Every session records a video, device logs, and optional network logs on the App Automation dashboard.
  • Automatic reporting: Sessions are named after the tests they ran and marked passed or failed without any extra code.
  • Real-world conditions: Test behind a tunnel, from another country with IP geolocation, in a different timezone, or on a throttled network.

How it works​

The @testmuai/mobilewright package is a Mobilewright driver. When you run npx mobilewright test:

  1. The driver uploads your app (if you pass a local file) and requests a real device for each Mobilewright worker.
  2. TestMu AI allocates a device that matches the platform, device name, and OS version in your config, and starts an automation session on it.
  3. Every Mobilewright action, such as a tap, a swipe, or a hierarchy read, is sent to the device over that session. Nothing is installed on the device apart from your app.
  4. When the run ends, the driver pushes the pass or fail status of each session to the dashboard.

Supported configuration​

ItemSupport
Driver package@testmuai/mobilewright on npm
DevicesAndroid and iOS real devices only. Emulators and simulators are not supported.
Mobilewright version0.0.56 or later, below 0.1.0
Node.js version22.12 or later
LanguagesTypeScript and JavaScript
App formats.apk and .aab for Android, .ipa for iOS
DashboardSessions appear on the App Automation dashboard with the framework shown as Mobilewright

Get started​

  • Run your first test: run the sample project on a real device, run tests in parallel, read the results, and set up CI/CD.
  • Set up your test environment: manage credentials, apps, device selection, and test features such as tunnels, geolocation, and network throttling.
  • References: every driver and config option, common errors, and known differences from local runs.

Terminal First Testing With Kane CLI

Natural language browser & mobile app tests right from terminal.

×
Schedule Your Personal Demo
Kane CLI terminal

Help and Support

Related Articles