TestverTestver
Mobile testingBeta

Native Android & iOS tests — record them or describe them

Tap through your app or describe the flow in plain English and get an Appium test in your language — then run it on a phone on your desk or on a device cloud, beside your web suites.

Get started freeRead the documentation
Android & iOSAppiumReal devicesEmulators & simulatorsDevice cloudsHybrid apps
Testver — Mobile
AI Record · Pixel 8 · USBAppium · Java
Cart
SAVE20Apply
Total$79.20
Tap cart-tabaccessibilityId
Type "SAVE20"promo-input
Tap Applyapply-promo
Assert $79.20order-total
One workspace
Mobile beside webThe same scheduling, history and reports as your web suites.
Real devices
Local or cloudUSB phones, Android emulators, iOS simulators, BrowserStack, LambdaTest and Sauce Labs.
Hybrid ready
Native and webview togetherWebview steps keep their real web locators and context.
End to end

How mobile testing runs in Testver

  1. 1

    Switch the project to Mobile

    The workspace shows device tooling, an app library for your .apk and .ipa builds, and mobile-aware AI.

  2. 2

    Connect a device

    An Android phone over USB or an Android emulator, an iPhone or iOS simulator on a Mac, or a real device on BrowserStack, LambdaTest or Sauce Labs.

  3. 3

    Record it, or describe it

    AI Record writes Appium code as you tap, accessibility ids first. Or the AI Assistant writes it from plain English, driving the app itself and reusing your helpers.

  4. 4

    Hybrid screens, handled

    Webview steps are captured with their real web locators and wrapped in the right context switch.

  5. 5

    Run, watch and repair

    A live device view while it runs, then failure analysis and Auto-Heal for mobile locators, verified by a re-run.

Not only recording

Author mobile flows by describing them

You do not always have the app in hand. The AI Assistant writes and updates mobile tests from plain English too — driving the app itself — and reuses your helpers and locator conventions instead of inventing new ones.

  • Describe a scenario; get an Appium test in your language
  • Refactor, extend or debug an existing mobile test the same way
  • Reuses the page objects and helpers already in your project
  • The code lands in your repo, not in a proprietary format

“Add a test that applies promo code SAVE20 in the cart and asserts the order total.”

CheckoutTest.javaJava · Appium
@Test
public void checkoutAppliesPromoCode() {
    driver.findElement(AppiumBy.accessibilityId("cart-tab")).click();
    driver.findElement(AppiumBy.accessibilityId("promo-input"))
          .sendKeys("SAVE20");
    driver.findElement(AppiumBy.accessibilityId("apply-promo"))
          .click();

    assertEquals("$79.20", driver.findElement(
        AppiumBy.accessibilityId("order-total")).getText());
}
What you get

Everything for mobile testing

AI Record for mobile

Tap-through capture that writes Appium code with ranked, accessibility-first locators.

In your language

Java or Kotlin, Python with pytest, C# with NUnit, Ruby with RSpec, Robot with AppiumLibrary, or WebdriverIO in TypeScript.

Plain-English authoring

The AI Assistant drives the app to write, extend and debug tests from a description.

Live device view

Watch the screen while the test runs instead of reading a log afterwards.

Hybrid and webview

Native and web layers in one test, each addressed the right way.

Auto-Heal for mobile

Broken ids repaired from the session’s page source, then verified by a re-run.

Your stack

Already using a framework?

Testver wraps it rather than replacing it.

AppiumWebdriverIOJava · TestNGpytest

Also works with Android · iOS · Kotlin · NUnit · RSpec · Robot Framework

Questions

Mobile testing, answered

Do we have to record every mobile test?

No. Recording is quickest when the app is in front of you, but the AI Assistant also writes and updates mobile tests from a plain-English description, driving the app itself and reusing the helpers already in your project.

Do we need a separate tool for mobile testing?

No. Mobile lives in the same Testver workspace as your web and API suites, sharing scheduling, run history, reporting and CI gating.

Can we run on real devices as well as emulators and simulators?

Yes — Android phones and iPhones connected to your machine, Android emulators and iOS simulators, or real devices on BrowserStack, LambdaTest and Sauce Labs. iOS on your own machine needs a Mac with Xcode.

Does it handle hybrid apps with webview screens?

Yes. Webview steps are recorded with their real web locators and wrapped in the right context switch, so the test addresses each layer correctly.

Is mobile testing production-ready?

Mobile is in beta. Recording, AI authoring, device clouds, the live view and Auto-Heal are all available today, and it improves with every release.

Web testingAPI testing
Quickstart

Start testing mobile in three commands

No account required to install, nothing to configure first, and your existing project works as-is.

1

Install it

One global npm package. Node.js 22 or newer (24 recommended) is the only prerequisite.

terminal
npm install -g @testver/testver
2

Go to your test project

Testver runs from inside the framework project you want to test, so change into that folder first.

terminal
cd path/to/your-test-project
3

Start the dashboard

Opens at localhost:3700. Testver detects the framework, language and structure of the project you started it in and lists your tests — no configuration to write.

terminal
testver serve

Typically under five minutes, start to first generated test.

Full installation guide — prerequisites, ports, running as a service
Ready to upgrade your test suite?

Keep your framework. Add AI and a premium toolset.

Set up in minutes. Self-host on your own hardware. Describe a test in plain English and get working code in your own framework — in a fraction of the time.

Get StartedSupport