mobile-app-testing · aj-geddes — Claude Code skill: what it does, how to install
Provides testing guidelines for iOS and Android apps. Covers unit, UI, and performance tests using Jest, Detox, Espresso, and XCTest.
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-testing -a claude-codeWhat mobile-app-testing does
mobile-app-testing sets up testing workflows for iOS and Android projects. It includes unit test structures with Jest, component checks via @testing-library/react-native, and reference guides for Detox, Espresso, and XCTest.
The guidelines enforce strict practices: mock external APIs, keep test cases isolated, and maintain code coverage above 80%. Testing internal implementation details or hardcoding test data is explicitly discouraged.
Because the skill requires test execution and performance measurement on actual hardware, emulators alone will not be enough for a release pipeline.
What it helps with
- write component unit tests with @testing-library/react-native
- automate mobile UI testing with Detox or Espresso
- mock backend API calls for integration tests
- profile and measure performance on target mobile devices
Example prompts for the agent
- Write a Jest unit test for UserProfile using @testing-library/react-native
- Help me set up automated UI tests with Detox for the login flow
- Review our mobile test suite against the >80% coverage guidelines
How to install mobile-app-testing
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-testing -a claude-code2Manually: put the files in place
~/.claude/skills/mobile-app-testing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mobile-app-testing/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-testing -a codex2Manually: put the files in place
.agents/skills/mobile-app-testing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-testing -a cursor2Manually: put the files in place
.cursor/skills/mobile-app-testing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aj-geddes/useful-ai-prompts mobile-app-testing2Manually: put the files in place
.github/skills/mobile-app-testing/SKILL.md1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-testing -a gemini-cli2Platform CLI
gemini skills install https://github.com/aj-geddes/useful-ai-prompts --path skills/mobile-app-testingManually: put the files in place
.devin/skills/mobile-app-testing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-testing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about mobile-app-testing
How to install mobile-app-testing in Claude Code?
Run npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-testing -a claude-code. The skill file will be placed in ~/.claude/skills/mobile-app-testing/SKILL.md.
What test frameworks are covered by mobile-app-testing?
It includes guides and examples for Jest and Detox in React Native, XCTest for iOS, and Espresso for Android.
What code coverage target does mobile-app-testing require?
The skill instructs the agent to maintain test coverage above 80% and cover both success and failure execution paths.
Source text
SKILL.md · MIT
---
name: mobile-app-testing
description: >
Comprehensive mobile app testing strategies for iOS and Android. Covers unit
tests, UI tests, integration tests, performance testing, and test automation
with Detox, Appium, and XCTest.
---
# Mobile App Testing
## Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
## Overview
Implement comprehensive testing strategies for mobile applications including unit tests, UI tests, integration tests, and performance testing.
## When to Use
- Creating reliable mobile applications with test coverage
- Automating UI testing across iOS and Android
- Performance testing and optimization
- Integration testing with backend services
- Regression testing before releases
## Quick Start
Minimal working example:
```javascript
// Unit test with Jest
import { calculate } from "../utils/math";
describe("Math utilities", () => {
test("should add two numbers", () => {
expect(calculate.add(2, 3)).toBe(5);
});
test("should handle negative numbers", () => {
expect(calculate.add(-2, 3)).toBe(1);
});
});
// Component unit test
import React from "react";
import { render, screen } from "@testing-library/react-native";
import { UserProfile } from "../components/UserProfile";
describe("UserProfile Component", () => {
test("renders user name correctly", () => {
const mockUser = { id: "1", name: "John Doe", email: "[email protected]" };
render(<UserProfile user={mockUser} />);
expect(screen.getByText("John Doe")).toBeTruthy();
});
// ... (see reference guides for full implementation)
```
## Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents |
|---|---|
| [React Native Testing with Jest & Detox](references/react-native-testing-with-jest-detox.md) | React Native Testing with Jest & Detox |
| [iOS Testing with XCTest](references/ios-testing-with-xctest.md) | iOS Testing with XCTest |
| [Android Testing with Espresso](references/android-testing-with-espresso.md) | Android Testing with Espresso |
| [Performance Testing](references/performance-testing.md) | Performance Testing |
## Best Practices
### ✅ DO
- Write tests for business logic first
- Use dependency injection for testability
- Mock external API calls
- Test both success and failure paths
- Automate UI testing for critical flows
- Run tests on real devices
- Measure performance on target devices
- Keep tests isolated and independent
- Use meaningful test names
- Maintain >80% code coverage
### ❌ DON'T
- Skip testing UI-critical flows
- Use hardcoded test data
- Ignore performance regressions
- Test implementation details
- Make tests flaky or unreliable
- Skip testing on actual devices
- Ignore accessibility testing
- Create interdependent tests
- Test without mocking APIs
- Deploy untested code
© aj-geddes · MIT · aj-geddes/useful-ai-prompts
Similar skills
Everything for Testing and QA →mobile-app-testing by other authors comes first.