Add Pester Tests to Support branch #1035
Merged
+90
−0
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
Update the pester tests to be consistent with the other Chocolatey repositories.
Motivation and Context
Consistency in Pester test location and behaviour.
Testing
These pester tests are not currently part of any Test Kitchen environment. As such, the only tests we have are a manual running of these tests:
chocolateygui
andpester
packages.Invoke-Pester
in thetests/pester-tests
directory.Note: these are the tests that were done for #1033. The screenshot is copied from there, but the output was the same for the 1.x releases of Chocolatey CLI and Chocolatey GUI.
Operating Systems Testing
Windows 10 22H2
Change Types Made
Change Checklist
Related Issue
N/A