reviewing-test-quality

To review Swift test quality, analyze unit and integration tests across multiple files to identify coverage gaps, testability issues, and formatting inconsistencies, then propose concrete improvements using Swift Testing conventions.

Enforcing Swift Testing conventions requires checking that tests use @Test and @Suite attributes correctly, reference FitnessTestSupport utilities, and align with project architecture documentation for consistent test organization.

Yes, analyzing multiple Swift test files for style and DRY violations is supported for production-grade reviews of 3 or more files, with guidance on isolating context to assess test organization and formatting inconsistencies.

The best way to identify testability issues in Swift integration tests is to evaluate assertions, coverage gaps, and test structure against FitnessTestSupport utilities and architecture documentation to pinpoint areas needing concrete fixes.

Yes, the test review process works directly with Swift Packages by analyzing tests located in Packages/*/Tests directories, evaluating them for Swift Testing conventions, coverage gaps, and FitnessTestSupport utility usage.

Inconsistent formatting and organization across Swift test targets often stems from missing DRY utilities, lack of standardized @Test/@Suite conventions, and misalignment with FitnessTestSupport utilities and architecture documentation.