swift-testing

Swift Testing uses macros like @Test and #expect to define concise, host-less tests that run in parallel by default, eliminating simulator overhead. Tests execute directly in the test process, making them significantly faster than XCTest-based approaches while maintaining full coverage of Swift packages, frameworks, and apps.

Yes. Swift Testing integrates natively with Swift concurrency, letting you write async test functions and use await within test bodies. The framework handles isolation and parallelization automatically, making concurrent code safe and straightforward to test.

Swift Testing replaces XCTest boilerplate with lightweight macros (@Test for functions, #expect for assertions) and runs tests in parallel by default. It eliminates app/simulator launches, integrates directly with Swift concurrency, and supports parameterized tests and trait-based organization without setup complexity.

No. Swift Testing and XCTest coexist in the same project. You can migrate incrementally—add new tests with Swift Testing macros while keeping existing XCTest suites intact. The metadata documents patterns for gradual migration without disrupting your current test suite.

Swift Testing's @Suite macro groups related tests, while traits and tags let you categorize tests by function, platform, or custom criteria. This organization enables selective test runs, parallel execution with safe isolation, and clearer test intent for reliability and maintainability.

Yes. Swift Testing is designed for package-based testing and runs host-less by default, meaning tests execute without an application or simulator. This makes it ideal for testing frameworks and packages in CI/CD pipelines and local development with minimal overhead.