Write, review, and migrate Swift tests using modern Swift Testing APIs with parallel execution and clear diagnostics.
Works with
Covers test structure, #expect / #require macros, traits, tags, parameterized tests, and async waiting patterns for readable, maintainable tests
Guides incremental XCTest migration while preserving UI automation and performance-metric tests that require XCTest
Prioritizes parallel-safe test design; recommends fixing shared state before applying .serialized isolation \
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionswift-testing-expertExecute the skills CLI command in your project's root directory to begin installation:
Fetches swift-testing-expert from avdlee/swift-testing-agent-skill and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate swift-testing-expert. Access via /swift-testing-expert in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
328
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
328
stars
Use this skill to write, review, migrate, and debug Swift tests with modern Swift Testing APIs. Prioritize readable tests, robust parallel execution, clear diagnostics, and incremental migration from XCTest where needed.
XCUIApplication), performance metrics (XCTMetric), and Objective-C-only test code.#expect as the default assertion and use #require when subsequent lines depend on a prerequisite value..serialized..enabled, .disabled, .timeLimit, .bug, tags) over naming conventions or ad-hoc comments.@available on test functions for OS-gated behavior instead of runtime #available checks inside test bodies; never annotate suite types with @available.Testing in test targets, never in app/library/binary targets.references/fundamentals.md#expect, #require, and throw expectations -> references/expectations.mdreferences/traits-and-tags.mdreferences/parameterized-testing.md.serialized, isolation strategy -> references/parallelization-and-isolation.mdreferences/performance-and-best-practices.mdreferences/async-testing-and-waiting.mdreferences/migration-from-xctest.mdreferences/xcode-workflows.mdreferences/_index.mdtestFooCaseA/testFooCaseB/... methods -> replace with one parameterized @Test(arguments:).try #require(...) then assert on unwrapped value..serialized only as a transition step.withKnownIssue for temporary known failures to preserve signal.CustomTestStringConvertible for focused test diagnostics.#require where failure should stop the test.references/_index.mdreferences/fundamentals.mdreferences/expectations.mdreferences/traits-and-tags.mdreferences/parameterized-testing.mdreferences/parallelization-and-isolation.mdreferences/performance-and-best-practices.mdreferences/async-testing-and-waiting.mdreferences/migration-from-xctest.mdreferences/xcode-workflows.mdPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
erichowens/some_claude_skills
wispbit-ai/skills
jeffallan/claude-skills
jeffallan/claude-skills
We added swift-testing-expert from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: swift-testing-expert is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: swift-testing-expert is focused, and the summary matches what you get after install.
swift-testing-expert fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
swift-testing-expert is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for swift-testing-expert matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: swift-testing-expert is focused, and the summary matches what you get after install.
Useful defaults in swift-testing-expert — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
swift-testing-expert has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added swift-testing-expert from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 71