Swift Testing Code Review

Hard gates

Complete in order before recording Swift Testing review findings. Stack with review-verification-protocol for universal review rules.

Scope: You have an explicit list of .swift paths under review (or a user-named single file). Pass: Paths captured in working notes or one line: No Swift files in scope — then stop with no findings.
Swift Testing surface: For each path you treat as Swift Testing code, confirm import Testing or @Test / #expect / #require / @Suite appears in that file (open or search). Pass: At least one match per critiqued file, or you exclude that file from Swift Testing review with a one-line reason (e.g. XCTest-only).
Evidence + protocol: Load review-verification-protocol before asserting any issue. Pass: Each finding meets that skill’s anchor rules; any violated Review Checklist item cites [FILE:LINE] evidence. If you report zero issues, state Protocol applied; no Swift Testing issues (or equivalent) in the review summary.

Issue Type	Reference
#expect vs #require, expression capture, error testing	references/expect-macro.md
@Test with arguments, traits, zip() pitfalls	references/parameterized.md
confirmation, async sequences, completion handlers	references/async-testing.md
@Suite, tags, parallel execution, .serialized	references/organization.md