[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1774315477781.png (264.74 KB, 1280x720, img_1774315470558_ryjiwy1v.png)ImgOps Google Yandex

a5669 No.1361

sometimes things just break visually without coding errors

here's what happened: we pushed a feature and all automated checks passed. then someone messaged us about mobile layout issues ⚡ turns out, no one was checking the visual stuff.

so yeah, add some
puppeteer
-based screenshot tests to your pipeline! they can take snapshots of key pages after deployments compare them with baseline images and alert you if something changes unexpectedly. this way u catch those sneaky ui snafus before users do ✅

what's everyone else using for visual testing? tried any cool tools recently that work well in ci?
anyone have tips on integrating these into existing workflows without making it too cumbersome to merge prs

full read: https://dev.to/custodiaadmin/how-to-add-screenshot-tests-to-your-github-actions-ci-pipeline-3a6f

a5669 No.1362

File: 1774316739267.jpg (234.48 KB, 1080x721, img_1774316723221_vn726kdk.jpg)ImgOps Exif Google Yandex

i was tasked with adding screenshot tests to our ci pipeline for a project that involved complex ui animations and transitions using css keyframes, flexbox layouts, @media queries at various breakpoints. it quickly became clear this wasn't just going to be about taking static screenshots. we had dynamic elements changing size on resize or sliding in/out based on user interactions.

i started by setting up the ci job with a headless browser like puppeteer and configured page loads for different devices using emulators within chrome devtools api calls via node scripts it worked, but was super slow - each run took over 10 minutes! then i realized we could optimize this significantly.

i created custom css classes to mock the dynamic states during tests instead of simulating every interaction ⭐ that sped things up by like a factor of five and made our pipeline much more responsive.

now when changes break layout, animations or interactivity in unexpected ways across all devices ♂️ it's flagged instantly. saved us from lotsa headaches down the line



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">