--- title: "AI-Driven UI Testing with Android Studio Journeys" url: https://daily.dev/posts/ai-driven-ui-testing-with-android-studio-journeys-1rc0wqgtj source_url: https://proandroiddev.com/ai-driven-ui-testing-with-android-studio-journeys-ed98ae9ea89b type: article source: "ProAndroidDev" published: 2026-08-14T20:19:02.981Z updated: 2026-08-14T20:50:01.756Z tags: ["testing", "android", "google-gemini", "android-studio"] reading_time: 7 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # AI-Driven UI Testing with Android Studio Journeys **[ProAndroidDev](https://daily.dev/sources/pand)** · 7 min read · 0 upvotes · 0 comments ## Summary Journeys for Android Studio, powered by Gemini AI and integrated via AGP Test Suites, replaces brittle Espresso and UI Automator selector-based E2E tests with natural language intent-driven testing. Instead of hardcoded testTags or resource IDs, developers write XML step descriptions describing user goals, and a multimodal vision-reasoning engine interprets screenshots to compute taps, swipes, and assertions. The piece covers how the underlying screen-capture-to-Gemini-to-ADB pipeline works, rules for writing unambiguous journey steps, Gradle/AGP 9.0+ setup for CI execution, and where Journeys fit in a testing pyramid alongside unit and Compose tests. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Journeys for Android Studio and how does it differ from Espresso testing? Journeys is an AI-driven end-to-end UI testing feature in Android Studio, powered by Gemini and integrated via AGP Test Suites, that replaces hardcoded element selectors with natural language step descriptions. Instead of referencing testTag or resource IDs like Espresso does, you write XML steps such as tapping a field and verifying a total updates, and Gemini's vision engine interprets screenshots to compute taps, swipes, and assertions. _daily.dev surfaces practical breakdowns like this for teams evaluating AI-driven UI testing approaches._ ### What are the requirements to run Journeys tests in Android Studio and CI? Journeys requires Android Studio Otter 3 Feature Drop or later with Journeys enabled under Settings, Studio Labs, plus Android Gradle Plugin 9.0.0 or higher and a Google Developer Account signed in with Gemini access. Tests are configured through the testSuites DSL in build.gradle.kts and can run headlessly in CI environments like GitHub Actions or Firebase Test Lab via gradlew runJourneys. _developers wiring AI-based UI testing into CI pipelines track setup details like these on daily.dev._ ### How does the Journeys AI testing engine decide where to tap on the screen? The engine captures a high-resolution screenshot plus lightweight semantic metadata from the device, sends the frame along with the natural language instruction to Gemini's vision engine, which computes precise spatial coordinates and an interaction type such as a tap at specific x,y coordinates or a scroll amount. The gesture executes via ADB/UI Automator, then the engine waits for the screen to stabilize before capturing the next frame and verifying success. _engineers debugging flaky UI test runs can dig into pipelines like this one on daily.dev._ --- Tags: [#testing](https://daily.dev/tags/testing), [#android](https://daily.dev/tags/android), [#google-gemini](https://daily.dev/tags/google-gemini), [#android-studio](https://daily.dev/tags/android-studio) [View this post on daily.dev](https://daily.dev/posts/ai-driven-ui-testing-with-android-studio-journeys-1rc0wqgtj)