Avoiding The Suck Of Testing Using Cypress.io
summary
Claims that Protractor/Selenium-style end-to-end testing is flaky and slow and demonstrates switching to Cypress.io by installing, running npx cypress open, and writing tests that use cy.visit cy.get and should to assert DOM state. Shows waiting for network with cy.route & cy.wait, stubbing responses and fixtures to force edge cases, running tests in CI and capturing videos and screenshots. The demos run live and all features work as shown.
AI-written summary · about
chapters (12)
- 0:00Introduction to cypress
- 1:18The pain of E2E testing
- 2:45Why testing tools fail
- 5:29Setting up cypress
- 6:57Your first cypress test
- 12:30Understanding the UI
- 16:26Hands-on exercise
- 20:05Solving test flakiness
- 25:55Network waiting and routing
- 33:02Stubbing and edge cases
- 38:42Fixtures and exercises
- 41:57CI mode and conclusion
related talks
47mEnd to End Testing with Cypress
23mRun your end-to-end tests at light speed with Cypress
23mGaining Confidence with Cypress Tests
45mCypress: Testing without Selenium, Part 1
57mGaining Confidence with Cypress Tests
50mCypress, the Tool That Will Make You Love End-to-End Testing!
32mGaining Confidence with Cypress Tests
39mGaining Confidence with Cypress Tests