Stop flooding Swift Package Manager projects with Firebase test schemes #8212
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
Coverage ReportAffected SDKs
Test Logs
|
maksymmalyhin
approved these changes
Jun 8, 2021
| * Add `CODE_SIGNING_REQUIRED` setting with a value of `NO` | ||
|
|
||
| ### Swift Package Manager | ||
| * To enable test schemes: `./scripts/setup_spm_tests.sh` |
There was a problem hiding this comment.
I'm afraid I will miss this step all the time in the future 😄
There was a problem hiding this comment.
Yep, it's annoying, but as far as I can tell worth it because of the product advantages for clients. 😛
ncooke3
approved these changes
Jun 8, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
Fix #8167
Move SPM test schemes into place only for CI and internal development. Additional context at https://forums.swift.org/t/swiftpm-and-library-unit-testing/26255/21
Also, updated schemes with enabling analyzer to mitigate conflicts with in-flight #8208, #8209, and #8210