This section is The content in this section is supplied by GlobeNewswire for the purposes of distributing press releases on behalf of its clients. Postmedia has not reviewed the content. by GlobeNewswire Article content
The same agent that drives Chrome now drives native and hybrid mobile apps, with no Appium servers, brittle locators, or context switches to maintain
Sign In or Create an Account
or View more offersArticle content
SAN FRANCISCO & NOIDA, Sept. 10, 2026 (GLOBE NEWSWIRE) — TestMu AI (formerly LambdaTest), the Agentic AI Quality Engineering platform, announced Mobile Automation in Kane CLI, extending its agentic, vision-grounded verification engine natively to iOS Simulators and Android Emulators. Teams can now state the expected user outcome in plain English, and Kane CLI drives the device, verifies the rendered output, and delivers a defensible verdict.
Article contentWe apologize, but this video has failed to load.Try refreshing your browser, or
tap here to see other videos from our team.Article content
Story continues below
This advertisement has not loaded yet, but your article continues below.
Article content
Mobile UI testing has carried a heavy maintenance tax for more than a decade. Setting up Appium servers, mapping accessibility labels and resource-id locator hierarchies that shift with every build, handling ADB port locks, and switching contexts between WebViews and native views consume immense engineering time. Within months of launching an automated mobile suite, a large share of tests end up commented out because maintaining them costs more than building the features themselves. When TestMu AI launched Kane CLI to eliminate selector decay on the web, the feedback from engineering teams was unanimous: web testing was difficult, but mobile testing was an operational nightmare.
Article contentArticle content
Rather than build a wrapper around Appium, TestMu AI extended Kane’s core architecture directly to native mobile viewports. Mobile does not run on a separate, simplified agent; the same reasoning and perception graph that drives Chrome now drives iOS Simulators and Android Emulators, so writing a mobile test feels the same as writing a web one. At every step, Kane CLI captures the screen and reads the native accessibility document, serializing each element with its affordance, geometry, state, and identity so the agent can evaluate screens against human intent rather than brittle XPath queries. This works across native UI frameworks including UIKit, SwiftUI, Jetpack Compose, Flutter, and React Native.
Article content
Story continues below
This advertisement has not loaded yet, but your article continues below.
Article content
Hybrid app screens fold WebView elements directly into the same perception list, so the agent never performs an explicit Appium context switch, removing a major source of mobile test flakiness. When native trees collapse or an app renders non-standard components such as custom canvas elements or Flutter controls, the agent falls back to visual reasoning and coordinate grounding so the flow keeps moving. Every mobile run also seals a portable evidence pack containing step-annotated screenshots, native device logs, and step-attributed network traffic, replacing the usual hunt through ADB logs, Xcode console dumps, and video clips when a run fails.
Article content
“Mobile testing has always demanded a toll before you could even begin: a day of wiring up Appium, drivers, and device configuration, and then a permanent maintenance bill after that. With Kane CLI, that toll is gone. You describe the outcome you expect in a sentence, and the same agent that drives your browser drives your phone,” said Mudit Singh, Co-Founder and Head of Growth at TestMu AI. “What you get back isn’t a claim about what the agent says it did. It’s a verified verdict, with the screenshots, device logs, and network traffic to back it up.”