Don’t Believe the Rumors: Writing Tests for CSS is Possible
summary
Claim: writing tests for CSS is possible. Practical setup uses Cypress plus visual plugins (one-liner matchImageSnapshot) or cloud services like Applitools. Workflow captures DOM and CSS, creates a baseline screenshot, then compares new screenshots across viewports and browsers; diffs require human accept/reject. Four core problems—taking reliable screenshots, robust comparison beyond pixel-by-pixel, managing approvals, and scaling responsive/browser matrices—have concrete solutions: smarter comparison algorithms, DOM-based snapshots, dashboards or automated acceptance flows, and cloud-parallel rendering.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:45What kind of web developers are there
- 3:05Why are we writing tests
- 6:28Who is writing the tests
- 7:55How to write tests for CSS
- 9:08Visual vs functional testing
- 10:21Visual regression testing
- 16:08The Answer
- 19:34Demo
related talks
29mDon’t Believe the Rumors Writing Tests for CSS is Possible
27mWriting Tests For CSS Is Possible! Don’t Believe The Rumors
42mAutomated CSS Testing
30mLet's Test Our CSS!
30mImplementing a Visual CSS Testing Framework
04mCSS tests
18mImplementing a Visual CSS Testing Framework
31mWriting (Really) Good Tests