Repository navigation
Clean up test code to use -Parameter syntax for Pester tests #6245
Description
Activity
- addedIssue-Code Cleanupthe issue is for cleaning up the code with no impact on functionalitythe issue is for cleaning up the code with no impact on functionality
on 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 Mark Kraus (@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.
- addedIssue-Metaan issue used to track multiple issuesan issue used to track multiple issues
on Feb 26, 2018 SteveL-MSFT commented
on Feb 26, 2018 MemberAuthorMore actionsIlya (@iSazonov) breaking it up makes sense!
bergmeister commented
on Feb 26, 2018 ContributorMore actions- added 4 commits that reference this issue
on Mar 24, 2018 KevinMarquette commented
on Mar 24, 2018 ContributorMore actionsKevinMarquette commented
on Mar 26, 2018 ContributorMore actionsI have a PR out for the LocalAccounts module #6499
#6499 was not merged
Ilya (@iSazonov) Can you reopen?
xtqqczze The Microsoft.PowerShell.LocalAccounts module was removed from PowerShell Core.
Ilya (@iSazonov) There is an issue to remplement (#4305) so we should still update pester syntax.
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 -Beinstead ofShould Besyntax. We should update all our tests and documentation to adhere to this setting a good example for the community.