What problem does it solve? Swift Testing uses macros and result reporting that differ sharply from XCTest, so developers migrating test suites or reading xcodebuild output often misjudge whether tests actually ran, passed, or crashed. ## Core Features & Use Cases - Macro-driven test authoring: Write tests with @Test, #expect, #require, and Issue.record, including async, throwing, and parameterized cases. - Staged XCTest migration: Convert XCTest targets to Swift Testing incrementally while keeping the target green, since both frameworks run side by side. - Result bundle diagnosis: Read fresh xcresult bundles with xcresulttool to detect zero-test runs, crashes, and environmental faults that console output hides. - Use Case: A run reports "Executed 0 tests" after renaming a suite; use this Skill to verify the -only-testing selection, inspect the result bundle, and confirm the real test count. ## Quick Start Help me migrate my XCTest target to Swift Testing and verify the results from the xcodebuild result bundle.