swift-testing

Rules for writing tests with Swift Testing, Apple's modern Swift testing framework. They cover test declarations, checks, required conditions, asynchronous code, parameterized tests, and test organization.

In plain words
What is it for?
Apply them when creating or changing Swift test files, test suites, or test setup. They specify where tests belong and how to test successful results, errors, asynchronous work, and multiple inputs.
Why use it?
They keep Swift tests consistent and use the framework's recommended style instead of older XCTest patterns. Clear checks and organization make test failures easier to understand.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/getsentry/xcodebuildmcp-ios-template/swift-testing
Clone the repo
git clone --depth 1 https://github.com/getsentry/XcodeBuildMCP-iOS-Template

Made for: Cursor.

Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,471 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.01471
Opus 5 $0.00022 $0.00736
Sonnet 5 $0.00009 $0.00294
Haiku 4.5 $0.00004 $0.00147

Measured 2d ago against content hash 24dd8184cd9d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

swift-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

template/.cursor/rules/swift-testing.mdc · 233 lines

How it starts

The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.

name: "Swift Testing Framework Guidelines" description: "Modern Swift Testing patterns with @Test macros, #expect/#require assertions, async testing, parameterized tests, and test organization. Apply when writing or modifying tests, setting up test suites, or working with test files." agent_requested: true applies_to: ["/Tests//*.swift", "/*Tests.swift", "/*Test.swift"]

Swift Testing Framework Guidelines

Modern Testing with @Test Macros

Use the Swift Testing framework (not XCTest) for all tests. Tests should be placed in MyProjectPackage/Tests.

Basic Test Structure

import Testing

@Test("User can successfully log in with valid credentials")
func userLogin() async throws {
    let authService = AuthService()
    let result = try await authService.login(
        username: "testuser",
        password: "validpassword"
    )
    
    #expect(result.isSuccess)
    #expect(result.user.name == "Test User")
}

@Test("Login fails with invalid credentials")
func invalidLogin() async throws {
    let authService = AuthService()
    
    await #expect(throws: AuthError.invalidCredentials) {
        try await authService.login(username: "", password: "")
    }
}

Required Patterns

  1. Use @Test macro instead of XCTest's test prefix
  2. Use #expect and #require for assertions, not XCTAssert
  3. Include descriptive test names as string parameters
  4. Test async code with proper async/await patterns
  5. Use #require when test should stop on failure

Key Swift Testing Features

  • @Test: Marks a test function (replaces XCTest's test prefix)
  • @Suite: Groups related tests together
  • #expect: Validates conditions (replaces XCTAssert)
  • #require: Like #expect but stops test execution on failure
  • Parameterized Tests: Use @Test with arguments for data-driven tests
  • async/await: Full support for testing async code
  • Traits: Add metadata like .bug(), .feature(), or custom tags

Read the full file on GitHub · 233 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 233 lines · 44 tokens per session scan A 24dd8184cd9d

Subscribe to this mod's changes

swift-testing is a cursor rule published in the GitHub repository getsentry/XcodeBuildMCP-iOS-Template (43 stars, last pushed 1y ago), licensed MIT. It adds 44 tokens to every session and 1,471 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.