domains / families / software-engineering / swift-testing

swift-testing

separate

Writes and migrates Swift Testing framework tests with @Test, @Suite, #expect, #require, confirmation, traits, withKnownIssue, Attachment.record, processExitsWith exit tests and capture lists, Test.cancel, Issue.record warnings/manual failures, XCTest-to-Swift Testing migration, Xcode 27 interoperability modes, XCUITest UI-test boundaries, performance/snapshot boundaries, mocking, async patterns, and test organization. Use when writing tests, converting XCTest assertions such as XCTUnwrap or XCTFail, reviewing advanced Swift Testing API availability, or deciding when to keep XCTest/XCUITest.

When to use

• Writing Swift Testing framework tests
• Migrating XCTest to Swift Testing
• Using @Test, @Suite, #expect, and #require
• Handling test traits and known issues
• Managing test attachments and exit tests
• Reviewing advanced Swift Testing API availability
• Deciding when to keep XCTest or XCUITest
• Configuring Xcode 27 interoperability modes

When not to use

• UI automation tests
• Performance benchmarks
• Objective-C exception tests
• Common snapshot-test tooling

Skill page

Source