mcpField
M
mobile-testing

mobile-testing

github.com/proffesor-for-testingTesting & quality520171 installsUpdated 1d ago
Repository

About mobile-testing

A mobile application testing skill for teams validating iOS, Android, hybrid, and mobile web apps. It organizes device coverage and platform-specific checks, including gestures, connectivity, permissions, and interruptions.

Key features

  1. 01Device coverage matrix planning
  2. 02iOS and Android difference checks
  3. 03Touch gesture validation
  4. 04Offline and interruption scenarios
  5. 05Real-device and emulator guidance

Use cases

  1. 01Plan device coverage for mobile releases
  2. 02Test platform-specific navigation and permissions
  3. 03Validate gestures and offline behavior
  4. 04Prepare mobile apps for store submission

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill mobile-testing

After installing, type/mobile-testingin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

evals/
mobile-testing.yaml
schemas/
output.json
scripts/
validate-config.json

Details

From the project README

Mobile Testing

<default_to_action> When testing mobile applications:

  1. DEFINE device coverage matrix (Tier 1: 60%, Tier 2: 30%, Tier 3: 10%)
  2. TEST platform differences (iOS ≠ Android: back button, permissions, UI)
  3. VALIDATE touch gestures (tap, swipe, pinch, long-press)
  4. TEST mobile-specific scenarios (offline, low battery, interruptions)
  5. USE real devices for critical paths, emulators for fast feedback

Quick Mobile Checklist:

  • Test on latest iOS + Android flagship devices
  • Test offline mode and network transitions
  • Verify push notifications work
  • Test gesture interactions (swipe, pinch)
  • Check permissions flow (camera, location, notifications)

Critical Success Factors:

  • Emulators for 80% of testing, real devices for 20% critical paths
  • Test on devices your users actually use (analytics)
  • Device fragmentation is Android's biggest challenge </default_to_action>

Quick Reference Card

When to Use
  • Native app development (iOS/Android)
  • Hybrid apps (React Native, Flutter)
  • Mobile web / PWAs
  • App store submission preparation
iOS vs Android Differences
AspectiOSAndroid
OS Versions2-3 supported10+ in use
Devices~40 models1000+ variants
Back ButtonGesture/navHardware/software
PermissionsSingle promptRuntime granular
App StoreStrict reviewGoogle Play + sideload
Device Coverage Tiers
TierCoverageDevices
Tier 160% usersiPhone 15, Galaxy S24, iPad
Tier 230% usersiPhone 14/13, Pixel 8
Tier 310% usersOlder devices, other manufacturers

Mobile-Specific Scenarios

// Offline mode testing
test('app works offline', async () => {
  await driver.toggleAirplaneMode();

  await driver.findElement('view-saved-items').click();
  const items = await driver.findElements('saved-item');
  expect(items.length).toBeGreaterThan(0);

  const banner = await driver.findElement('offline-banner');
  expect(banner.getText()).toContain('No internet');

  await driver.toggleAirplaneMode(); // Restore
});

// Location testing
test('location-based features', async () => {
  await driver.setGeoLocation({
    latitude: 37.7749,
    longitude: -122.4194,
    altitude: 0
  });

  const stores = await driver.findElement('stores-list');
  expect(stores.getText()).toContain('San Francisco');
});

// Permission testing (Android)
test('camera permission flow', async () => {
  await driver.findElement('take-photo').click();

  // Handle permission dialog
  await driver.findElement(
    'com.android.packageinstaller:id/permission_allow_button'
  ).click();

  expect(await driver.findElement('camera-view')).toBeDefined();
});

Agent-Driven Mobile Testing

// Cross-platform mobile testing
await Task("Mobile Test Suite", {
  platforms: ['iOS', 'Android'],
  deviceTiers: [1, 2],
  tests: 'regression-suite',
  parallelDevices: 5,
  deviceFarm: 'browserstack'
}, "qe-test-executor");

// Device farm integration
await Task("Device Farm Execution", {
  service: 'browserstack',
  devices: [
    'iPhone 15 - iOS 17',
    'Samsung Galaxy S24 - Android 14'
  ],
  recordVideo: true,
  captureNetworkLogs: true
}, "qe-test-executor");

Agent Coordination Hints

Memory Namespace
aqe/mobile-testing/
├── device-matrix/*      - Device coverage strategy
├── platform-tests/*     - iOS/Android specific tests
├── gesture-library/*    - Reusable gesture patterns
└── performance/*        - Mobile performance metrics
Fleet Coordination
const mobileFleet = await FleetManager.coordinate({
  strategy: 'mobile-testing',
  agents: [
    'qe-test-executor',       // Cross-platform execution
    'qe-performance-tester',  // Mobile performance
    'qe-visual-tester'        // Screen size validation
  ],
  topology: 'parallel'
});

Related Skills


Remember

Test on real devices for critical flows. Emulators catch 80% of bugs but real devices are needed for actual performance, sensor behavior, and platform quirks.

With Agents: qe-test-executor orchestrates testing across device farms, manages platform differences, and tests 10+ devices in parallel.

Comments

Markdown supported