Documenting application behaviours with E2E tests
summary
Claims that test behavior not implementation is the guiding principle, and demonstrates using Cypress commands and retries to write reliable E2E specs against a TodoMVC app. Shows concrete steps: reinitialise the backend from the browser, stub XHRs, record DOM snapshots, share class-name constants with the app, and use page objects as executable docs. Tests run inside the Cypress runner with TypeScript, most pass and failures are debuggable, and the suite serves as living documentation rather than brittle implementation checks.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:47Test behaviour not implementation
- 1:34Test purpose
- 1:54User interface
- 2:31Cypress
- 3:57Demo
- 10:44Example application
- 11:42Starting tests
- 14:59Page objects
- 15:55Behavior vs implementation spec
- 17:09Converting spec into tests
- 19:09Debugging
- 19:44New introduced
- 22:39Item behaviour
- 25:04Testing state resistance
- 25:44Editing items
- 27:08Testing
- 32:04ToggleAll
- 35:37Counter
- 37:48ClearCompleted
- 39:55Console
- 47:11Sharing code
- 49:37Interview
related talks
35mCypress Tales: Effective E2E Testing
39mGaining Confidence with Cypress Tests
20mAmazing E2e testing experience with Cypress and Angular
20mIntegration Testing with Cypress
23mGaining Confidence with Cypress Tests
33mCypress: The future of E2E testing
43mLessons from E2E Testing Web Applications with Avindra Fernando
44mAutomation Testing Web Apps with Cypress
