mobile-testinglisted

# Mobile Testing ## Responsive/mobile-web testing (most common in this harness) - Use Chrome DevTools MCP `emulate`/`resize_page` or Claude in Chrome to test key breakpoints: 375px (small phone), 414px (large phone), 768px (tablet), plus the actual design breakpoints if known. - Check touch target size (min ~44×44px) — mouse-precision UI often ships touch targets too small to tap reliably. - Check for hover-dependent functionality that has no touch equivalent (tooltips, hover menus). - Test both orientations (portrait/landscape) if the app doesn't lock orientation. - Test with the mobile viewport's actual user-agent, not just a resized desktop window — some sites serve different code paths by UA. ## Native app testing (iOS/Android) - **Device/OS matrix**: pick a representative spread — oldest supported OS version, newest, one low-end device (perf-constrained), one high-end. Don't test only on the simulator/emulator; real-device testing catches sensor, permissions-dialog, and performance issues simulators miss. - **Lifecycle testing**: backgrounding mid-flow (payment, upload) and resuming, force-quit and relaunch (state restore correctness), low-memory termination behavior, incoming call/notification interruption. - **Network conditions**: airplane mode mid-request, flaky/slow 3G simulation, switching wifi→cellular mid-session — does the app recover gracefully or lose state/crash? - **Permissions**: test both grant and deny paths for every permission (camera, location, notif