Don’t Believe the Rumors Writing Tests for CSS is Possible
summary
Claims that visual regression testing can make CSS changes safe and shows a workflow that actually works: use Cypress or Puppeteer (or webdriverIO/selenium for cross‑browser) plus Applitools or jest-image-snapshot to capture a baseline image and fail on diffs, then triage failures. Covers four practical hurdles—full‑page vs viewport vs selector screenshots, noisy pixel diffs and tolerance sliders, GUI or workflow for accepting baselines, and running across viewports/browsers (parallel runs or cloud DOM snapshot render farms). Tests run, surface bugs, and baselines are updated when features change.
AI-written summary · about
chapters (6)
- 0:00The developer's fear
- 2:23Adopting testing culture
- 7:32The challenge of CSS testing
- 12:05How visual testing works
- 16:52Overcoming the four elephants
- 27:10Conclusion and closing
related talks
26mDon’t Believe the Rumors: Writing Tests for CSS is Possible
27mWriting Tests For CSS Is Possible! Don’t Believe The Rumors
42mAutomated CSS Testing
27mVisual UI Testing – Testing the Last Mile
18mImplementing a Visual CSS Testing Framework
30mImplementing a Visual CSS Testing Framework
30mLet's Test Our CSS!
04mCSS tests