> Markdown version of [/videos/996-why-i-love-end-2-end-tests-and-how-to-get-them-right?t=1331](https://www.wearedevelopers.com/videos/996-why-i-love-end-2-end-tests-and-how-to-get-them-right?t=1331). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Why I Love End-2-End Tests and How To Get Them Right

Outsourcing end-to-end tests to separate QA teams guarantees failure. Shift ownership directly to developers and adopt embarrassment-driven testing to build a lean, ten-minute suite that actually catches bugs.

- **Speakers:** [Johannes Stern](https://www.wearedevelopers.com/@johannes-stern)
- **Event:** World Congress 2024
- **Published:** August 20, 2024
- **Duration:** 23:46
- **URL:** https://www.wearedevelopers.com/videos/996-why-i-love-end-2-end-tests-and-how-to-get-them-right

## Summary

A common failure mode of end-to-end (E2E) testing is outsourcing automation to separate teams, leading to bloated, hours-long test suites that fail constantly and are impossible to run locally. A real-world transition from a massive manual testing effort to an automated environment reveals that retaining broken tests due to sunk cost fallacy only paralyzes deployment. True continuous delivery requires discarding flaky, high-maintenance code in favor of a lean suite that executes in under ten minutes and achieves at least 75% stability.

To get E2E tests right, shift the responsibility from isolated QA silos directly to stream-aligned engineering teams. Writing and maintaining these tests must become a core part of the feature definition of done, factored deeply into planning and execution rather than treated as an afterthought. Shared ownership ensures that every developer can execute and debug E2E tests, breaking the bottleneck of relying on a single test engineer. Furthermore, tests must run hourly and be monitored daily; a red suite demands immediate attention, as "end-to-end tests are of no value if the last green run is eight months ago."

Traditional models like the test pyramid are increasingly challenged by microservice architectures, where integration and E2E tiers often provide a better return on investment than rigid, heavily mocked unit tests that restrict refactoring. Adopting an "embarrassment-driven" testing mindset focuses developer effort on critical user journeys that would be unacceptable to break, such as authentication. High-value testing strategies include writing regression coverage for specific production bugs, actively deleting redundancy across test methodologies, and isolating test scopes—such as emitting a Kafka message directly rather than relying on another team’s volatile downstream service. Ultimately, investing in scalable internal quality leads to fewer production bugs, less deployment pain, and lower developer burnout.

**Keywords:** end-to-end testing, test suite automation, software internal quality, stream-aligned teams, definition of done, continuous delivery pipelines, flaky test mitigation, test pyramid alternatives, microservices integration testing, embarrassment-driven testing, test redundancy reduction, sunk cost fallacy engineering, developer burnout prevention, kafka message testing

## Chapters

1. **Struggling with manual testing in large software systems** (00:03) — Monthly releases bottlenecked by tedious manual spreadsheet testing create the need for test automation.
1. **Failing at test automation with slow and complex suites** (02:12) — Outsourcing test automation can result in unmaintainable suites that take hours to run and require extensive local setup.
1. **Overcoming the sunk cost fallacy to delete broken tests** (06:02) — Discarding expensive but useless test suites is necessary to maintain release velocity and system reliability.
1. **Justifying software testing through internal quality and economic cost** (07:39) — High internal quality significantly lowers long-term development costs and accelerates feature delivery compared to skipping tests.
1. **Assigning end-to-end tests to stream-aligned feature teams** (09:15) — Accountability and reliability improve when the same team builds the features and owns the corresponding end-to-end tests.
1. **Integrating end-to-end tests into the definition of done** (11:01) — Making tests an integrated part of feature deployment ensures they are accounted for in estimations and executed continuously.
1. **Managing instability and execution time in end-to-end tests** (12:34) — Complex dependencies cause fragile test runs that require strict execution time limits and high stability targets to remain valuable.
1. **Moving beyond the traditional test pyramid for microservices** (14:34) — Modern architectures prioritize integration and end-to-end checks over unit tests due to the complexity of service interactions.
1. **Optimizing test return on investment with targeted strategies** (16:57) — Techniques like embarrassment-driven testing and removing redundant checks maximize the practical value of automated suites.
1. **Reducing developer stress and burnout through reliable software testing** (20:09) — Dependable testing frameworks directly reduce deployment anxiety and improve overall job satisfaction as highlighted in industry research.
1. **Core principles for successful end-to-end test implementation** (22:11) — Integrating tests with every feature, sharing ownership, monitoring closely, and focusing on value guarantees continuous delivery success.

## Related Moments

- [Rethinking the testing pyramid and deleting risk-free tests](https://www.wearedevelopers.com/videos/1672-your-testing-strategy-is-broken-lets-fix-it) (from "Your Testing Strategy is broken - lets fix it!")
- [Using test automation as a catalyst for team collaboration](https://www.wearedevelopers.com/videos/1668-how-to-add-test-automation-to-your-project-the-good-the-bad-and-the-ugly) (from "How to add test automation to your project: The good, the bad, and the ugly")
- [Reflecting on the core motivations for writing tests](https://www.wearedevelopers.com/videos/1678-the-2025-state-of-javascript-testing) (from "The 2025 State of JavaScript Testing")
- [Adopting a pragmatic approach to reasonable software engineering tests](https://www.wearedevelopers.com/videos/175-how-not-to-test) (from "How not to test ")
- [Weighing the benefits and tradeoffs of test-driven development](https://www.wearedevelopers.com/videos/114-why-you-must-use-tdd-now) (from "Why you must use TDD now!")
- [Shifting development challenges towards complex testing and team collaboration](https://www.wearedevelopers.com/videos/1459-the-evolving-landscape-of-application-development-insights-from-three-years-of-research) (from "The Evolving Landscape of Application Development: Insights from Three Years of Research")

## Related Articles

- [Integration And E2E Testing: Are They Complementary or Interchangeable?](https://www.wearedevelopers.com/magazine/86-integration-and-e2e-testing-are-they-complementary-or-interchangeable)
- [What is a Test Plan: Guide to Test Planning](https://www.wearedevelopers.com/magazine/191-what-is-a-test-plan-guide-to-test-planning)
- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [The 8 Best Code Testing Tools](https://www.wearedevelopers.com/magazine/402-the-8-best-code-testing-tools)

## Related Jobs

- [Engineer, Offensive Security Organization](https://www.wearedevelopers.com/jobs/ext/1992296-engineer-offensive-security-organization) at **Twilio**
- [Software Tester (f/m/d)](https://www.wearedevelopers.com/jobs/44712-software-tester-f-m-d) at **Power Plus Communications**
- [Test Engineer](https://www.wearedevelopers.com/jobs/ext/1872489-test-engineer) at **ZEISS Group**
- [Staff, Analytics Engineer](https://www.wearedevelopers.com/jobs/ext/569504-staff-analytics-engineer) at **Twilio**
- [Software Tester](https://www.wearedevelopers.com/jobs/ext/1209689-software-tester) at **BWI GmbH**
- [QA Automation Engineer](https://www.wearedevelopers.com/jobs/ext/1414297-qa-automation-engineer) at **Bitpanda**