Skip to content
testcritic

Waldo vs Firebase Test Lab

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 only

From $1 per virtual device hour (physical devices are $5/hour)

Free tier

What 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.

Pay-as-you-go on the Blaze plan, billed to the nearest minute. Physical devices cost five times virtual ones, which is the number that actually shapes a bill. Android Device Streaming is separate: 30 free minutes per project per month, then $0.15 a minute.

Free tier

Free trial.

Spark plan: 10 virtual-device tests a day (up to 60 free minutes) and 5 physical-device tests a day (up to 30 free minutes).

Open source

Self-hostable

No-code authoring

Languages

Codeless
KotlinJavaSwiftJavaScript

Platforms

iOSAndroid
AndroidiOS

Fits teams

StartupScale-up / mid-market
Solo / side projectStartupScale-up / mid-marketEnterprise

Adoption

Emerging

Tricentis (formerly Waldo) · since 2019

Widely used

Google · since 2016

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.
  • Very cheap per device hour compared with commercial device clouds.
  • Robo Test finds crashes with zero test-writing effort.
  • Tight integration with Android tooling and Firebase Crashlytics.

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.
  • Device selection is far narrower than a dedicated device cloud.
  • iOS support is meaningfully thinner than Android.
  • No interactive manual testing session.

Best for

Tricentis customers extending into mobile. Small teams that wanted Waldo's self-serve simplicity should look at Maestro instead.

Android-first teams that want real-device coverage at the lowest cost.

All of these integrate with: GitHub Actions.

Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.