Testing Angular apps with Cypress in CI
summary
Argues end-to-end tests catch integration bugs unit tests miss and shows a working setup: Angular CLI scaffolds Cypress, tests run headless and in GUI, and CI uses an official GitHub Actions integration. Demo produces 3 passing 1 failing tests and surfaces failing-state screenshots and videos so CI artifacts explain why. Also shows generated test code from the Cypress GUI and how ng e2e updates package.json angular.json and a cypress folder so the pipeline actually runs.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:51E2E tests matter
- 10:23Requirements over coverage
- 17:48Angular’s E2E evolution
- 19:32What is Cypress
- 21:48Cypress in Angular
- 23:33Writing Cypress tests
- 26:54Debugging failures
- 28:39Cypress GUI exploration
- 32:15Q&A
related talks
20mAmazing E2e testing experience with Cypress and Angular
31mTesting Angular with Cypress.io
44mAutomation Testing Web Apps with Cypress
23mGaining Confidence with Cypress Tests
23mGaining Confidence with Cypress Tests
42mStrategy for Automation Testing Using Cypress.io
39mGaining Confidence with Cypress Tests
47mEnd to End Testing with Cypress