Cypress Tales: Effective E2E Testing
summary
Cypress runs tests inside a real browser, records time-traveling snapshots and video, and makes debugging fast; tests use a mix of true requests and stubs (use cy.route to stub requests) so most scenarios are integration-level rather than full E2E, yielding much faster suites. Recommended practices shown: use programmatic login via API and Cypress custom commands, reset state in beforeEach, wait for services with start-server-and-test/wait-on for reliable CI, and mount React components for focused checks.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:40Who am I
- 2:17Why test
- 4:00Code Coverage
- 6:00Testing Trophy
- 12:06Cypress Cons
- 13:00Cypress Best Practices
- 14:50Page Object Pattern
- 16:17User Interface
- 16:54Best Practices
- 17:51Starting Web Servers
- 19:28Cypress React
- 23:04Stop Requests
- 25:51Questions
related talks
33mCypress: The future of E2E testing
04mCypress E2E Automation
47mEnd to End Testing with Cypress
29mEnd-to-end Testing Is Hard - But It Doesn't Have to Be
50mShip Web Apps Confidently: End-to-End Testing with Cypress
32mCypress.io – the State of the Art End-to-end Testing Tool
56mCypress: Where Automated Acceptance Testing Isn’t Just for QA Anymore
50mCypress, the Tool That Will Make You Love End-to-End Testing!
