Why Playwright Beats Jest and Vitest Slows Down: Measuring Coverage Like a Pro
summary
Explains how to measure JavaScript code coverage using Playwright, compares Playwright coverage workflows to Jest and Vitest (claiming Vitest is slow), and shows techniques to speed up Playwright and Jest tests. Describes how to merge coverage outputs from multiple test runs into a single report.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:10Test coverage importance
- 3:58Vitest/Jest instrumentation
- 8:11Coverage alternatives
- 12:34Istanbul/Babel limits
- 16:09V8 coverage in Playwright
- 19:22Playwright coverage
- 21:37Merging coverage data
- 24:07Coverage report tools
- 25:32CI/CD with GitHub Actions
- 28:21GitHub coverage comments
- 31:55Optimizing Jest/Vitest
- 36:12Playwright vs frameworks
- 38:45Why Vitest is slower
- 39:26Results and summary
related talks
32mPlaywright Component Tests: Are they the Testing-Library killer?
51mAdvanced Playwright Techniques for Flawless Testing
26mWe May Not Need Component Testing
31mGreat Expectations – Understanding nodejs Testing Frameworks
14mAdvanced Playwright Techniques for flawless testing
28mTesting Web Applications with Playwright
13mComponent Testing with Playwright for Vue
51mTesting Web Applications with Playwright