Skip to content
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

Closed
20 tasks done
SteveL-MSFT opened this issue Feb 26, 2018 · 11 comments
Closed
20 tasks done

Clean up test code to use -Parameter syntax for Pester tests #6245

SteveL-MSFT opened this issue Feb 26, 2018 · 11 comments
Labels
Issue-Code Cleanup the issue is for cleaning up the code with no impact on functionality Issue-Meta an issue used to track multiple issues Resolution-Fixed The issue is fixed.

Comments

@SteveL-MSFT
Copy link
Member

SteveL-MSFT commented Feb 26, 2018

Pester documentation for 4.x recommends using Should -Be instead of Should Be syntax. We should update all our tests and documentation to adhere to this setting a good example for the community.

@SteveL-MSFT SteveL-MSFT added the Issue-Code Cleanup the issue is for cleaning up the code with no impact on functionality label Feb 26, 2018
@SteveL-MSFT SteveL-MSFT added this to the 6.1.0-MQ milestone Feb 26, 2018
@iSazonov
Copy link
Collaborator

iSazonov commented Feb 26, 2018

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.

@markekraus
Copy link
Contributor

hehe I planned to do this with the web cmdlet tests, yes.

@SteveL-MSFT SteveL-MSFT added the Issue-Meta an issue used to track multiple issues label Feb 26, 2018
@SteveL-MSFT
Copy link
Member Author

@iSazonov breaking it up makes sense!

@bergmeister
Copy link
Contributor

bergmeister commented Feb 26, 2018

I haven't tried it yet but here is a helper script to help with with upgrading to the new syntax. I have seen it being used by the xDFS repo already.

KevinMarquette added a commit to loanDepot/PowerShell that referenced this issue Mar 24, 2018
KevinMarquette added a commit to loanDepot/PowerShell that referenced this issue Mar 24, 2018
KevinMarquette added a commit to loanDepot/PowerShell that referenced this issue Mar 24, 2018
@KevinMarquette
Copy link
Contributor

I have a PR out for these items on the list:
PowerShellGet, PackageManagement, PSReadLine #6488
SDK and Provider tests #6490

@KevinMarquette
Copy link
Contributor

I have a PR out for the LocalAccounts module #6499

@kalgiz kalgiz closed this as completed Apr 26, 2018
@iSazonov iSazonov added the Resolution-Fixed The issue is fixed. label Apr 26, 2018
@xtqqczze
Copy link
Contributor

#6499 was not merged

@xtqqczze
Copy link
Contributor

@iSazonov Can you reopen?

@iSazonov
Copy link
Collaborator

@xtqqczze The Microsoft.PowerShell.LocalAccounts module was removed from PowerShell Core.

@xtqqczze
Copy link
Contributor

@iSazonov There is an issue to remplement (#4305) so we should still update pester syntax.

@iSazonov
Copy link
Collaborator

@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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Code Cleanup the issue is for cleaning up the code with no impact on functionality Issue-Meta an issue used to track multiple issues Resolution-Fixed The issue is fixed.
Projects
None yet
Development

No branches or pull requests

7 participants