[url_launcher_macos] Migrate XCTest to Swift Testing

[jmagman]

Part of flutter/flutter#180787

Add some test parameterization.

Also, only two of the tests were using the StubWorkspace, so were actually integration testing my local Mac's ability to canLaunch URLs. Swap them all to use the stub.

◇ Test run started.
↳ Testing Library Version: 102 (arm64e-apple-macos13.0)
◇ Suite RunnerTests started.
◇ Test launch(url:isSuccessful:) started.
◇ Test launchInvalidUrlReturnsError() started.
◇ Test canLaunch(url:isSuccessful:) started.
◇ Passing 2 arguments url → "https://flutter.dev/", isSuccessful → true to launch(url:isSuccessful:)
◇ Passing 2 arguments url → "schemethatdoesnotexist://flutter.dev", isSuccessful → false to launch(url:isSuccessful:)
◇ Test canLaunchInvalidUrlReturnsError() started.
◇ Passing 2 arguments url → "https://flutter.dev/", isSuccessful → true to canLaunch(url:isSuccessful:)
◇ Passing 2 arguments url → "example://flutter.dev", isSuccessful → false to canLaunch(url:isSuccessful:)
​​✔ Test launchInvalidUrlReturnsError() passed after 0.001 seconds.
​✔ Test canLaunchInvalidUrlReturnsError() passed after 0.001 seconds.
✔ Test launch(url:isSuccessful:) passed after 0.030 seconds.
​✔ Test canLaunch(url:isSuccessful:) passed after 0.030 seconds.
✔ Suite RunnerTests passed after 0.030 seconds.
✔ Test run with 4 tests passed after 0.030 seconds.

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

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 successfully migrates the url_launcher_macos tests from XCTest to the new Swift Testing framework. The changes are well-executed, leveraging test parameterization to reduce boilerplate and combine related test cases. A significant improvement is the consistent use of StubWorkspace across all tests, converting what were previously integration tests into true unit tests. I've included one suggestion to further improve code reuse within the test suite.

[jmagman]

Adding CHANGELOG override per #10761 (comment)