QA guide · Mobile web
Mobile web QA checklist: responsive behavior, input and real-device risk
Responsive testing is more than shrinking the browser window. Use emulation for fast coverage, then remember that emulation is only an approximation of a real mobile device.
Fast browser pass
- Test narrow and wide viewports; look for clipping, overflow and unreachable controls.
- Check portrait and landscape layouts.
- Verify tap targets, sticky headers, menus, dialogs and fixed-position elements.
- Test forms with realistic text lengths and validation errors.
- Check zoom and text resizing; important content should remain usable.
Performance and environment pass
- Use Chrome DevTools device mode to approximate mobile viewport behavior.
- Throttle network/CPU to expose loading and interaction problems.
- Test offline/error states if the product promises resilience.
- Remember: device emulation does not execute your code on an actual phone.
Evidence fields for mobile bugs
Viewport/device: Orientation: Browser/version: Network condition: Input method: Steps: Expected: Actual: Screenshot/video: Reproduces on real device? yes / no / not checked
Practice task
Open the QA Lab at two viewport widths. Find one responsive/usability issue and report the exact viewport, orientation, expected layout and evidence.
Ferramenta gratuita
Revise a qualidade do seu bug report antes de enviar.
O QA Evidence Generator roda localmente no navegador, dá um score determinístico de completude, aponta lacunas e exporta Markdown ou HTML pronto para PDF.
Practice it
Use a real browser exercise, not only a definition.
The QA + Security Bug Hunt Lab gives you a self-contained storefront with intentional findings, reporting templates, scoring and an answer key.
Open the QA Lab on Gumroad ↗