Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.

Xcode Simulator Test Build and exercise an iOS app on a simulator, preserving screenshots, logs, human verification results, and failures as evidence for the user. Done: A completed run reports overall PASS , FAIL , or PARTIAL plus project, scheme, simulator, build result, per surface PASS / FAIL / SKIP , console errors, human checks, and residual failures. Per surface status is derived from evidence, not the user's routing choice. PASS requires completed passing evidence. FAIL records observed failing evidence until a completed retest replaces it. SKIP means the check has no completed outcome. The overall result is FAIL while any failure remains, PARTIAL when no failure remains but a scoped check is skipped, and otherwise PASS . Any failure before the app is launched with log capture running stops later stages and reports an actionable setup blocker with its evidence. Boundaries: this skill tests and reports. Diagnosis and any user approved product fix belong to ce debug , invoked with its authority narrowed so it returns here without committing, pushing, or opening a PR. Keep simulator interaction within the app and flows the user placed in scope. Run 1. Prepare and launch. Read references/setup and build.md . It defines the XcodeBuildMCP availability check, project and scheme discovery, simulator choice, build, install, launch, and log capture start. 2. Exercise and report. After launch, read references/test and report.md . It defines per screen evidence, human only flows, the SwiftUI inline link automation limitation, what to do when a check fails, cleanup, and the fixed summary fields. Do not replace either required read with remembered tool names. XcodeBuildMCP adapters differ by host, while their observable success conditions do not.

ce-test-xcode