Stop Using the Console to Test Components
summary
Argues that using jsdom and Jest to test UI components in Node.js is inadequate, explains why jsdom is problematic, and proposes more reliable alternatives. Shows how Cypress.io approaches component testing differently and previews a hands-on workshop demonstrating that approach.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:13Workshop overview
- 3:41Live Cypress coding
- 15:51Testing Date Picker in React
- 31:45Native events and accessibility
- 41:21CircleCI parallel tests
- 51:35Reports and visual testing
- 1:00:45Summary and Q&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
45mCypress: Testing without Selenium, Part 1
09mElemental Testing My Dear Watson - Unit Tests for UI Components
14mHow to Test Components – It Doesn’t Need to All Be E2E Tests