I see your point, but… (Part 2)
summary
Argues for replacing parts of the testing pyramid with Cypress component mounting that runs real DOM components in a real browser, shows adapters for all major frameworks except Angular, and demonstrates snapshot + screenshot diff to make passing builds informative. Records video, network, storage and devtools events to diff a passing run against a failing one so tests explain why a UI changed. Calls out wasted CI spend — about $500 a month on ignored green builds — and shows the approach works end to end.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:23Moving Around The Testing Pyramid
- 2:16Example: React with Enzyme Full rendering Shallow rendering
- 4:49Cypre WEB INTEGRATION TESTS
- 10:13Use same syntax, life cycle and Cypress API
- 10:46Replacing some tests
- 11:47Useful Passing Test: Snapshot testing
- 19:11Test history diff explains WHY the page has changed
- 19:30Record Everything?
related talks
34mI See What is Going on: Visual Testing for Your Components
15mCypress Component Testing - Lightning talk
38mFrontend Tests: what nobody said to you
39mTesting, Testing, 1, 2, NaN
37mTesting the way it should be
40mCypress Component Testing - The Disappearance of Mr. Button
23mGaining Confidence with Cypress Tests
24mScalable Testing Practices for Modern Apps
