Skip to content
TrustedSkillsbeta
Back to all skills

Swift Testing

Checked
johnrogers·vlatest·testing·MIT

Helps with Swift, testing as part of building frontend UIs and user experiences workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add johnrogers/claude-swift-engineering --skill swift-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

johnrogers

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned johnrogers/claude-swift-engineering at 1dc2cf4d02.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1dc2cf4d02
Manifest
plugins/swift-engineering/skills/swift-testing/SKILL.md
Scanned
1 file, 129 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to assist with writing and understanding Swift tests using the modern Swift Testing framework. It replaces Apple's XCTest framework with a macro-based approach that offers more concise syntax, improved asynchronous support, and parallel test execution by default. The skill helps developers transition from XCTest concepts and write effective unit tests for Swift projects.

When to use it

  • When migrating existing XCTest codebases to the Swift Testing framework.
  • For writing new Swift unit tests, particularly when needing concise syntax and async support.
  • To understand test failures and debug issues within Swift testing workflows.
  • When implementing parameterized tests with multiple input sets.

Key capabilities

  • Assertion Macros: Uses #expect for soft assertions (continues on failure) and #require for hard preconditions (stops the test).
  • Test Structure Support: Assists in creating test suites (@Suite) and individual tests (@Test).
  • Assertion Conversion: Provides guidance on translating XCTest assertions to Swift Testing equivalents.
  • Error Handling Tests: Supports testing for specific error types using #expect(throws: ...) syntax.
  • Parameterized Tests: Facilitates the creation of parameterized tests with input data sets.
  • Async Testing Support: Enables writing asynchronous tests using async/await.
  • Confirmation Blocks: Assists in implementing callback confirmations within tests.
  • Tagging: Supports test tagging for categorization and filtering (e.g., @Tag static var fast).

Example prompts

  • "How do I write an assertion in Swift Testing to check if a variable is nil?"
  • "Can you show me how to create a parameterized test using the Swift Testing framework?"
  • "What's the difference between #expect and #require in Swift Testing?"

Tips & gotchas

  • Prioritize #expect: Use #expect for most assertions; reserve #require for preconditions only. Overusing #require can mask other failures.
  • State Isolation: Remember that each test gets a new instance of the system under test (SUT).
  • Cartesian Product Awareness: When using parameterized tests, always use zip to combine input arrays; otherwise, you may unintentionally create a Cartesian product.