Do Not Fight Your Testing Tools
summary
Shows how to stop fighting async by using real tools: Node.js test runner, Playwright and Cypress for web tests, and Replay.io time-travel debugging to step through CI runs statement by statement. Describes converting DOM elements into pipelines so assertions retry cleanly, compares Cypress’s command log snapshots with Playwright’s UI mode, reports running ~720 tests daily, and predicts tooling that automatically explains failures by comparing current run traces to prior successful runs.
AI-written summary · about
chapters (15)
- 0:00Introduction and climate call
- 1:12Developer experience and testing
- 3:20JavaScript’s unholy hybrid nature
- 6:12Async programming challenges
- 9:02Promises and async/await
- 10:03Testing static and dynamic pages
- 12:56The problem with async/await sugar
- 15:46Why sugar is bad for testing
- 16:50Choosing the right testing tool
- 19:39Imperative vs reactive testing
- 22:05Speed vs debugging in tests
- 23:10Cypress debugging features
- 25:18Replay.io time-travel debugger
- 28:27Future predictions for testing
- 30:33Capturing and using test data
related talks
51mCypress, Playwright or Selenium: choosing the right testing tool
29mEnd-to-end Testing Is Hard - But It Doesn't Have to Be
46mTest Automation with Selenium, Cypress, and Playwright
50mShip Web Apps Confidently: End-to-End Testing with Cypress
43mLessons from E2E Testing Web Applications with Avindra Fernando
57mGaining Confidence with Cypress Tests
35mCypress Tales: Effective E2E Testing
51mAdvanced Playwright Techniques for Flawless Testing