Espresso vs Waldo
Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.
Entry price
Free and open source
Open sourceQuote on request
Quote onlyWhat drives the bill
The metric that actually scales your invoice.
Free and open source. You pay in engineering time and CI minutes.
No longer priced as Waldo — it is part of a Tricentis Mobile quote, which is an enterprise sales conversation rather than the self-serve signup Waldo once had.
Free tier
Everything, self-hosted
Free trial.
Open source
Apache-2.0
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Category standard
Google · since 2013
Emerging
Tricentis (formerly Waldo) · since 2019
Strengths
- Automatic UI-thread synchronisation makes tests both fast and reliable.
- First-party Google support, updated alongside Android itself.
- Runs on emulators in CI cheaply, including Firebase Test Lab.
- No SDK and no code — a designer or PM can record a regression flow.
- Self-healing keeps recorded flows working across releases.
- Runs on every build without device lab management.
Limitations
- Android only.
- Testing across app boundaries requires UiAutomator alongside it.
- Compose testing uses a related but separate API to learn.
- You can no longer buy Waldo as such — it is a component of Tricentis Mobile, sold on an enterprise contract.
- Limited support for complex logic or data-driven scenarios.
- Cloud-only.
Best for
Android teams that want the fastest, most reliable native UI tests.
Tricentis customers extending into mobile. Small teams that wanted Waldo's self-serve simplicity should look at Maestro instead.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.