Comprehensive mobile testing for iOS and Android platforms including gestures, sensors, permissions, device fragmentation, and performance.

MITAuto-check passedMobile

Install Mobile Testing

skills CLI
$ npx skills add proffesor-for-testing/agentic-qe --skill mobile-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install proffesor-for-testing/agentic-qe mobile-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/skills/mobile-testing .claude/skills/mobile-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mobile-testing
GitHub stars
494
Token cost
~1.3k tokens
SKILL.md length
272 words
Files
4 (incl. scripts)
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Comprehensive mobile testing for iOS and Android platforms including gestures, sensors, permissions, device fragmentation, and performance.

  • Works in 5 steps: DEFINE device coverage matrix (Tier 1:… → TEST platform differences (iOS ≠… → VALIDATE touch gestures (tap, swipe,… → …
  • Testing native apps
  • SKILL.md covers Quick Reference Card, Mobile-Specific Scenarios, Agent-Driven Mobile Testing and Agent Coordination Hints, plus 2 more sections
  • Ensuring quality across 1000+ device variants

What it does

Mobile Testing is an agent skill from proffesor-for-testing/agentic-qe. Comprehensive mobile testing for iOS and Android platforms including gestures, sensors, permissions, device fragmentation, and performance. Use when testing native apps, hybrid apps, or mobile web, ensuring quality across 1000+ device variants.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `evals/mobile-testing.yaml`, `schemas/output.json` and `scripts/validate-config.json`).

It sits in Mobile, covering Mobile testing and debugging and Cross-platform mobile apps. It works with Android and iOS. The repository describes itself as: Agentic QE Fleet is an open-source AI-powered QA/QE platform designed for use with Coding Agents (works best with Claude Code) featuring specialized agents and skills to support… The licence is MIT.

When your agent uses it

  • Testing native apps
  • Ensuring quality across 1000+ device variants

Example prompts

  • “/mobile-testing”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit 829d030. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mobile Testing loads about 1.3k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 272 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from proffesor-for-testing/agentic-qe at commit 829d030, republished under its MIT licence (© proffesor-for-testing). 272 words, ~1,319 tokens.

Download SKILL.mdSave it as .claude/skills/mobile-testing/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
mobile-testing
description
Comprehensive mobile testing for iOS and Android platforms including gestures, sensors, permissions, device fragmentation, and performance. Use when testing native apps, hybrid apps, or mobile web, ensuring quality across 1000+ device variants.
category
specialized-testing
priority
high
tokenEstimate
1000
agents
qe-test-executor, qe-performance-tester, qe-visual-tester
implementation_status
optimized
optimization_version
1
last_optimized
2025-12-02
quick_reference_card
true
tags
mobile, ios, android, appium, gestures, device-fragmentation, sensors
trust_tier
3

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

javascript
// 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

typescript
// 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
typescript
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'
});


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.

© proffesor-for-testing, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in assets/skills/mobile-testing of proffesor-for-testing/agentic-qe.

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

Open the folder on GitHubat commit 829d030

Compare with similar skills

Mobile Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mobile Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mobile Testing this skillproffesor-for-testing/agentic-qe494—~1.3kAutomated safety check: PassMIT
Screenmapaleqsio/screenmap239—~7.2kAutomated safety check: PassMIT
Simulator Audio E2Ehyochan/react-native-nitro-sound961—~1.1kAutomated safety check: PassMIT
Maui AI DebuggingRedth/Maui.Gtk101—~4.1kAutomated safety check: PassMIT
Expo Development on Limrunsuperset-sh/superset15k—~3.6kAutomated safety check: PassCustom licence
Android Screenshotsboardsesh/boardsesh163—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Screenmap

    aleqsio/screenmap

    Generate a visual navigation map of an Expo / React Native or NativeScript app.

    239 GitHub stars~7.2k tokensUpdated 3 days ago
    MobileAuto-check passed
  • Simulator Audio E2E

    hyochan/react-native-nitro-sound

    Build and run repeatable react-native-nitro-sound recorder/player regression tests on an iOS Simulator or Android emulator, with explicit virtual-device selection, microphone permission, Maestro…

    961 GitHub stars~1.1k tokensUpdated 8 days ago
    MobileAuto-check passed
  • Maui AI Debugging

    Redth/Maui.Gtk

    End-to-end workflow for building, deploying, inspecting, and debugging .NET MAUI and MAUI Blazor Hybrid apps as an AI agent.

    101 GitHub stars~4.1k tokensUpdated 5 mo ago
    MobileAuto-check passed
  • Expo Development on Limrun

    superset-sh/superset

    Sets up and runs Expo and React Native apps on Limrun remote iOS simulators and Android emulators, using dev-client builds for fast JS and TS iteration.

    15k GitHub stars~3.6k tokensUpdated today
    MobileAuto-check passed
  • Android Screenshots

    boardsesh/boardsesh

    Capture screenshots of the Boardsesh React Native app (packages/mobile/) running on an Android emulator, driven against Metro with a cached dev-client APK.

    163 GitHub stars~1.1k tokensUpdated today
    MobileAuto-check passed
  • Frb Dev Env

    fzyzcjy/flutter_rust_bridge

    A skill your agent uses when the user wants Docker-based FRB development or Tart-based iOS Simulator validation.

    5.4k GitHub stars~5.5k tokensUpdated yesterday
    MobileAuto-check passed

More from proffesor-for-testing/agentic-qe

All 111 skills in this repo
  • Contract Testing

    proffesor-for-testing/agentic-qe

    Consumer-driven contract testing for microservices using Pact, schema validation, API versioning, and backward compatibility testing.

    494 GitHub stars~1.8k tokensUpdated 3 days ago
    Auto-check passed
  • Mutation Testing

    proffesor-for-testing/agentic-qe

    Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate.

    494 GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed
  • Performance Testing

    proffesor-for-testing/agentic-qe

    Profiles application performance under load using k6, Artillery, or JMeter to measure latency, throughput, and error rates.

    494 GitHub stars~2.4k tokensUpdated 3 days ago
    Auto-check passed
  • Code Review Quality

    proffesor-for-testing/agentic-qe

    Conduct context-driven code reviews focusing on quality, testability, and maintainability.

    494 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Security Testing

    proffesor-for-testing/agentic-qe

    Scans for security vulnerabilities including XSS, SQL injection, CSRF, and auth flaws using OWASP Top 10 methodology.

    494 GitHub stars~2.7k tokensUpdated 3 days ago
    Auto-check: notes
  • Database Testing

    proffesor-for-testing/agentic-qe

    Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance.

    494 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Works with

Categories

Questions about Mobile Testing

What does Mobile Testing do?

Comprehensive mobile testing for iOS and Android platforms including gestures, sensors, permissions, device fragmentation, and performance. Mobile Testing is an agent skill from proffesor-for-testing/agentic-qe. Comprehensive mobile testing for iOS and Android platforms including gestures, sensors, permissions, device fragmentation, and performance.

When should I use Mobile Testing?

Mobile Testing fits situations like: testing native apps; ensuring quality across 1000+ device variants.

How do I install Mobile Testing in Claude Code?

Run `npx skills add proffesor-for-testing/agentic-qe --skill mobile-testing -a claude-code`. Or copy the skill folder (assets/skills/mobile-testing in proffesor-for-testing/agentic-qe) into .claude/skills/mobile-testing in your project. Claude Code loads it when a task matches its description.

How do I install Mobile Testing in Codex?

Run `npx skills add proffesor-for-testing/agentic-qe --skill mobile-testing -a codex`. Or copy the skill folder (assets/skills/mobile-testing in proffesor-for-testing/agentic-qe) into .agents/skills/mobile-testing in your project. Codex loads it when a task matches its description.

Can I use Mobile Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add proffesor-for-testing/agentic-qe --skill mobile-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mobile-testing, .gemini/skills/mobile-testing, .github/skills/mobile-testing and .opencode/skills/mobile-testing in your project.

What does Mobile Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Mobile Testing is instructions for the agent only.

Does Mobile Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Mobile Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Mobile Testing use?

Mobile Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mobile Testing use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Mobile Testing?

Skills that share tags, products or a category with Mobile Testing: Screenmap (aleqsio/screenmap, 239 stars), Simulator Audio E2E (hyochan/react-native-nitro-sound, 961 stars), Maui AI Debugging (Redth/Maui.Gtk, 101 stars) and Expo Development on Limrun (superset-sh/superset, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mobile Testing?

proffesor-for-testing (a GitHub user) maintains it in proffesor-for-testing/agentic-qe, which has 494 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on October 4, 2026.

Source: proffesor-for-testing/agentic-qe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.