End to End Testing: The Game Has Changed
summary
Claims that end-to-end testing shifts from remote drivers to an in-process JS runtime, replacing Selenium Webdriver with Cypress to cut flakiness and tool churn. Shows direct DOM access, built-in time travel via DOM snapshots, replayable command logs, and native single-process debugging. Notes tradeoffs: single-tab execution and limited early browser support, but reports rapid setup, fewer intermittent failures, and concrete developer productivity gains when hundreds to thousands of tests exist.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 0:51How to test your frontend
- 5:35The problem with selenium
- 6:59Why do we keep testing
- 8:33Selenium
- 9:30Cypress
- 11:08Opening Cypress
- 11:52BDD Style
- 14:24Running Tests
- 14:48Recording Tests
- 14:59Electron App
- 15:24Browser
- 15:40Test Runner
- 16:10Selector Playground
- 16:33Command Log
- 18:28Debugging
- 19:36Replayability
- 20:33Other nice things
- 21:48Performance tradeoff
- 22:42Tradeoffs
- 24:37Ambitious
- 25:41The Game Has Changed
- 26:01Write a Smoke Test
- 26:47Dont let your users test
- 27:16Wills thoughts on JavaScript
- 28:23Wills thoughts on Cypress
- 29:03Wills personal story
- 29:51Outro
related talks
29mEnd-to-end Testing Is Hard - But It Doesn't Have to Be
47mEnd to End Testing with Cypress
50mShip Web Apps Confidently: End-to-End Testing with Cypress
53mModern Web Testing: Going Beyond Selenium
36mModern Web Testing: Going Beyond Selenium
41mEnd-2-end testing without the pain
30mModern Web Testing: Going Beyond Selenium
37mTesting the way it should be