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
Pester v5 migration #815
Pester v5 migration #815
Conversation
Currently The ConstrainedLanguage tests from The error log:
@BernieWhite If needed I can track this in a issue 🙂. Definetely seems Pester v5 related, will see if I can figure it out. |
@ArmaanMcleod Constrained language is when PowerShell is operating in a locked down environment. These failures check language is limited in these environments. The check is mocked for pester 4 tests, probably double check that is working. |
@BernieWhite Yeah knew it was something small. I forgot to move the mocks into Thanks for spotting that, needed an extra pair of eyes since the tests all start looking the same after a while when doing these migrations😄 . In any case I've learnt what ConstrainedLanguage does, thanks for explanation mate 🙂 . |
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.
@ArmaanMcleod Great work! All good to merge.
PR Summary
Fix #478
Converted to pester v5 tests syntax and v5.3.0 module version.
PR Checklist