Component Testing in 2026: The Return of the Browser
summary
Project moves from Jest + jsdom back to real browsers because many DOM interactions and visuals fail silently in jsdom. The migration uses vtest browser mode or Playwright-driven pages, keeps tests on CI, and switches mocking to component-level rather than full API fixtures. Visual asserts target specific regions to avoid pixel drift; layout suites run fast — an example suite renders 110 widgets in 7.7s — and Cypress/Storybook remain options for story-based checks.
AI-written summary · about
related talks
19mWhy you should Jest use Cypress for React component testing
01h 11mStop Using the Console to Test Components
27mTesting in 2024
36mModern Web Testing: Going Beyond Selenium
38mModern Web Testing: Going Beyond Selenium
20mComponent Testing with Playwright
39mTesting, Testing, 1, 2, NaN
37mTesting the way it should be