Responsive QA is about behavior
A responsive page should not only fit the screen; it should preserve the user journey. I test whether navigation remains reachable, forms remain readable, buttons are easy to tap, and content keeps a clear order.
For projects like CMS storefronts, college forms, and animated company pages, responsive QA needs both layout checks and workflow checks.
Viewport set I like to cover
- Small mobile around 360 to 390 px width.
- Large mobile around 430 px width.
- Tablet around 768 px width.
- Laptop around 1366 px width.
- Wide desktop around 1440 px and above.
Common defects to look for
- Horizontal overflow caused by long words, cards, tables, or menus.
- Sticky headers covering anchor targets or form fields.
- Cards with uneven heights that hide calls to action.
- Images cropped so the important subject disappears.
- Hover-only interactions that do not work on touch devices.
Cross-browser evidence
When a defect appears only in one browser, the report should include browser name, version, operating system, viewport size, and a screenshot. That detail helps separate a product bug from a rendering difference or unsupported behavior.