mcpField
C
ce-test-xcode

ce-test-xcode

github.com/everyincTesting & quality25.8k3.0k installsUpdated today
Repository

About ce-test-xcode

ce-test-xcode is a skill for building and exercising iOS apps in an Xcode simulator. It records screenshots, logs, verification results, and failures as evidence, then reports the outcome for each tested surface and the overall run.

Key features

  1. 01Build and launch an iOS app in a simulator
  2. 02Exercise in-scope app flows
  3. 03Capture screenshots and logs
  4. 04Report per-surface and overall results
  5. 05Record human checks and failures

Use cases

  1. 01Checking app screens in an Xcode simulator
  2. 02Saving evidence from a simulator test run
  3. 03Reporting failures or skipped checks after testing

MCP support

The skill checks for XcodeBuildMCP availability during setup and build. It uses available adapters to build, install, and launch the app.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/everyinc/compound-engineering-plugin --skill ce-test-xcode

After installing, type/ce-test-xcodein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
setup-and-build.md
test-and-report.md

Details

From the project README

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.

Comments

Markdown supported