Automated Testing for the Modern Web
summary
Cypress.io executes tests inside the browser and directly in the app’s run loop so tests can access application objects, call methods and inspect and time-travel at the failing step. It observes and can alter XHR traffic in real time, avoids webdriver’s stateless HTTP hops that cause flake, and ships as an npm package you run with cypress open. The bundled stack includes Mocha, Chai and Sinon, supports Chrome and Electron in the demo, and re-runs tests on file change.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker background
- 1:13What is browser automation
- 2:41History of browser automation
- 5:11WebDriver architecture explained
- 7:47Real-world WebDriver example
- 10:26Challenges with WebDriver
- 11:10Stateless vs stateful testing
- 14:23Debugging difficulties in WebDriver
- 15:51Complex setup of WebDriver
- 16:55Cypress architecture differences
- 19:31Live demo of Cypress
- 27:41Debugging with Cypress
- 28:03Closing and call to action
related talks
45mCypress: Testing without Selenium, Part 1
54mCypress: Your Automated Sous Chef
50mShip Web Apps Confidently: End-to-End Testing with Cypress
47mCypress — Charm and Ease
33mCypress: The future of E2E testing
50mCypress, the Tool That Will Make You Love End-to-End Testing!
47mEnd to End Testing with Cypress
56mCypress: Where Automated Acceptance Testing Isn’t Just for QA Anymore