TestverTestver
AppiumAppium

Testver for Appium

Record, generate and repair native Android and iOS tests — on real devices.

Mobile automation is where suites go to rot. Capabilities drift between Appium versions, locators differ per platform, waits are guesswork, and a failing run on a device you cannot see is close to undebuggable.

Testver treats mobile like the rest of your testing: tap through the app once and the recorder writes an idiomatic Appium test in your language, then runs it on a locally connected device or a device cloud with the results collected next to your web suites. Mobile support is in beta today and available to use now.

Android & iOSAppium 2Real devicesDevice cloudsAccessibility idsBeta

Languages supported for Appium: Java · Python · TypeScript · JavaScript · C#

Today

What an Appium suite costs to keep

  • Locators differ per platform—Accessibility ids, resource ids and XPath all behave differently on Android and iOS, so one flow needs two sets of selectors.
  • Capability sprawl—Every device, OS version and Appium release wants slightly different capabilities, and getting them wrong costs a run.
  • Failures you cannot watch—When something breaks on a cloud device, the evidence is a log and a video you have to sit through.
With Testver

The same suite, maintained for you

  • A recorder that speaks mobile

    Tap through the journey on a real device and the AI Record Agent writes the test in your framework and language, with stable accessibility-id locators where they exist.

  • Auto-Heal for mobile locators

    When an element id changes, the fix is proposed from what the session actually saw and verified by re-running before it is kept.

  • Local devices and device clouds

    Run on a phone plugged into your machine, or on BrowserStack, LambdaTest and Sauce Labs device clouds — same workflow, same reports.

  • Plain English for mobile actions

    Ask the assistant to add a scenario, drive an on-device action, or explain a mobile failure, with full context on your project.

  • One workspace for web and mobile

    Web, Mobile or Both modes adapt the UI to what you test, so a mobile suite lives beside the web suite with shared scheduling, history and CI gating.

What lands in your repository

Plain Appium in your own style — recorded on a device, written to your repo. Delete Testver tomorrow and this test still runs — there is no Testver runtime, adapter or import inside your project.

AppiumJava
@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());
}
Quickstart

Point Testver at your Appium project

It detects the framework, language and structure on its own. No migration, no config file to write, no change to how you run tests.

1

Install it

One global npm package. Node 18 or newer 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

Appium questions, answered

Which devices can Testver run Appium tests on?
Devices connected locally to your machine, or BrowserStack, LambdaTest and Sauce Labs device clouds. Results are collected the same way either way.
Which languages are supported for Appium?
Java, Python, TypeScript, JavaScript and C#. Generated tests are plain Appium code in your own project structure.
Is mobile support production ready?
Mobile is in beta and available to use now. It covers recording, generation, execution on real devices and reporting, in the same workspace as your web suites.

More in the full FAQ or the documentation.

Running more than one framework?

One Testver instance handles all of them — different projects can use different frameworks, languages and AI models.

PlaywrightPlaywrightSeleniumCypressRobot FrameworkWebdriverIO

See the full feature set, the comparison with other approaches, or try a live demo repo.

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