{"href":"https://api.simplecast.com/oembed?url=https%3A%2F%2Fpodcast.brainsandbeards.com%2Fepisodes%2Fbbs-22-are-e2e-tests-just-burning-money-LvbKvgdB","width":444,"version":"1.0","type":"rich","title":"BBS 22: Are E2E Tests Just Burning Money?","thumbnail_width":300,"thumbnail_url":"https://image.simplecastcdn.com/images/9700d319-c3b0-4ab4-8607-3b3fff3771f0/781c93cd-6e94-4afd-a215-116f33f2819a/brains-20and-20beards-20show-20artwork-209000.jpg","thumbnail_height":300,"provider_url":"https://simplecast.com","provider_name":"Simplecast","html":"<iframe src=\"https://player.simplecast.com/cc1e178f-51c0-4832-a88d-7ffe54d0c77c\" height=\"200\" width=\"100%\" title=\"BBS 22: Are E2E Tests Just Burning Money?\" frameborder=\"0\" scrolling=\"no\"></iframe>","height":200,"description":"In this episode of Brains & Beards, Patryk and Wojciech dive into why end-to-end tests often feel like “burning money” for mobile teams. They challenge the assumption that end-to-end tests provide reliable UI validation, arguing instead that they are expensive, flaky, and rarely catch meaningful issues. The hosts explain why UI-driven flows break easily, why maintenance costs balloon, and why the return on investment is often low except in specific cases such as performance tracking or automated screenshot generation for design reviews. They wrap up with pragmatic strategies for teams forced to use end-to-end tests and make the case that thoughtful architecture—and good communication—usually yield better results."}