(GH-426) Pin Pester 4 version #439
Closed
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
|
@pauby this has been addressed as part of the work in getting build to work on AppVeyor, and as a result, no longer required. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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
The Pester tests fail to run (locally) if Pester v5 is installed. Pin Pester to latest version 4.
Related Issue
#426
Motivation and Context
This allows the Pester tests to run locally. And will also run when the in the automated build (when they are enabled).
How Has This Been Tested?
While working on #438 I noticed the Pester tests were failing as I had Pester v5 installed. When switching to Pester v4 everything worked as expected.
Types of changes
Checklist: