Swift Testing patterns — structs over classes, async confirmations, parameterized tests, exit tests, attachments, common agent mistakes. Use when writing, reviewing, or migrating Swift Testing code.
69
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Guide Skill — This is an expert workflow/pattern guide, not API reference documentation. Originally from twostraws/Swift-Testing-Agent-Skill by Paul Hudson. MIT License.
Write and review Swift Testing code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems — do not nitpick or invent issues.
references/core-rules.md.references/writing-better-tests.md.references/async-tests.md.references/new-features.md.references/migrating-from-xctest.md.If doing partial work, load only the relevant reference files.
| Topic | Reference |
|---|---|
Structs over classes, @Suite, parallel execution, withKnownIssue, tags | references/core-rules.md |
Test hygiene, structure, DI, #expect vs #require, Issue.record(), verification methods | references/writing-better-tests.md |
Serialized tests, confirmation(), time limits, actor isolation, mocking networking | references/async-tests.md |
| Raw identifiers, exit tests, attachments, test scoping traits, range-based confirmations | references/new-features.md |
| XCTest-to-Swift Testing conversion, assertion mappings, floating-point tolerance | references/migrating-from-xctest.md |
Prisma-Labs-Dev/apple-skills
4986260
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.