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

mobile-testing

Skill1 starsChanged 53 days 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

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test key widths: 360–375 (small phone), 390–430 (modern phone), 768 (tablet portrait), 1024 (tablet landscape), plus the design's real …

    line 16
  2. Very specific:

    No hover-only functionality.

    line 19
  3. Very specific:

    Always include device model, OS version, app version/build, network condition, locale, and whether it reproduces on other devices, plus …

    line 70

“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

Covers mobile web (responsive sites, PWAs) and native/hybrid apps (iOS, Android, React Native, Flutter). Mobile bugs are often device-, OS- and network-specific: always record them precisely.

1. Responsive / mobile-web

  • Test key widths: 360–375 (small phone), 390–430 (modern phone), 768 (tablet portrait), 1024 (tablet landscape), plus the design's real breakpoints. Both orientations.
  • Emulate real devices (DevTools device mode, Playwright devices['iPhone 15'], BrowserStack/Sauce/LambdaTest real devices) including user agent, touch events, DPR and CPU/network throttling, not just a resized window.
  • Touch targets ≥ 44×44 pt (Apple) / 48×48 dp (Material); WCAG 2.2 minimum 24×24 CSS px (accessibility-testing).
  • No hover-only functionality; virtual keyboard doesn't cover fields (visualViewport), correct inputmode/autocomplete/type for keyboards; sticky bars vs dynamic address bar (dvh units); safe-area insets/notches; pull-to-refresh and scroll-lock behavior.
  • Performance on mid-range Android over throttled 4G (web-performance-testing); offline/PWA behavior (pwa-offline-testing).

2. Native app test matrix

Pick a representative spread rather than "everything": oldest supported OS, latest OS, one low-end device (RAM/CPU-constrained), one flagship, a foldable/tablet if supported, small and large screens, and the top devices from your analytics. Use real devices for sensors, camera, biometrics, push, Bluetooth, GPS, thermal and battery behavior; emulators/simulators for fast functional runs.

3. What to test

AreaCases
LifecycleBackground mid-flow (payment, upload) and resume · force-quit and relaunch (state restore) · low-memory kill · rotation · split-screen/multi-window · app switcher snapshot hides sensitive data
InterruptionsIncoming call, SMS, notification, alarm, low-battery dialog, OS permission popups, Do Not Disturb, Bluetooth/headphone connect
NetworkAirplane mode mid-request, slow/lossy 3G, Wi-Fi ↔ cellular handover, captive portal, offline queue and sync, timeouts and retry UX (chaos-resilience-testing)
PermissionsGrant and deny (and "only this time", approximate location) for camera, mic, location, notifications, contacts, photos; "don't ask again" recovery path via Settings
Push & deep linksDelivery in foreground/background/killed state, tap routing, badge counts, universal/app links, cold vs warm start
GesturesTap, long-press, swipe, pinch, drag-reorder; accidental-gesture resistance; edge-swipe back gesture conflicts
Install/updateFresh install, upgrade from previous and older versions (data migration), reinstall, uninstall cleanup, background app refresh
Data & storageLocal DB migrations, secure storage (Keychain/Keystore), backup/restore, low-disk behavior, logout clears data
SecurityCertificate pinning behavior, no secrets in logs/binaries, jailbreak/root handling, screenshot/recording protection where required, deep-link input validation (security-testing)
AccessibilityVoiceOver/TalkBack, dynamic type/font scaling, contrast, reduced motion, switch control
LocalizationRTL, long strings, locale formats (localization-testing)
Battery/perfCold start time, frame rate/jank, memory growth, battery drain, thermal throttling (memory-leak-resource-testing)
Payments/IAPStore sandbox, restore purchases, refunds, receipt validation (payment-ecommerce-testing)

4. Automation

ToolNotes
Appium (UiAutomator2/XCUITest drivers)Cross-platform, WebDriver-based
MaestroSimple YAML flows, fast to author, good for smoke
XCUITest / EspressoNative, fastest and most stable per platform
DetoxReact Native gray-box E2E
Flutter integration_testFlutter apps
Device cloudsBrowserStack, Sauce Labs, AWS Device Farm, Firebase Test Lab
# Maestro flow
appId: com.example.shop
---
- launchApp: { clearState: true }
- tapOn: "Sign in"
- inputText: "qa@example.com"
- assertVisible: "Welcome"
adb shell settings put global airplane_mode_on 1          # Android network toggles
xcrun simctl status_bar booted override --time 9:41       # deterministic iOS screenshots
adb logcat -b crash ; xcrun simctl spawn booted log stream --predicate 'process == "MyApp"'

5. Release readiness for stores

Store screenshots and metadata match the current UI · privacy labels/data-safety form match real data collection · crash-free sessions ≥ 99.5% on a beta/TestFlight/internal track · staged rollout with halt criteria · store policy checks (permissions justification, IAP rules, background modes) (release-readiness-testing).

Reporting

Always include device model, OS version, app version/build, network condition, locale, and whether it reproduces on other devices, plus logs (adb logcat, Xcode device logs), screen recording and crash stack. Format: bug-reporting.

Related

e2e-testing, accessibility-testing, pwa-offline-testing, web-performance-testing, compatibility-testing, game-testing

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