[path_provider_foundation] Migrate XCTest to Swift Testing

[jmagman]

Part of flutter/flutter#180787

Migrate testGet*Directory tests to one parameterized tests.

Test suite 'RunnerTests' started on 'Clone 1 of Flutter-iPhone - Runner (7112)'
Test case 'RunnerTests/getApplicationSupportDirectory()' passed on 'Clone 1 of Flutter-iPhone - Runner (7112)' (0.000 seconds)
Test case 'RunnerTests/directoryPath(directoryType:searchPathDirectory:)' passed on 'Clone 1 of Flutter-iPhone - Runner (7112)' (0.000 seconds)
Test case 'RunnerTests/directoryPath(directoryType:searchPathDirectory:)' passed on 'Clone 1 of Flutter-iPhone - Runner (7112)' (0.001 seconds)
Test case 'RunnerTests/directoryPath(directoryType:searchPathDirectory:)' passed on 'Clone 1 of Flutter-iPhone - Runner (7112)' (0.002 seconds)
Test case 'RunnerTests/directoryPath(directoryType:searchPathDirectory:)' passed on 'Clone 1 of Flutter-iPhone - Runner (7112)' (0.002 seconds)
Successfully ran iOS xctest for packages/path_provider/path_provider_foundation/example

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8693104410263501761/+/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 native tests from XCTest to the new Swift Testing framework. The changes are logical and correctly adopt the new APIs like @Test and #expect. I've provided one suggestion to improve test robustness by replacing force unwraps with the idiomatic #require macro from Swift Testing, which will prevent potential test crashes.

[jmagman]

Xcode gonna Xcode, let it touch these files.

[stuartmorgan-g]

For all of the PRs, I would revert this and use the override label instead. These changes fall under the "unless they only affect development of the package, such as test-only changes" exemption for needing CHANGELOG changes.