Swift Testing Pro
Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.
- Скачивания
- 0
- В избранном
- 0
- Комментарии
- 0
- Просмотры
- 2
Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.
Добавьте инструмент одной командой или скачайте проверенный архив версии.
npx skills add twostraws/swift-testing-agent-skill --skill swift-testing-proWrite 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.
Review process:
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.
Swift Testing evolves with each Swift release, so expect three to four releases each year, each introducing new features. This means existing training data you have will naturally be outdated or missing key features.
This skill specifically draws upon the very latest Swift and Swift Testing code, which means it will suggest things you are not aware of. Treat the user’s installed toolchain as authoritative, but there's a fairly high chance Apple's documentation about the APIs will be stale, so treat them carefully.
If the user asks for a review, organize findings by file. For each issue:
Skip files with no issues. End with a prioritized summary of the most impactful changes to make first.
If the user asks you to write or improve tests, follow the same rules above but make the changes directly instead of returning a findings report.
Example output:
Line 5: Use struct, not class, for test suites.
// Before
class UserTests: XCTestCase {
// After
struct UserTests {
Line 12: Use #expect instead of XCTAssertEqual.
// Before
XCTAssertEqual(user.name, "Taylor")
// After
#expect(user.name == "Taylor")
Line 30: Use #require for preconditions, not #expect.
// Before
#expect(users.isEmpty == false)
let first = users.first!
// After
let first = try #require(users.first)
XCTestCase.XCTAssertEqual on line 12 should be migrated to #expect.#require to unwrap safely and stop the test early on failure.End of example.
references/core-rules.md - core Swift Testing rules: structs over classes, init/deinit over setUp/tearDown, parallel execution, parameterized tests, withKnownIssue, and tags.references/writing-better-tests.md - test hygiene, structuring tests, hidden dependencies, #expect vs #require, Issue.record(), #expect(throws:), and verification methods.references/async-tests.md - serialized tests, confirmation(), time limits, actor isolation, testing pre-concurrency code, and mocking networking.references/new-features.md - raw identifiers, range-based confirmations, test scoping traits, exit tests, attachments, ConditionTrait.evaluate(), and the updated #expect(throws:) return value.references/migrating-from-xctest.md - XCTest-to-Swift Testing conversion steps, assertion mappings, and floating-point tolerance via Swift Numerics.| Путь | Размер | SHA256 |
|---|---|---|
| .claude-plugin/plugin.json | 393 | ce277427d557d776... |
| SKILL.md | 4302 | ad4f1bff44b5b7fc... |
| agents/openai.yaml | 360 | f7a35b0befd4eb13... |
| assets/swift-testing-pro-icon.svg | 1515 | 92d3d0b2855da240... |
| references/async-tests.md | 8535 | bc6e0eabd10377b5... |
npx skills add twostraws/swift-testing-agent-skill --skill swift-testing-pro или скачайте ZIP-архив.Войдите, чтобы оставить комментарий.
Комментариев пока нет.