Waldo vs Espresso
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
Quote on request
Quote onlyFree and open source
Open sourceWhat drives the bill
The metric that actually scales your invoice.
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 and open source. You pay in engineering time and CI minutes.
Free tier
Free trial.
Everything, self-hosted
Open source
Apache-2.0
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Emerging
Tricentis (formerly Waldo) · since 2019
Category standard
Google · since 2013
Strengths
- 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.
- 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.
Limitations
- 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.
- Android only.
- Testing across app boundaries requires UiAutomator alongside it.
- Compose testing uses a related but separate API to learn.
Best for
Tricentis customers extending into mobile. Small teams that wanted Waldo's self-serve simplicity should look at Maestro instead.
Android teams that want the fastest, most reliable native UI tests.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.