Johannes Stern
Why I Love End-2-End Tests and How To Get Them Right
#1about 4 minutes
The story of a failed test automation project
A large-scale effort to automate manual regression tests with an external team resulted in a slow, brittle, and unusable test suite.
#2about 3 minutes
Why the automated end-to-end tests failed
The test suite was doomed by its three-hour runtime, constant failures, and complex local setup requirements, leading to the decision to delete most of them.
#3about 2 minutes
Making the business case for software quality
High internal quality, including robust testing, leads to faster feature delivery over time, making it a cost-effective strategy rather than an expense.
#4about 2 minutes
Why team ownership is crucial for testing
Assigning end-to-end responsibility for features and their corresponding tests to a single team creates accountability and ensures tests are maintained.
#5about 3 minutes
The daily practice of maintaining E2E tests
Successful end-to-end testing requires daily monitoring, debugging complex failure chains, and setting realistic goals for stability and execution time.
#6about 2 minutes
Questioning the test pyramid in modern development
Modern architectures like microservices may benefit from alternative models like the test honeycomb or trophy, which place more emphasis on integration tests over unit tests.
#7about 3 minutes
Focusing on return on investment for tests
Prioritize which tests to write by focusing on their return on investment, using heuristics like fixing production bugs and "embarrassment-driven" testing.
#8about 2 minutes
How good testing improves developer well-being
A solid testing practice reduces production bugs and deployment pain, which directly leads to less stress, less burnout, and higher job satisfaction.
#9about 2 minutes
Four principles for successful end-to-end testing
The core principles for effective testing are to build them with features, ensure team ownership, monitor them closely, and focus on their return on investment.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
07:48 MIN
Why traditional testing methods fail for microservice architectures
Lessons from Our API Past: Evolving to a Resilient API Future
03:48 MIN
Using automation as a catalyst for team collaboration
How to add test automation to your project: The good, the bad, and the ugly
06:22 MIN
The limitations of traditional end-to-end testing
Let's get visual - Visual testing in your project
09:07 MIN
Why traditional testing methods fail to guarantee quality
How will artificial intelligence change the future of software testing?
39:35 MIN
The evolution of testing practices at Chrono24
Write tests you love, not hate
10:30 MIN
Testing is a social and human-centric science
Excellent Software Testing
13:39 MIN
Rethinking the traditional testing pyramid
Your Testing Strategy is broken - lets fix it!
00:05 MIN
Setting the stage for a test automation project
How to add test automation to your project: The good, the bad, and the ugly
Featured Partners
Related Videos
56:49Write tests you love, not hate
Jens Happe
28:12Your Testing Strategy is broken - lets fix it!
Luise Freese
26:20How to add test automation to your project: The good, the bad, and the ugly
Augustin Gottlieb
43:07How not to test
Golo Roden
47:22Continuous testing - run automated tests for every change!
Christian Kühn
24:19It's a (testing) trap! - Common testing pitfalls and how to solve them
Ramona Schwering
21:39Unveiling the Dark Side: Navigating the Pitfalls of Digital Ambitions
Johannes Hansen
26:02Contract Testing - How do you tame an external API that constantly breaks your tests
Vincent Hennig & Anupam Krishnamurthy
Related Articles
View all articles
.gif?w=240&auto=compress,format)
From learning to earning
Jobs that call for the skills explored in this talk.
Informatiker als Technischer Product Owner Test Automation
E.ON
GIT
Gitlab
Jenkins
Continuous Integration
Informatiker als Technischer Product Owner Test Automation
E.ON
GIT
Gitlab
Jenkins
Continuous Integration