The 2025 State of JavaScript Testing
summary
Survey data shows mocking is the top pain, 62% of companies use Jest + React Testing Library (Storybook common) and 13% report no tests; eight company cases reveal one surprising pattern: static analysis (TypeScript/ESLint/Yes) is now treated as testing. Tool shifts: Vitest + Vite enable browser-mode component testing replacing slow JSDOM workflows, costing ~2–3s per run but removing many mocks; Playwright dominates end‑to‑end with built‑in visual, API and accessibility features, and MSW is the de facto network‑mocking solution.
AI-written summary · about
chapters (11)
- 0:00Introduction and Purpose of Testing
- 0:45Common Testing Pain Points
- 1:40Survey Insights and Tool Usage
- 4:06Case Studies on Testing Practices
- 6:37The Evolution of Testing Tools
- 7:37Static Analysis and Unit Testing
- 8:38Integration and Component Testing
- 17:53End-to-End Testing Trends
- 20:12Mocking and Network Interception
- 21:44AI in Testing
- 26:56Conclusion and Key Takeaways
related talks
15mComponent Testing in 2026: The Return of the Browser
42mSurviving the JS Testing Tools Jungle
27mTesting in 2024
32mTesting React apps like it’s 2026
29mTest Like It's 2017
39mTesting, Testing, 1, 2, NaN
25mBuilding High-Quality JavaScript Tools
31mGreat Expectations – Understanding nodejs Testing Frameworks