Menu
Run UI tests
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Build the project for testing
Build the project
Take the current plan all the way to a ready-to-merge pull request — review the plan (scaled to risk), implement it test-first, code-review and fix, security-review, verify the acceptance criteria, open the PR, and watch it green. Use after you have an approved plan (e.g. from plan mode) and want the rest of the feature pipeline run end-to-end. Invoking it is itself plan approval — it then runs autonomously to a single hard stop: ready-to-merge.
Run a specific test target or test class
Run all unit tests
Run snapshot tests
Based on SOC occupation classification
| name | test-ui |
| description | Run UI tests |
Runs the PopcornUITests test plan on the iOS Simulator. Optional argument: a
<TestTarget>/<TestClass> or <TestTarget>/<TestClass>/<testMethod> for a subset.
Preferred — Xcode MCP (xcode), when running inside Xcode. Get the
tabIdentifier from mcp__xcode__XcodeListWindows, then run
mcp__xcode__RunAllTests (or mcp__xcode__RunSomeTests with <specifier> for a
subset) with that tabIdentifier, targeting the PopcornUITests plan.
Fallback — make, when the MCP isn't available. Delegate to a Haiku subagent
(subagent_type: general-purpose, model: haiku). Do not run it yourself. Prompt it to:
Run `mkdir -p .build && make test-ui [TEST_CLASS=<specifier>] > .build/last-ui.log 2>&1`,
check the exit status, and report ONLY:
- Status: passed or failed
- Counts: total / passed / failed
- Each failing test as `SuiteName/testName` with its `file:line` and message (omit if none)
- On failure, the log path `.build/last-ui.log`
Do not paste passing-test output or raw logs.