responsive-qa

Responsive QA tests pages across 9 standard viewports including phones, tablets, laptops, and desktops, capturing screenshots and running layout-health checks to generate a consolidated report with per-viewport artifacts.

Automated viewport emulation for frontend QA uses Chrome DevTools to script viewport resizing, capturing screenshots and detecting layout issues like overflow, overlap, and touch target violations to ensure pages render correctly.

You can check for overflow and truncation issues by running layout-health checks via viewport emulation, which captures per-breakpoint screenshots and flags visibility, overlap, and touch target anomalies.

Yes, Chrome DevTools MCP supports standalone responsiveness checks by scripting viewport emulation to test pages across common devices, capturing screenshots and producing per-viewport layout-health reports.

Responsive testing works with Feature Builder pipeline pages for both dweb and mweb, applying viewport emulation and layout-health checks to ensure correct rendering across standard breakpoints.

The best way to automate regression checks after design QA passes is to run scripted viewport emulation across standard breakpoints, generating consolidated reports and per-viewport screenshots to detect layout regressions.