mobile-testing

The mobile-testing skill provides a structured, AI-driven framework for ensuring high-quality mobile application delivery. Designed for QA engineers and developers working on native, hybrid (React Native, Flutter), and mobile web applications, this skill orchestrates complex testing workflows across diverse mobile environments. It emphasizes a hybrid execution strategy, balancing the speed of emulators with the precision of real-device testing for critical application paths. By leveraging the fleet of specialized agents like qe-test-executor, qe-performance-tester, and qe-visual-tester, it manages the inherent challenges of mobile development, such as OS version disparities and hardware fragmentation.

• Automated device coverage matrix generation based on Tier 1 (60%), Tier 2 (30%), and Tier 3 (10%) user distribution.

• Advanced interaction validation for touch gestures including tap, swipe, pinch, and long-press actions.

• Specific mobile scenario testing for offline modes, low battery, network transitions, and sensor-based inputs like geo-location.

• Automated permission flow testing for Android and iOS, handling native system dialogs and runtime requests.

• Platform-aware test execution that accounts for differences in navigation, hardware buttons, and app store compliance requirements.

• High-performance execution through device farm integration with providers like BrowserStack.

• Input requirements include target platforms, chosen device tiers, and specific test suites; outputs provide detailed execution reports, video recordings, and network logs.

• Use the mobile-testing skill when preparing for app store submissions, regression cycles, or performance benchmarking on flagship mobile devices.

• Always prioritize real-device testing for critical user flows to capture nuances in hardware performance and sensor sensitivity that emulators might miss.

• Integrate with other specialized QE skills such as accessibility-testing for VoiceOver/TalkBack support or performance-testing for detailed latency analysis.

• Remember that Android fragmentation is the primary technical challenge; structure your device matrix to cover a broad spectrum of manufacturers and OS versions to ensure robustness.