appium

Appium mobile app automation. Use for mobile testing.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

appium is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Appium mobile app automation. Use for mobile testing.

Teams using appium should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/appium/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/testing/appium/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/appium/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How appium Compares

Feature / Agent	appium	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Appium mobile app automation. Use for mobile testing.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Appium

Appium is an open-source framework for automating native, mobile web, and hybrid applications on iOS, mobile Android, and Windows desktop platforms. It uses the WebDriver protocol.

## When to Use

- **Real Device Testing**: Testing on physical iPhones/Androids.
- **Cross-Platform**: Write one test (mostly) for both iOS and Android.
- **Black-box Testing**: Testing the app from the outside (like a user) without needing source code access.

## Quick Start (WebdriverIO + Appium)

```javascript
// wdio.conf.js
capabilities: [
  {
    platformName: "Android",
    "appium:deviceName": "Pixel_3a",
    "appium:app": "/path/to.apk",
    "appium:automationName": "UiAutomator2",
  },
];

// test.js
await $("~Login Button").click(); // Accessibility ID
await $('android=new UiSelector().text("Submit")').click();
```

## Core Concepts

### Drivers

Appium uses drivers to interface with underlying frameworks:

- **XCUITest**: Apple's UI test framework (iOS).
- **UiAutomator2**: Google's UI test framework (Android).

### Appium Inspector

A GUI tool to inspect your mobile app's definition (XML), find element IDs, and record scripts.

## Best Practices (2025)

**Do**:

- **Use Accessibility IDs**: The most robust way to find elements (`~MyID`). Avoid XPath which is slow on mobile.
- **Use Appium 2.0**: The new standard. Driver-based architecture (`appium driver install uiautomator2`).
- **Parallelize**: Use device farms (BrowserStack, SauceLabs) for running on multiple devices.

**Don't**:

- **Don't use hard waits**: Mobile devices vary widely in speed.
- **Don't rely on coordinates**: Different screen sizes will break your tests.

## References

- [Appium Documentation](https://appium.io/docs/en/2.0/)