Skip to content
testcritic

Firebase Test Lab 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

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

Free tier

Quote on request

Quote only

What drives the bill

The metric that actually scales your invoice.

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.

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

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

Free trial.

Open source

Self-hostable

No-code authoring

Languages

KotlinJavaSwiftJavaScript
Codeless

Platforms

AndroidiOS
iOSAndroid

Fits teams

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

Adoption

Widely used

Google · since 2016

Emerging

Tricentis (formerly Waldo) · since 2019

Strengths

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

  • Device selection is far narrower than a dedicated device cloud.
  • iOS support is meaningfully thinner than Android.
  • No interactive manual testing session.
  • 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-first teams that want real-device coverage at the lowest cost.

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

All of these integrate with: GitHub Actions.

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