Espresso waits on your developers. Pie writes the tests.

Give your Android developers their hours back. Pie’s agents explore your APK and write the tests, and anyone on your team can add one in plain English.

Pie

Pie is an agentic testing platform that writes Android tests from your APK. Agents explore the app, and anyone on your team can add a test in plain English.

Espresso

Espresso is Google’s free, open-source framework for UI tests on Android. Your Android developers write each test in Kotlin or Java.

The basics

Pie vs Espresso at a glance

PieAgentic testing platform
What it is
An agentic testing platform for web, iOS and Android apps.
Who writes the tests
Pie’s agents explore your app and generate them. Your team adds the cases that matter in plain English.
What a test is
Plain-English steps and checks. No scripts to write, no locators to break.
Where it runs
iOS apps on the iOS Simulator, Android apps on the Android Emulator, and web apps in a browser. Nothing to install.
AI help
The whole product. Agents explore, write and run the tests, and group what they find into issues.
EspressoAndroid UI testing framework
What it is
Google’s free, open-source framework for UI tests on Android.
Who writes the tests
Your Android developers, in Kotlin or Java.
What a test is
Code that finds a view by its ID or text, acts on it, then checks the result.
Where it runs
On Android emulators and devices you set up, or on a device cloud such as Firebase Test Lab.
AI help
Android Studio has Journeys, a separate preview feature that runs tests described in natural language.
Who brings what

Five jobs in every mobile test. Who does each one?

A working mobile test needs an environment, a script, a device, upkeep and someone to read the failure. Here is who handles each part with Espresso, and who handles it with Pie.

The jobEspressoPie
Set up the environment

EspressoYour developers add the Gradle dependencies and the test runner, and turn off three animation settings on each test device.

PieNothing to install. Upload an iOS simulator build or an Android APK.

Write the test

EspressoYour developers, in Kotlin or Java, plus an idling resource for each background operation Espresso can’t see.

PiePie writes it. Tell Pie Chat what to check, and it explores the flow and drafts the test for your OK.

Supply the device

EspressoYour own emulators and devices, or Firebase Test Lab at $1 per virtual device hour and $5 per physical device hour after the free quota.

PieSimulators and emulators for iPhone, iPad and Android phones and tablets, on the OS version you pick.

Keep it passing after a UI change

EspressoYour developers update the view matchers in code when a view’s ID or text changes.

PieNo locators to repair. Pie re-reads the screen on every run.

Make sense of a failure

EspressoYour developers, from the test results in Android Studio.

PiePie groups related findings into issues. Your team decides what counts as a bug.

Where they differ

Four reasons your Android tests shouldn’t wait on developers.

  1. 01

    Espresso is written for developers

    Google says Espresso’s full power is unlocked for people who know the codebase under test. So in most teams, the tests wait on developer time. Pie’s agents generate the tests, and anyone on your team can add one in plain English.

    Source
  2. 02

    No license, plenty of developer time

    Espresso costs nothing to download. The cost is the developers who write the tests and repair them. In one study, flaky tests alone took at least 2.5% of a team’s productive time. Pie’s agents write the tests and re-run them on every APK.

    Source
  3. 03

    Background work is yours to register

    Espresso waits for the main thread, but its docs say it is “not aware” of other asynchronous work. Your developers register each one as an idling resource. Android’s own testing guide says idling resources can be hard to install. Pie works from the screen, so there is nothing to register.

    Source
  4. 04

    Android phones and tablets, on the version you pick

    Pie runs your Android tests on phone and tablet emulators, on the Android version you pick. When your iOS or web app needs testing, it is the same platform.

Side by side

What your Android developers stop doing.

Espresso tests are code your Android developers write and keep in sync with the app. Pie writes its tests from your APK.

What you’re comparingPieEspressoAdvantage
Cost to run it No scripts to write and no locators to break, so your team spends those hours on your product. Your developers’ hours to write and repair tests, plus the devices or device cloud they run on. Pie
Getting started Upload an Android APK. You get results in hours, not weeks. Add the dependencies and the test runner to the Android project, then write your first test in Kotlin or Java. Pie
Writing a new test Agents generate tests by exploring your app. Anyone on your team can add one in plain English. A developer writes it in code, with matchers for each view and idling resources for background work. Pie
When the UI changes No locators to update. Pie re-reads the screen on every run. View matchers live in code. When an ID or a label changes, a developer edits the test. Pie
Apps it covers Android apps from an APK you upload, plus iOS and web apps. Android apps. Pie
Fixing the bug Pie groups related findings into issues, and can open a Fix PR in a repo you connect. Merging it is always your team’s call. Espresso reports pass or fail in Android Studio. Triage and the fix are your team’s. Pie
License cost Custom pricing, tailored to your team’s requirements and testing volume. Contact Pie for a quote. Free and open source, under the Apache 2.0 license. Espresso
Speed inside the app Pie works from the outside, on what the screen shows, the way a user does. Espresso runs in the app’s own process and waits on the main thread, so tests run fast with no sleeps. Espresso
The exception

When the test has to run inside the app

Your developers want fast tests inside the app

Espresso runs in the app’s own process and syncs with the main thread, so a developer gets quick feedback from Android Studio while the code is still open. Pie works from the screen, the way a user does.

Source
Who should pick which

Which fits your team, Pie or Espresso?

Pick Pie to

  • Get Android tests without waiting on developer time.
  • Test on Android phones and tablets, on the version you pick.
  • Give your developers back the hours they spend on matchers and idling resources.
  • Run your suites on a schedule or on every new build, with nobody starting them.
  • Bring your iOS and web apps in on the same platform.

Pick Espresso if

  • Your developers need fast tests that run inside the app’s own process.
Getting started

Switch from Espresso one flow at a time

No big rewrite. Your Espresso tests keep running until Pie covers the same flow.

  1. 1

    Upload a build

    Give Pie an Android APK. If the app has a login, add a test login through a supported path.

  2. 2

    Let Pie explore

    Pie explores your app’s reachable flows and generates tests. You get results in hours, not weeks.

  3. 3

    Add your edge cases

    Type the cases only your team knows into Pie Chat in plain English. Pie explores each flow, drafts the test and runs it once you confirm.

  4. 4

    Retire tests as Pie covers them

    Compare Pie’s results with your Espresso runs, and delete each UI test once Pie covers the flow.

FAQ

Did we miss a question?
Email us directly →

Is Pie an Espresso alternative?

Yes. Pie replaces the UI tests your developers write and maintain with tests its agents generate by exploring your app.

Stay on Espresso if your developers need fast tests that run inside the app’s own process.

Is Espresso free?

Yes. Espresso is open source under the Apache 2.0 license.

The cost is your developers’ time to write the tests and keep them passing, plus the devices or device cloud they run on.

Pie’s agents write and run the tests, with no matchers for your developers to maintain.

What are Espresso idling resources?

Espresso waits for the app’s main thread on its own, but its docs say it is “not aware” of other asynchronous operations, such as work on a background thread.

Your developers register each one as an idling resource so the test knows when to continue. Pie works from what the screen shows, so there is nothing to register.

Does Espresso work with Jetpack Compose?
Compose has its own testing APIs. Google’s docs describe Espresso as intended for View-based UIs, so an app that mixes Views and Compose uses both. Pie reads the screen, so the UI toolkit behind it doesn’t change the test.
Doesn’t Android Studio have AI testing now?
Android Studio has Journeys, a preview feature that runs tests described in natural language. It is separate from Espresso, and a person still writes each journey. Pie’s agents find the flows by exploring your app.
Does Pie test on real devices?

Real devices are available on demand. Pie runs iOS apps on iOS simulators and Android apps on Android emulators, on the OS version you pick.

Our guide to real devices, emulators and simulators covers which bugs need which.

Does Pie test APIs and accessibility too?

Yes, and both are in beta. Pie runs whole API flows call by call, and checks each screen its tests reach for accessibility problems.

Your UI, API and accessibility testing sit in one place.

What do Espresso users complain about?

Flaky runs that trace back to synchronization. Espresso waits for the main thread, and your developers register other background work by hand. Android’s own testing guide says idling resources can be hard to install.

With Pie there are no idling resources for your developers to write.

How do I move from Espresso to Pie?
One flow at a time. Upload a build, let Pie generate tests, and type your edge cases into Pie Chat. Keep your Espresso tests running until Pie covers the same flow, then retire them.
Who on my team runs Pie?

Whoever owns quality today, such as a QA lead or an engineer who owns releases. Pie does the exploring, writing and re-running, and the owner decides what matters and what counts as a bug.

Anyone on the team, including a product manager, can read a test or add one in plain English.

What does Pie cost?

Pie’s pricing is custom, tailored to your team’s requirements and testing volume.

You buy one product: agents explore your web, iOS and Android apps, write and run the tests, group related findings into issues and can open a Fix PR.

Book a demo, tell us what you ship and how often you release, and we’ll send you a quote.

Test your Android app without writing the test code.

Book a demo and bring an APK. We’ll show you the tests Pie writes for it, with no idling resources to register.

Sources

  1. Espresso, Android Developers. UI tests for Android in Kotlin or Java; aimed at developers, with its “full power” unlocked for those familiar with the codebase under test; synchronizes with the main thread.developer.android.com/training/testing/espresso
  2. Espresso setup instructions. Gradle dependencies, the AndroidJUnitRunner, tests in src/androidTest, and the recommendation to turn off three system animation settings on test devices.developer.android.com/training/testing/espresso/setup
  3. Espresso idling resources. Espresso is “not aware” of other asynchronous operations; each must be registered as an idling resource.developer.android.com/training/testing/espresso/idling-resource
  4. Testing your Compose layout. Compose has its own testing APIs; Espresso is intended for View-based UIs.developer.android.com/develop/ui/compose/testing
  5. Journeys for Android Studio. Natural-language tests run by Gemini, in preview and separate from Espresso.developer.android.com/studio/gemini/journeys
  6. AndroidX Test on GitHub, the home of Espresso. Apache 2.0 license.github.com/android/android-test
  7. Firebase Test Lab usage, quotas and pricing. Beyond the free daily quota, $1 per device hour on virtual devices and $5 per device hour on physical devices.firebase.google.com/docs/test-lab/usage-quotas-pricing
  8. Cost of Flaky Tests in CI, ICST 2024 industry track. Five years of history, about 30 developers, one commercial project; “at least 2.5% of the productive developer time”. Not specific to Espresso.conf.researchr.org/details/icst-2024/icst-2024-industry/1
  9. Android Developers, Stability of instrumented tests. “Idling resources can be hard to install.”developer.android.com/training/testing/instrumented-tests/stability