Unify UI Tests and Enforce Swift 6.3#25
Conversation
|
Important Review skippedToo many files! This PR contains 155 files, which is 105 over the limit of 50. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (28)
📒 Files selected for processing (564)
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…fixBuilds # Conflicts: # Package.swift # Sources/SpeziLocation/LocationTasks/LocationTaskManager.swift # Sources/XCTRuntimeAssertions/Deprecations.swift # Sources/XCTRuntimeAssertions/XCTRuntimePrecondition.swift
♻️ Current situation & Problem
The monorepo's UI-test projects duplicated configuration across packages and had drifted from current Xcode defaults. Moving the package to Swift 6.3 and Xcode 27 also exposed concurrency diagnostics, nondeterministic unit/UI tests, and legacy runtime-assertion test infrastructure that is now superseded by Swift Testing's native exit tests.
No related issue was identified.
⚙️ Release Notes
XCTRuntimeAssertionsproduct and migrate repository consumers to Swift 6.3 native exit tests on macOS. Deprecate allRuntimeAssertionsTestingAPIs on every platform while retaining their compatibility self-tests.XCTRuntimeAssertionsremoval is a breaking change for test targets that import it. Migrate assertion/precondition tests to native Swift Testing exit tests:📚 Documentation
✅ Testing
python3 Scripts/generate-ui-test-projects.py --checkswift package dump-packagewith Swift 6.3The complete unit/UI and deployment-floor matrix is also validated by PR CI.
Code of Conduct & Contributing Guidelines
By creating and submitting this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: