HN Showcase
Back to browse
Chat AI Agent inside mobile device testing sessions

Chat AI Agent inside mobile device testing sessions

by krishpavuluri·Mar 9, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidSolve My ProblemSlick

AI-assisted mobile testing inside the device farm—saves inspector tab-switching, but cloud device farms exist.

Strengths
  • •Dual-context insight: combining screenshot + accessibility tree eliminates most locator friction in real-time.
  • •Reduces test-writing friction with generated Appium/Swift/Kotlin code directly from live screen state.
  • •Solves a genuine session workflow pain (flipping between inspector tools and test runner).
Weaknesses
  • •Cloud device farms are competitive (BrowserStack, Sauce Labs, LambdaTest)—the AI agent is a feature, not a moat.
  • •No pricing transparency on landing page; unclear if AI agent requires higher tier or how it affects cost.
Category
SaaS
Target Audience

Mobile QA engineers and test automation teams using Appium, Selenium, Playwright

Similar To

BrowserStack · Sauce Labs · LambdaTest

Post Description

We build RobotActions, a cloud device farm for Android/iOS testing. We just shipped a Chat AI Agent that lives inside the live device session.

What it does:

- During a session, you can ask "What's the XPath for this button?" and get a ready-to-use locator from the current screen - Ask "Write an Appium test for this flow" → get test code generated from the live accessibility tree - Type "tap the login button" in natural language → it executes on the real device - Ask "Why is my test failing on this element?" → gets context from both vision and the accessibility snapshot

The agent uses a combination of screenshot vision and the device's live accessibility tree. The key insight is that most mobile test failures are locator issues or UI state issues — and an agent with full context of what's on screen right now can solve those immediately, without the engineer leaving the session to use a separate inspector tool.

Technical bits: - Accessibility tree is captured per-frame during the session - Agent has both visual context (screenshot) and structured context (a11y tree) simultaneously - Supports Android (UIAutomator2/XPath/UISelector) and iOS (XCUITest/Appium) - Session context is also exposed via API for CI/CD post-failure reports

Happy to discuss the architecture, especially the tradeoffs between using vision alone vs. vision + a11y tree for locator generation.

Similar Projects