Stop Using the Console to Test Components
summary
The talk argues against using jsdom/Jest in Node.js for UI component testing and explains why jsdom is insufficient. It surveys more reliable alternatives to jsdom and demonstrates, via a workshop, how Cypress.io approaches component testing differently in practice.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:05Console limits for components
- 11:27Jest DOM limits
- 29:56Shallow rendering issues
- 36:39Jest DOM vs Karma
- 44:42Ideal tool requirements
- 51:47SayPress solution
- 59:35Browser tests in SayPress
- 1:02:47Q&A
related talks
15mComponent Testing in 2026: The Return of the Browser
15mCypress Component Testing - Lightning talk
19mWhy you should Jest use Cypress for React component testing
39mTesting, Testing, 1, 2, NaN
40mCypress Component Testing - The Disappearance of Mr. Button
42mSurviving the JS Testing Tools Jungle
45mCypress: Testing without Selenium, Part 1
14mHow to Test Components – It Doesn’t Need to All Be E2E Tests