swift-testing-guidelines

To write Swift StateTree tests, annotate functions with @Test, replace XCTest assertions with #expect, and use Issue.record for failures. Follow the Arrange-Act-Assert pattern across core library, transport, and macros modules.

Migrate XCTest assertions by replacing them with #expect for conditions and Issue.record for explicit failures. The Swift Testing framework enforces this pattern to align test style and avoid common pitfalls across StateTree modules.

Yes, the Swift Testing framework supports async tests for Swift StateTree. You can use @Test annotations for async functions and apply #expect assertions to validate asynchronous state changes and transport operations.

No, you should avoid XCTest for Swift StateTree feature tests. The guidelines enforce using the Swift Testing framework with @Test and #expect to ensure correct, maintainable test coverage across core modules like matchmaking and transport.

Organize Swift Testing files by applying module organization guidance for each StateTree module, such as core library, transport, and macros. Use @Test annotations and #expect to maintain consistent test style across the project.

Swift StateTree tests require Issue.record to report failures instead of XCTFail. This enforces the Swift Testing framework's structured approach, ensuring failures are recorded correctly during feature tests and test-quality reviews.