It's a (testing) trap! - Common end-to-end pitfalls and how to solve them
summary
Concrete examples of failing front-end tests, the mistakes that cause them, and concrete fixes: uses Jest and Cypress as examples, shows unclear short titles and adopts the three-part title rule, restructures tests with given–when–then / arrange‑act‑assert, warns against shared test data and fragile CSS selectors, and demonstrates replacing fixed waits with dynamic waits or network intercepts and using data- selectors for stability. Expect code-level patterns, specific assertions to add, and measurable outcomes (fewer flakes, faster runs).
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:25Personal testing journey
- 5:12Star Wars testing pain
- 7:00End-to-end pitfalls
- 9:06Mindset and simplicity
- 10:12Clear test titles rule
- 12:19Unit test structure
- 14:25Unit test readability
- 16:33Pattern adaptation
- 19:04End-to-end testing and its unique challenges
- 20:14Avoid shared data
- 22:21Realistic test names
- 23:48Avoid implementation traps
- 25:34Fixed wait dangers
- 27:41Turning pain to success
- 28:45Final thoughts
related talks
19mIt's a (Testing) Trap! - Common Testing Pitfalls and How to Solve Them
23mIt's a Testing Trap
39mTesting, Testing, 1, 2, NaN
21mTests That Help you Find Defects Faster
38mFrontend Tests: what nobody said to you
42mSurviving the JS Testing Tools Jungle
32mOld solutions to new testing problems
38mHow to Stop Hating Tests with Jest, Supertest and Cypress