Menu

Individual skill

to-ios-test

0upvotes

Run existing iOS mobile-easy-use tests from a natural-language request, recursively finding files in the requested directory and summarizing results.

skills/to-ios-test/SKILL.md

Read pinned source

Source commit 79d8da76964b67c5857cd700ea30bf12538b52d0

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
9
Repository last updated
Sep 17, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# To iOS Test

Accept a natural-language request such as “run the click tests under this directory.” Resolve the scope, recursively find test files, and execute them one by one through [to-ios-run](../to-ios-run/SKILL.md).

## Workflow

1. Resolve the App, directory, and requested behavior from the request and session. Default to the App's `tests/`; clarify only material ambiguity.
2. Recursively discover files with `rg --files`. Read test modules to identify relevant tests and starting/cleanup conditions. Exclude helpers, deduplicate paths, and sort by path. State the selected files, then proceed; report no matches without claiming success.
3. Read and follow `to-ios-run`, using its `scriptPath + functionName` form: pass each module's absolute `scriptPath`, `functionName: "run"`, and `args: []`. Reuse the same target and MCP session; invoke each file once and await completion before the next file. No `.d.ts` is needed.
4. Continue after assertion failures when cleanup succeeded and the next starting conditions are established. Stop on cleanup failure, disconnect, operation timeout, or uncertain App state; mark remaining files unrun. Do not automatically retry or modify tests.

## Result

Show results in the reply first: list the first 10 cases in execution order (all cases if fewer), using ✅ for passed, ❌ for failed, and ⏭ for not run. Include the file and case name; briefly explain failures. Keep execution errors distinct from assertion failures.