BBS 22: Are E2E Tests Just Burning Money?
Failed to add items
Add to basket failed.
Add to Wish List failed.
Remove from Wish List failed.
Follow podcast failed
Unfollow podcast failed
BBS 22: Are E2E Tests Just Burning Money?
-
Narrated by:
-
By:
About this listen
Key Moments
Defining end-to-end tests: The hosts clarify that true business end-to-end flows go far beyond what mobile teams can actually test, so the “ends” are usually artificially limited.
How they’re supposed to work: Tools like Detox or Maestro automate UI taps through accessibility labels, running flows on simulators or devices.
Why they fail: End-to-end tests are flaky, slow, expensive to run, and often break due to infrastructure issues rather than app logic.
High maintenance cost: Teams commonly spend 10–20% of engineering time on setup, debugging, and unreliable failures—often with little real value.
What they can be good for: Tracking performance (e.g., startup time) and generating automated screenshots for design review.
Why they don’t catch UI issues: Tests only verify tappability and flow—not layout, appearance, or subtle bugs.
If you must use them: Cache aggressively, learn your tool deeply, and write tests optimized for reliability, not full coverage.
Big picture: For most teams, end-to-end tests provide poor ROI; solid architecture and good communication usually solve the real problems better.
👋 Visit us on https://brainsandbeards.com/