Sparround

DevTools & mobile testing basics

Chrome DevTools is the manual QA's daily tool:

  • Network — API calls, status codes, response times, HAR export (for bug reports)
  • Console — JS errors (always attach to bug reports)
  • Elements — root causes of UI issues (CSS/DOM)
  • Device toolbar — responsive checks, throttling (slow network simulation)
  • Application — cookies, localStorage, session

Mobile testing specifics (vs web): interruptions (calls, push, low battery), network transitions (WiFi ↔ mobile data ↔ offline), permissions, diverse screen sizes/OS versions, app lifecycle (background/foreground, kill and restore).

Environment matters even more in mobile bug reports: device model, OS version, app version/build number and network type are mandatory — the same bug may exist on iPhone 12/iOS 17 but not on iPhone 15/iOS 18.

📚 Sources and documentation