[url_launcher_ios] Migrate XCTest to Swift Testing

[jmagman]

Part of flutter/flutter#180787

Add some test parameterization.

◇ Test run started.
↳ Testing Library Version: 102 (arm64-apple-ios13.0-simulator)
◇ Suite URLLauncherTests started.
◇ Test canLaunchFailureWithInvalidURL() started.
◇ Test canLaunch(url:expected:) started.
◇ Test launchWithUniversalLinks() started.
◇ Test launch(url:expected:) started.
◇ Test launchSafariViewControllerWithClose() started.
◇ Test launchSafariViewControllerFailureWithNoViewPresenter() started.
◇ Test launchWithoutUniversalLinks() started.
◇ Test launchFailureWithInvalidURL() started.
◇ Passing 2 arguments url → "good://url", expected → .success to launch(url:expected:)
◇ Passing 2 arguments url → "bad://url", expected → .failure to launch(url:expected:)
2026-01-12 12:53:39.222409-0800 Runner[62355:494810] [Warning] Attempting to load the view of a view controller while it is deallocating is not allowed and may result in undefined behavior (<SFSafariViewController: 0x1018cd200>)
◇ Passing 2 arguments url → "bad://url", expected → .failure to canLaunch(url:expected:)
◇ Passing 2 arguments url → "good://url", expected → .success to canLaunch(url:expected:)
✔ Test canLaunchFailureWithInvalidURL() passed after 0.001 seconds.
✔ Test launchWithUniversalLinks() passed after 0.001 seconds.
✔ Test launchSafariViewControllerWithClose() passed after 0.042 seconds.
✔ Test launchWithoutUniversalLinks() passed after 0.042 seconds.
✔ Test launchSafariViewControllerFailureWithNoViewPresenter() passed after 0.042 seconds.
✔ Test launchFailureWithInvalidURL() passed after 0.042 seconds.
​​​​✔ Test launch(url:expected:) passed after 0.043 seconds.
✔ Test canLaunch(url:expected:) passed after 0.043 seconds.
✔ Suite URLLauncherTests passed after 0.043 seconds.
✔ Test run with 8 tests passed after 0.043 seconds.

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8692848274232556065/+/u/Run_package_tests/native_test/stdout

Adding CHANGELOG override per #10761 (comment)

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under¹.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩² ↩³

[gemini-code-assist]

Code Review

This pull request migrates the url_launcher_ios unit tests from XCTest to Swift Testing. This involves updating the Swift version to 6.0 in the project configuration and rewriting the tests in URLLauncherTests.swift. The XCTest APIs are replaced with Swift Testing APIs, such as using @Test instead of XCTestCase methods, #expect for assertions, and await confirmation for asynchronous operations. Some tests have been combined and parameterized, such as canLaunch and launch, reducing code duplication.

[jmagman]

2026-01-12 12:53:39.222409-0800 Runner[62355:494810] [Warning] Attempting to load the view of a view controller while it is deallocating is not allowed and may result in undefined behavior (<SFSafariViewController: 0x1018cd200>)

Hm that doesn't look good...

[jmagman]

2026-01-12 12:53:39.222409-0800 Runner[62355:494810] [Warning] Attempting to load the view of a view controller while it is deallocating is not allowed and may result in undefined behavior (<SFSafariViewController: 0x1018cd200>)

Hm that doesn't look good...

Actually this warning was happening before my change, probably because TestViewPresenter mocks the presentation, so the view isn't actually loaded, which causes weirdness:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8692766281012941425/+/u/Run_package_tests/native_test/stdout#L24622_0

I'll ignore it since it's not related to the Swift Testing change.

[gemini-code-assist]

Code Review

This pull request successfully migrates the url_launcher_ios example tests from XCTest to the modern Swift Testing framework. The changes include updating the project to Swift 6.0, refactoring test classes into @MainActor structs, and adopting new Swift Testing APIs like @Test, #expect, and async confirmations. A notable improvement is the use of parameterized tests, which consolidates several test cases and makes the test suite more concise. My review focuses on ensuring the migration correctly preserves the original testing intent, especially regarding how error conditions are handled.