mobile-testing
Use when profiling a mobile app, authoring or sizing mobile TCs, orchestrating a mobile suite run, executing a mobile TC, generating a manual guide, or producing a mobile run report. Mobile-app testing for all manual-qa agents — native iOS/Android via Appium MCP and the Mobitru device farm, and PWA/hybrid via Playwright mobile viewport.
arozumenko · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add arozumenko/sdlc-skills --skill mobile-testingAbout this skill
name: mobile-testing description: Use when profiling a mobile app, authoring or sizing mobile TCs, orchestrating a mobile suite run, executing a mobile TC, generating a manual guide, or producing a mobile run report. Mobile-app testing for all manual-qa agents — native iOS/Android via Appium MCP and the Mobitru device farm, and PWA/hybrid via Playwright mobile viewport. license: Apache-2.0 compatibility: "Appium mode: Node.js 22+, JDK 8+, appium-mcp, Android SDK (Android) or macOS+Xcode (iOS). Device-farm mode: mobitru-mcp-server, DEVICE_FARM_API_KEY. Playwright mode: Node.js 18+, @playwright/mcp. Manual mode: no additional tooling." metadata: authors: - Olha Stetsenko1 Olha_Stetsenko1@epam.com version: "1.0.0"
Mobile Testing
Add-on skill for all manual-qa agents. Augments app-profiler, test-author, test-sizer, test-run-lead, test-runner, and test-reporter to handle native iOS/Android apps (via Appium MCP or Mobitru device farm) and PWA/hybrid apps (via Playwright mobile viewport).
When to Use Each Section
| Situation | Agent | Section |
|---|---|---|
| Profile / onboard a mobile app | app-profiler | Part 1 |
| Author mobile test cases | test-author | Part 2 |
| Size mobile test cases (S/M/L) | test-sizer | Part 3 |
| Run a mobile test suite | test-run-lead | Parts 4–5 |
| Execute one mobile TC | test-runner | Part 6 |
| runner_mode = manual → guide | test-runner | Part 7 |
| Generate mobile run report | test-reporter | Part 8 |
Part 1 — Mobile App Profiling
Trigger: app-profiler is asked to profile a native iOS/Android or PWA/hybrid app.
Apply this section instead of (or in addition to) the standard web-profiling flow when the app is native (iOS/Android APK/IPA, React Native, Flutter, Swift, Kotlin) or when the user provides an APK/IPA file path.
Check for Existing Profile
Read .agents/manual-qa/app_profile.md if it exists. If it does — say "I found an existing profile for {app_name}. I'll update it." Use its content as a starting point; don't re-ask answered questions.
Phase 1 — Interview
Ask all at once:
To set up your mobile app profile I need a few things:
- App name (as it appears on the device)
- What does it do? (2-3 sentences)
- Platform: iOS, Android, or both?
- App type: Native (Swift/Kotlin/React Native/Flutter), PWA, or Hybrid?
- Build file: Do you have an APK (Android) or IPA (iOS) file path? Or a simulator/emulator already running? (If no file: TestFlight link, Firebase link, or public URL for PWA?)
- Login required? Auth method: email+password / OAuth / biometrics / magic link?
- Test credentials (if login required)
- 3-5 key flows to test
- User roles with different permissions?
- System permissions needed? (location, camera, notifications, contacts)
- External services in any flow? (email OTP, SMS, payment — I'll mark these manual-only)
Determine runner_mode in this priority order:
- PWA/Hybrid →
playwright - Native + APK/IPA provided:
check_device_farm_statussucceeds (Mobitru MCP available) →device-farm(real devices preferred)- Else local Appium MCP available →
appium - Else →
manual
- Native + no build file →
manual(interview-driven)
If both Mobitru and local Appium are available: "I'm defaulting to device-farm (real cloud devices). Say 'use local Appium' to switch to appium mode."
Phase 2a — Native Exploration via Appium MCP
Use when app_type: native, APK/IPA available, runner_mode: appium.
# 1. Select device
select_device → list available simulators/emulators → pick target
# 2. Install and launch
appium_app_lifecycle → { action: "install", app: "{apk_or_ipa_path}" }
appium_session_management → { action: "create", capabilities: {
platformName: "Android" | "iOS",
automationName: "UiAutomator2" | "XCUITest",
deviceName: "{device}",
app: "{path}"
}}
# 3. Explore launch screen
appium_get_page_source → understand initial UI structure
appium_screenshot → save to .agents/manual-qa/screenshots/launch.png
# 4. Authentication flow (if login required)
appium_find_element → locate email/password fields
generate_locators → auto-generate reliable locators for login screen
appium_set_value → fill credentials
appium_gesture → { action: "tap", elementId: "..." }
appium_get_page_source → verify authenticated state
appium_screenshot → save to .agents/manual-qa/screenshots/home.png
# 5. Explore each key screen from user's flow list
# For each flow:
appium_gesture → navigate to the screen
appium_get_page_source → document structure
generate_locators → extract reliable locators
appium_screenshot → save to .agents/manual-qa/screenshots/{screen}.png
# 6. Teardown
appium_session_management → { action: "delete" }
Apply systematic-debugging on unexpected behavior: screenshot + page_source → actual vs expected → hypothesis → adapt.
Phase 2b — PWA / Hybrid Exploration via Playwright MCP
Use when app_type: pwa or hybrid. Apply the standard web-profiling flow with mobile viewport added:
evaluate → set mobile viewport (e.g. iPhone 15: 393×852, touch enabled)
navigate → {base_url}
wait_for → networkidle
snapshot → understand structure
take_screenshot → .agents/manual-qa/screenshots/home.png
For each key flow — navigate, snapshot, screenshot, extract selectors.
Prefer: data-testid → ARIA role → visible text → name → CSS class.
Phase 2c — Device Farm Exploration via Mobitru MCP
Use when app_type: native and runner_mode: device-farm.
# 1. Verify farm and find a device
check_device_farm_status → confirm connection
device_farm_find_device → { platform: "android" | "ios", os_version: "..." }
device_farm_take_device_by_id → { serial: "{from find_device result}" }
# 2. Upload and install the app
device_farm_upload_artifact → upload APK or IPA file
device_farm_get_artifact_status → poll until status is "verified"
device_farm_instal
Read the complete source ↗