idb-claude-mobile-testing

Automate iOS simulator UI tests via IDB CLI using testID elements.

3|1|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/krzemienski/claude-mobile-expo --skill idb-claude-mobile-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idb-claude-mobile-testing
Source: https://github.com/krzemienski/claude-mobile-expo/tree/main/.claude/skills/idb-claude-mobile-testing
Command: npx skills add https://github.com/krzemienski/claude-mobile-expo --skill idb-claude-mobile-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solves? Automating iOS UI tests, especially when higher-level tools like expo-mcp are unavailable or insufficient, can be a significant hurdle. This Skill provides a reliable, testID-based method for interacting with the iOS simulator, ensuring consistent and accurate UI automation.

Core Features & Use Cases

  • testID-based UI Automation: Systematically find, tap, and type into UI elements using their testID (AXUniqueId) via the IDB accessibility tree, eliminating guesswork.
  • No MCP Dependencies: Perform autonomous testing without relying on expo-mcp or xc-mcp tools, offering a fallback for critical testing.
  • Precise Interaction: Calculate exact center coordinates for reliable taps, ensuring consistent and accurate UI interactions.
  • Use Case: When expo-mcp is not connected, use this skill to autonomously execute Gate 4A frontend visual tests on an iOS simulator, ensuring all UI elements are interactive and functional without manual intervention.

Quick Start

Use the idb-claude-mobile-testing skill to tap the 'settings-button' on the booted iOS simulator and then take a screenshot.

Frequently Asked Questions about idb-claude-mobile-testing

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

FAQPage Schema
How do I automate iOS UI testing without expo-mcp or xc-mcp tools?

Automate iOS UI testing by using IDB CLI to locate elements via testID and perform taps, typing, and verifications on simulators. This Skill provides testID-based automation when higher-level MCP tools are unavailable, enabling autonomous UI interaction through the accessibility tree.

How do I find and tap UI elements in an iOS simulator using testID?

Use IDB CLI to access the accessibility tree and locate elements by their testID (AXUniqueId), then calculate center coordinates from the element's frame and simulate precise taps. This approach eliminates guesswork and ensures consistent, accurate interactions.

Can I run UI tests on iOS simulators without manual intervention?

Yes. This Skill automates UI testing on booted iOS simulators by driving IDB CLI to locate elements, compute tap coordinates, input text, and validate results via screenshots—enabling autonomous test execution without manual steps.

What do I need to set up before automating iOS UI tests with IDB CLI?

You need an iOS simulator, IDB CLI installed and configured, access to the simulator's accessibility tree, and testID mappings (AXUniqueId values) for the UI elements you want to interact with.

How do I verify that UI interactions succeeded in iOS simulator tests?

Validate interactions by taking screenshots after performing taps and text input, then inspect the results to confirm the UI elements responded correctly. IDB CLI provides accessibility tree access for post-interaction verification.