• Mobile app/web feature must be validated across devices and OS versions.
• Crash, layout break, or gesture-related issues are reported.
• Team needs confidence in network, lifecycle, and permission behavior.

• Validate mobile behavior across device capability and usage context.
• Detect issues in compatibility, performance, and interaction consistency.
• Provide release risk view specific to mobile platform constraints.

1. Define device matrix by user share, OS version, and hardware class.
2. Cover install/update, login, key journeys, and background/foreground transitions.
3. Test network switches, offline/weak network, and interruption events.
4. Validate gesture, orientation, and permission flows.
5. Capture device-specific defects with reproducible context.
6. Report compatibility coverage and residual risk by device tier.

Input:

• Scope: checkout on Android 12/13 and iOS 17 under weak network

Output:

• Found duplicate submission on reconnect scenario (Android)
• Found keyboard overlap in coupon input (iOS)
• Device-tier risk summary and fix priority

Input:

• "Test app on one phone"

Output (problem):

• Single-device result used as global conclusion
• Major compatibility risks remain hidden

• Do not generalize from one device result.
• Do not skip lifecycle/interruption scenarios.
• Do not ignore permission and system-setting impacts.
• Do not report mobile quality without device matrix context.
• Do not close verification before high-share devices pass.