Frontend Tests: what nobody said to you
summary
Tests often give false confidence and fixing that required concrete changes: split tight components, add boundaries, prefer component snapshots and Cypress for integration, and parallelize CI to cut slow suites. A quick-search widget causes repeated DOM mounts and extra API calls, so a feature toggle component was built for Angular and React to gate rollout. Coverage rises from 8% to 83% after focused risk-driven tests. Use Cypress for replayable browser debugging and snapshots for fast assertions.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:51From manual to automated tests
- 8:20Test pyramid explained
- 13:43Modernizing frontend testing
- 21:02Writing meaningful tests
- 25:29Testing CSS and snapshots
- 26:57Cypress integration testing
- 30:10Refactoring with confidence
- 34:59Metrics and transparency
- 37:08Closing and resources
related talks
39mGaining Confidence with Cypress Tests
57mGaining Confidence with Cypress Tests
24mStrategy & Success with Adopting Cypress Component Testing
53mModern Web Testing: Going Beyond Selenium
45mCross-Framework Testing in MFs
39mMastering UI tests
49mFrontend Testing: Mapping Out the Territory
23mGaining Confidence with Cypress Tests