Ios unit test
A collection of Claude Code skills for iOS, MERN, NEAN, and shared development workflows
npx -y skills add edfenton/claude-skills --skill ios-unit-testAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Run iOS unit/UI tests, report results, and optionally fix failures.
SKILL.md
1.6 KB, as published. Nobody here has run it
Purpose
Run iOS tests, report failures with enough detail to debug, then (with approval) fix issues and re-run to confirm.
Arguments
--scheme <name>— Xcode scheme (inferred from xcodebuild -list if omitted)--project <path>— Path to .xcodeproj or .xcworkspace (auto-detected if omitted)--configuration <config>— Build configuration (default: NonProd)--no-fix— Report only, don't offer to fix
Workflow
1. Run tests
xcodebuild \
-project MyApp.xcodeproj \
-scheme MyApp \
-configuration NonProd \
-destination 'platform=iOS Simulator,name=iPhone 17 Pro' \
test
Use xcodebuild -list to discover schemes if not specified. Simulator names vary by Xcode version — use xcrun simctl list devices available to find available simulators.
Note: Tests use Swift Testing framework (import Testing, @Test, #expect), not XCTest.
2. Report results
Include:
- Pass/fail/skip counts
- Each failing test: target, file, test name, assertion/error message
- If test target won't build, include build errors
3–4. Approval gate, fix and confirm
See /shared-review-workflow for approval gate protocol, fix constraints, and severity definitions. Group iOS failures by area (view model, persistence, notifications, UI).
Reference
For xcodebuild patterns and common fixes, see reference/ios-unit-test-reference.md