Tests: Run packageInitExecutable test on all platforms for native build system #8527
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.
Motivation:
Increase code coverage for our integration tests.
This is an issue I introduced in #8454 while ignoring
--build-system swiftbuild
issues on Windows (i.e., actually this specific issue #8514). I accidentally skipped thepackageInitExecutable
test for--build-system native
as well (which should be green). This PR fixes that.Modifications:
Swift Testing currently doesn't support combining conditional traits (e.g.,
skipHostOS(.windows)
) with parametric tests — I double-checked with @stmontgomery. So the 2nd best approach is to split the tests as I just did.Result:
Slightly Increased test coverage for integration tests :-)