skills.rest
ahuaracab
ahuaracabCOMMUNITY
Explore all skills by this author →
GitHub

mobile-testing

Plan, automate, and review iOS, Android, and cross-platform mobile tests using XCTest, Espresso, and Detox.

Updated Aug 31, 2026
Search Tags:#test automation#ios#mobile testing#android#xctest#espresso#detox
One-click install
npx skills add https://github.com/ahuaracab/test-genesis --skill mobile-testing-ahuaracab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mobile-testing
Source: https://github.com/ahuaracab/test-genesis/tree/main/.agents/skills/mobile-testing
Command: npx skills add https://github.com/ahuaracab/test-genesis --skill mobile-testing-ahuaracab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Mobile QA teams struggle to write consistent automated tests across iOS, Android, and cross-platform apps while covering device orientation, runtime permissions, network conditions, sensors, performance SLAs, and OWASP Mobile Top 10 security. This Skill enforces a structured Plan → Code → Review workflow so mobile test automation is complete, platform-agnostic, and standards-compliant. ## Core Features & Use Cases - Multi-framework automation: Generates test components and suites for XCTest (iOS), Espresso (Android), and Detox/Appium (cross-platform) following the KATA component pattern with @atc test case IDs. - Adaptive scenario coverage: Partitions test cases by device class, orientation, network condition (WiFi/4G/offline), and permission state (granted/denied), with touch gestures, GPS/accelerometer simulation, and battery/memory/CPU SLA assertions. - Security and performance gates: Embeds OWASP Mobile Top 10 checks (SSL pinning, jailbreak detection) and measurable performance thresholds (cold start time, memory growth, battery drain) into every plan. - Use Case: Given a Jira story for a login feature, the skill derives 1:N test cases across iPhone/Android devices and orientations, writes the component classes and test files under tests/ios/, tests/android/, or tests/cross-platform/, then runs test, typecheck, and lint verifiers before merge. ## Quick Start Ask the AI to plan and automate mobile tests for a specific Jira ticket or module, for example: automate mobile tests for story LOGIN-101 covering iOS and Android login with permission and orientation scenarios.

Frequently Asked Questions about mobile-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate mobile tests for iOS and Android from a user story?▼

Invoke the skill with a ticket key or module slug. It loads the story's acceptance criteria, derives 1:N test cases partitioned by device, orientation, network, and permission state, then generates component classes and test files under tests/ios/, tests/android/, or tests/cross-platform/.

What mobile testing frameworks does this skill support?▼

It supports XCTest for iOS, Espresso for Android, and Detox or Appium for cross-platform React Native and Flutter apps. The same test structure applies across platforms, with platform-specific rules for locators, permissions, and gestures.

How are runtime permissions tested in mobile automation?▼

Permission state is treated as a precondition, never simulated mid-test. Tests cover both granted and denied states using GrantPermissionRule on Android, XCUIDevice alerts on iOS, or Detox's unified grantPermissions API.

Can I use this skill for web or CI/CD pipeline testing?▼

No. Web automation belongs to the test-automation skill and CI/CD orchestration belongs to regression-testing. This skill is scoped strictly to native and cross-platform mobile application testing.

How are mobile performance tests made measurable?▼

Every performance test asserts against explicit SLA thresholds, such as battery drain under 8% for a 10-minute video, cold start under 2 seconds, or memory growth under 5MB after repeated navigation. Vague goals like good performance are rejected.

Why does the skill reject tests without a declared device class?▼

Mobile behavior varies by screen size, orientation, and platform, so every test must declare its target device class such as iPhone, Android phone, or tablet. Device-agnostic tests are treated as review blockers because they hide responsive layout defects.

Related Skills

Explore More Software Engineering Skills→
terraphimterraphim

acceptance-testing

Transform requirements into acceptance criteria, test scenarios, and a UAT plan.

Official
Basic
guizonattoguizonatto

github-weekly-summary

Generates weekly engineering reports from GitHub releases and Jira metrics for Notion and Discord.

Community
Advanced
williamzujkowskiwilliamzujkowski
6

Application Security Validator

Assess application security against OWASP Top 10 2021 and API Security Top 10.

Community
Advanced
InnerScopeHearingInnerScopeHearing

live-walkthrough

Simulate user interactions across multiple devices to detect responsive bugs in web/Capacitor apps.

Official
Advanced