Add steps to test Swift pakcage on all supported Apple platforms #43
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The tvOS step produced an incorrect result: It should have failed because there is no tvOS SDK in the Xcode 15.2 image. |
jkmassel
approved these changes
Mar 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently we use
swift testto run SPM unit tests, which covers macOS and Linux. This PR adds steps to cover other Apple platforms, usingxcodebuild test.Test Instructions
The happy path should be covered by CI jobs.
You can test the new make targets fail if simulator doesn't exist. For example,
scripts/xcodebuild-test.sh watchOS-11should fail.