It's a (Testing) Trap! - Common Testing Pitfalls and How to Solve Them
summary
Frontend tests often become slow, flaky, or painful to maintain, and the concrete fixes are: follow the golden rule—keep tests obvious; structure tests with the three part rule or AAA; stop using fixed waits and use Cypress features to wait for UI changes or API requests; avoid brittle CSS selectors in favor of data attributes; use realistic names or faker for test data. The talk lists three pain points and shows working Cypress examples.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:21Biggest Failures
- 6:47Golden Rule
- 9:29Three Part Rule
- 11:23Structure Your Tests
- 12:32Fubar
- 15:49Fixed Waiting Time
- 17:46The Golden Rule
related talks
30mIt's a (testing) trap! - Common end-to-end pitfalls and how to solve them
23mIt's a Testing Trap
38mFrontend Tests: what nobody said to you
13mDon't Get Lost in the Trees: An Intro to Cypress
15mHow to (not) write a flaky test
32mHow to write a flaky test
46mFilip Hric: How to Write a Flaky Test Description: How (not) to Write a Flaky Test
26mEffective DOM selector patterns. Interact like a user