skills.rest
Emasoft
EmasoftCOMMUNITY
Explore all skills by this author →
Website𝕏@fmuaddibGitHub

simulator-automation

Resolve iOS simulator and device build failures and automate run-and-observe workflows.

1|Updated Jun 9, 2026
Search Tags:#swift#ios#xcode#simulator#ui automation#axe#app testing
One-click install
npx skills add https://github.com/Emasoft/emasoft-complete-ios-app-authoring --skill simulator-automation-emasoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: simulator-automation
Source: https://github.com/Emasoft/emasoft-complete-ios-app-authoring/tree/main/skills/simulator-automation
Command: npx skills add https://github.com/Emasoft/emasoft-complete-ios-app-authoring --skill simulator-automation-emasoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the hours of wasted time developers and QA engineers spend debugging mysterious iOS app build and run failures, which are almost always caused by environment issues like stale DerivedData, zombie xcodebuild processes, or stuck simulators instead of actual code bugs. It removes the manual, error-prone work of driving simulators and devices, capturing screenshots, pulling logs, and verifying UI behavior, turning a fragile, multi-step process into a reliable, repeatable workflow.

Core Features & Use Cases

  • Environment-first diagnostics: Automatically identifies and fixes the 80% of "mysterious" build/run failures caused by stale caches, zombie processes, or stuck simulators in 2–10 minutes, no code debugging required.
  • Multi-driver UI automation: Supports 6 different UI interaction drivers (XcodeBuildMCP, AXe, Maestro, XCUITest, WebDriverAgent, and native CLI) to tap, type, swipe, and interact with app elements via accessibility selectors or coordinates, surviving layout shifts and animation flakiness.
  • End-to-end QA passes: Includes built-in workflows for UI smoke tests, visual regression testing, accessibility audits, memory leak hunting, and localized screenshot capture for App Store assets.
  • Use Case: A developer getting a "BUILD FAILED" error with no clear cause can use this Skill to run the environment recovery checklist, automatically build and launch the app on a simulator, drive the login flow, capture a screenshot and accessibility tree, and pull crash logs if the app fails to launch.

Quick Start

Use the simulator-automation skill to build and launch your iOS app on the available simulator, drive the login flow via accessibility selectors, capture a screenshot of the home screen, and pull logs to confirm no crashes occurred on launch.

Frequently Asked Questions about simulator-automation

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

FAQPage Schema
How do I fix a mysterious iOS app build failure with no clear cause?▼

iOS app build failures are often caused by stale DerivedData, zombie xcodebuild processes, or stuck simulators. Running an environment-first diagnostic recovery checklist clears caches and resolves these environment issues in minutes without debugging code.

How do I automate iOS simulator UI testing using accessibility selectors?▼

Automate iOS simulator UI testing by using multi-driver frameworks like XCUITest, WebDriverAgent, or AXe to tap, type, and swipe app elements via accessibility selectors. This approach survives layout shifts and animation flakiness during interaction.

Does this approach support visual regression and accessibility auditing for iOS apps?▼

Yes, this approach supports end-to-end QA passes including visual regression testing, accessibility auditing, and memory leak hunting. It captures localized screenshots and accessibility trees to verify UI behavior and compliance during automated workflows.

What's the best way to capture App Store screenshots from an iOS simulator?▼

The best way to capture App Store screenshots is through localized screenshot capture workflows that automate simulator booting, app installation, and UI navigation. This captures localized assets directly from the simulator interface without manual intervention.

Why does my iOS simulator get stuck during automated app testing?▼

iOS simulators get stuck during automated testing due to stale CoreSimulator caches, stuck simulator states, or zombie processes. Running structured recovery procedures clears these environment issues and restores simulator availability for continued automation.

Can I use Maestro and XCUITest together for iOS UI automation?▼

Yes, Maestro and XCUITest can be used together within a multi-driver UI automation workflow. Supporting six different interaction drivers, the workflow orchestrates tapping, typing, and swiping across frameworks to drive app elements via selectors or coordinates.

Related Skills

Explore More Software Engineering Skills→
PallepadehatPallepadehat
1

swift-concurrency-expert

Review and remediate Swift 6.2+ concurrency issues with actor isolation and Sendable safety.

Community
Advanced
tuliopc23tuliopc23

axiom-app-store-connect-ref

Analyze crash reports, TestFlight feedback, and performance metrics in App Store Connect.

Community
Basic
wordpress-mobilewordpress-mobile
3.9k

ios-sim-navigation

Navigate iOS simulator UI via WebDriverAgent using the accessibility tree.

Official
Intermediate
ckorhonenckorhonen
12

ios-app-tester

Run AXe-based accessibility audits and automate UI interactions on iOS Simulators.

Community
Intermediate