(#508) Add Pester tests for unsupported metadata #2969
Merged
Conversation
This file contains 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
Adds some end to end tests for how choco behaves when handling a package with unsupported metadata elements in the nuspec.
gep13
force-pushed
the
tests/unsupported-metadata
branch
from
f1be3e6 to
51a8f8f
Compare
|
@vexx32 thanks for pulling these together! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Description Of Changes
Motivation and Context
We should have some tests confirming the end-user behaviour of package installs and packs when choco finds unsupported elements in the nuspec metadata.
Testing
The added tests should pass with no issues.
Operating Systems Testing
Win11
Change Types Made
Change Checklist
Related Issue
#508