Strategy & Success with Adopting Cypress Component Testing
summary
Extend adopts Cypress component testing across apps, growing from 79 component specs to 346 and converting about a quarter of Enzyme/RTL unit tests into components. Migrations use custom mounts, Cypress intercept and Storybook combinatorial models, reducing flaky mocks and maintenance. Performance tuning cuts test startup from ~20s to ~1s and switching bundlers with V drops cold starts from ~2 minutes to ~8 seconds. Surveyed UI engineers report faster feedback loops and easier debugging with visual, in-browser component tests.
AI-written summary · about
chapters (10)
- 0:00Introduction to Cypress component testing
- 1:49Becoming an expert in component testing
- 3:33Extent’s adoption journey
- 8:26Change curve and early adopters
- 9:49Kano model for feature adoption
- 12:34Custom mounts for simplicity
- 15:24Reducing mocking with intercept
- 16:47Migrating from Webpack to Vite
- 19:11Survey results from extent engineers
- 22:47Key takeaways and future outlook
related talks
38mFrontend Tests: what nobody said to you
24mScalable Testing Practices for Modern Apps
25mUsing Cypress to improve Test Reusability
15mCypress Component Testing - Lightning talk
56mCypress: Where Automated Acceptance Testing Isn’t Just for QA Anymore
47mEnd to End Testing with Cypress
22mIncreasing our test stability and reliability with Cypress
30mIntroducing Component Testing with Cypress