--- title: "Swift Testing explained with code examples" url: https://daily.dev/posts/swift-testing-explained-with-code-examples-pgxkvbvk5 source_url: https://www.avanderlee.com/swift-testing/modern-unit-test type: article source: "SwiftLee" published: 2026-08-17T08:57:09.693Z updated: 2026-08-17T08:57:36.810Z tags: ["testing", "ios", "swift"] reading_time: 9 upvotes: 1 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Swift Testing explained with code examples **[SwiftLee](https://daily.dev/sources/avanderlee)** · 9 min read · 1 upvotes · 0 comments ## Summary Swift Testing is the modern macro-based testing framework that replaces XCTest as the default for new Swift projects, using @Test, #expect, and #require instead of dozens of assertion methods. The guide walks through writing and organizing tests with structs and nested types, parameterized tests to reduce boilerplate, exit tests (available since Swift 6.2 with Xcode 26) for testing fatalError/precondition code paths, attaching values like CSV data or images to test reports, and migrating incrementally from XCTest since UI automation and performance tests still require the older framework. It also mentions an AI Agent Skill the author built to teach coding agents these Swift Testing conventions. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I test fatalError or precondition crashes in Swift Testing? Use an exit test with #expect(processExitsWith:), which runs the test body inside a new child process and validates how that process exits, letting you cover code paths that would otherwise crash the whole test run. Exit tests require Swift 6.2 and Xcode 26 or later, run on macOS and Linux but not iOS, and any captured value must conform to both Sendable and Codable. _Developers hardening crash paths can track Swift Testing capabilities like this on daily.dev._ ### What is the difference between #expect and #require in Swift Testing? #expect records a failure but continues running the test, while #require throws and stops the test immediately if the condition fails, similar to XCTUnwrap for unwrapping optionals. #require is typically used when a later assertion in the test depends on a value being present, such as unwrapping a struct before checking its properties. _Teams migrating XCTest suites can compare macro behavior like this via daily.dev._ ### Can I still use XCTest alongside Swift Testing in the same project? Yes, both frameworks can coexist in the same test target, so migration can happen incrementally by converting assertions first, then reorganizing suites, and finally adding parameterized tests. UI automation tests using XCUIApplication and performance tests using XCTMetric still require XCTest and are not expected to migrate. _Anyone planning a gradual test-suite migration can follow updates like this on daily.dev._ ## Similar posts on daily.dev - [Swift Testing Agent Skill: Write high quality tests with AI](https://daily.dev/posts/swift-testing-agent-skill-write-high-quality-tests-with-ai-tbmj7iytj) · SwiftLee · 0 upvotes · 0 comments --- Tags: [#testing](https://daily.dev/tags/testing), [#ios](https://daily.dev/tags/ios), [#swift](https://daily.dev/tags/swift) [View this post on daily.dev](https://daily.dev/posts/swift-testing-explained-with-code-examples-pgxkvbvk5)