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
Clean up test code to use -Parameter
syntax for Pester tests
#6245
Comments
Maybe Meta-Issue? I'd rather break the work apart otherwise we'll get a huge size PR which is hard to review. I guess @markekraus grabs web cmdlet tests. I could grab something else, rest utility cmdlet tests. |
hehe I planned to do this with the web cmdlet tests, yes. |
@iSazonov breaking it up makes sense! |
I have a PR out for the LocalAccounts module #6499 |
#6499 was not merged |
@iSazonov Can you reopen? |
@xtqqczze The Microsoft.PowerShell.LocalAccounts module was removed from PowerShell Core. |
@xtqqczze It is impossible to get Microsoft.PowerShell.LocalAccounts module based on other API. We have to implement new module and new tests. (See my WIP PR for AccountManagement module) |
Pester documentation for 4.x recommends using
Should -Be
instead ofShould Be
syntax. We should update all our tests and documentation to adhere to this setting a good example for the community.The text was updated successfully, but these errors were encountered: