swift-testing-expert

avdlee/swift-testing-agent-skill · updated Apr 8, 2026

$npx skills add https://github.com/avdlee/swift-testing-agent-skill --skill swift-testing-expert
0 commentsdiscussion
summary

Write, review, and migrate Swift tests using modern Swift Testing APIs with parallel execution and clear diagnostics.

  • 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 \
skill.md

Swift Testing

Overview

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.

Agent behavior contract (follow these rules)

  1. Prefer Swift Testing for Swift unit and integration tests, but keep XCTest for UI automation (XCUIApplication), performance metrics (XCTMetric), and Objective-C-only test code.
  2. Treat #expect as the default assertion and use #require when subsequent lines depend on a prerequisite value.
  3. Default to parallel-safe guidance. If tests are not isolated, first propose fixing shared state before applying .serialized.
  4. Prefer traits for behavior and metadata (.enabled, .disabled, .timeLimit, .bug, tags) over naming conventions or ad-hoc comments.
  5. Recommend parameterized tests when multiple tests share logic and differ only in input values.
  6. Use @available on test functions for OS-gated behavior instead of runtime #available checks inside test bodies; never annotate suite types with @available.
  7. Keep migration advice incremental: convert assertions first, then organize suites, then introduce parameterization/traits.
  8. Only import Testing in test targets, never in app/library/binary targets.

First 60 seconds (triage template)

  • Clarify the goal: new tests, migration, flaky failures, performance, CI filtering, or async waiting.
  • Collect minimal facts:
    • Xcode/Swift version and platform targets
    • Whether tests currently use XCTest, Swift Testing, or both
    • Whether failures are deterministic or flaky
    • Whether tests access shared resources (database, files, network, global state)
  • Branch quickly:
    • repetitive tests -> parameterized tests
    • noisy or flaky failures -> known issue handling and test isolation
    • migration questions -> XCTest mapping and coexistence strategy
    • async callback complexity -> continuation/await patterns

Routing map (read the right reference fast)

  • Test building blocks and suite organization -> references/fundamentals.md
  • #expect, #require, and throw expectations -> references/expectations.md
  • Traits, tags, and Xcode test-plan filtering -> references/traits-and-tags.md
  • Parameterized test design and combinatorics -> references/parameterized-testing.md
  • Default parallel execution, .serialized, isolation strategy -> references/parallelization-and-isolation.md
  • Test speed, determinism, and flakiness prevention -> references/performance-and-best-practices.md
  • Async waiting and callback bridging -> references/async-testing-and-waiting.md
  • XCTest coexistence and migration workflow -> references/migration-from-xctest.md
  • Test navigator/report workflows and diagnostics -> references/xcode-workflows.md
  • Index and quick navigation -> references/_index.md

Common pitfalls -> next best move

  • Repetitive testFooCaseA/testFooCaseB/... methods -> replace with one parameterized @Test(arguments:).
  • Failing optional preconditions hidden in later assertions -> try #require(...) then assert on unwrapped value.
  • Flaky integration tests on shared database -> isolate dependencies or in-memory repositories; use .serialized only as a transition step.
  • Disabled tests that silently rot -> prefer withKnownIssue for temporary known failures to preserve signal.
  • Unclear failure values for complex types -> conform type to CustomTestStringConvertible for focused test diagnostics.
  • Test-plan include/exclude by names -> use tags and tag-based filters instead.

Verification checklist

  • Confirm each test has a single clear behavior and expressive display name when needed.
  • Confirm prerequisites use #require where failure should stop the test.
  • Confirm repeated logic is parameterized instead of duplicated.
  • Confirm tests are parallel-safe or intentionally serialized with rationale.
  • Confirm async code is awaited and callback APIs are bridged safely.
  • Confirm migration keeps unsupported XCTest-only scenarios on XCTest.

References

  • references/_index.md
  • references/fundamentals.md
  • references/expectations.md
  • references/traits-and-tags.md
  • references/parameterized-testing.md
  • references/parallelization-and-isolation.md
  • references/performance-and-best-practices.md
  • references/async-testing-and-waiting.md
  • references/migration-from-xctest.md
  • references/xcode-workflows.md

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.671 reviews
  • Kiara Chawla· Dec 28, 2024

    We added swift-testing-expert from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ishan Dixit· Dec 28, 2024

    Keeps context tight: swift-testing-expert is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • William Chawla· Dec 24, 2024

    Solid pick for teams standardizing on skills: swift-testing-expert is focused, and the summary matches what you get after install.

  • Ishan Sharma· Dec 12, 2024

    swift-testing-expert fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Lucas Ghosh· Dec 4, 2024

    swift-testing-expert is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Yuki Wang· Dec 4, 2024

    Registry listing for swift-testing-expert matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Omar Ghosh· Nov 23, 2024

    Solid pick for teams standardizing on skills: swift-testing-expert is focused, and the summary matches what you get after install.

  • Camila Martin· Nov 23, 2024

    Useful defaults in swift-testing-expert — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kabir Martin· Nov 19, 2024

    swift-testing-expert has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • William Johnson· Nov 19, 2024

    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

1 / 8