-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Verify Pester 4 usage and unload Pester 5 if present #25531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are too many unrelated changes, which complicates the review. Could you please delete them?
@iSazonov sorry, the Powershell vscode formatter went nuts and I didn't mean to commit. I'll fix, stand by. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
@iSazonov looks like it needs a re-review after a tag add for some reason. |
/azp run PowerShell-CI-linux-packaging,PowerShell-Windows-Packaging-CI |
Azure Pipelines successfully started running 2 pipeline(s). |
This one is still stuck. I think it needs @TravisEz13 or @jshigetomi approval |
Ensure that Pester 4 is used for testing, while unloading Pester 5 if it is currently loaded. This helps avoid confusing error messages for users who have Pester 5 installed.