agentleFS
Sign inStart free
mejbaurbaharmejbaurbahar/fagun/skills/mobile-testing/SKILL.md

mobile-testing

Skill1 starsChanged 4 months agoMITView on GitHub

Use when testing mobile apps (iOS/Android native, or responsive/mobile-web) — device/viewport matrices, touch gesture testing, mobile-specific network and lifecycle conditions, and app-store readiness checks.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use Chrome DevTools MCP emulate/resize_page or Claude in Chrome to test key breakpoints: 375px (small phone), 414px (large phone), 768px …

    line 9
  2. Distinctive:

    Check touch target size (min ~44×44px) — mouse-precision UI often ships touch targets too small to tap reliably.

    line 10
  3. Distinctive:

    Check for hover-dependent functionality that has no touch equivalent (tooltips, hover menus).

    line 11
  4. Distinctive:

    Test both orientations (portrait/landscape) if the app doesn't lock orientation.

    line 12
  5. Distinctive:

    Test with the mobile viewport's actual user-agent, not just a resized desktop window — some sites serve different code paths by UA.

    line 13
  6. Distinctive:

    Permissions: test both grant and deny paths for every permission (camera, location, notifications, contacts) — deny path is the one that …

    line 19
  7. Distinctive:

    App update path: test upgrading from the previous released version (migrations, cached data compatibility), not just fresh installs.

    line 21
  8. Distinctive:

    Always include exact device model, OS version, app version/build number, and network condition in the report — mobile bugs are frequently …

    line 33

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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, notifications, contacts) — deny path is the one that gets skipped and ships broken.
  • Push notifications: delivery, deep-linking from a notification tap, badge count accuracy.
  • App update path: test upgrading from the previous released version (migrations, cached data compatibility), not just fresh installs.

Touch gesture testing

  • Tap, long-press, swipe (all directions where relevant), pinch-zoom, double-tap-zoom, drag-and-drop reorder.
  • Accidental-gesture resistance: does a scroll accidentally trigger a swipe-to-delete? Does a slightly-off tap on an adjacent element misfire?

App store readiness (if shipping to stores)

  • Screenshots/metadata match current UI (stale store screenshots are a common rejection/complaint source).
  • Privacy manifest / data-collection disclosures match what the app actually collects.
  • Crash-free session rate from a beta/TestFlight build before submitting.

Reporting

Always include exact device model, OS version, app version/build number, and network condition in the report — mobile bugs are frequently device/OS-specific and unreproducible without this. Use [[bug-reporting]].

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free