add test coverage for additional Get-Module parameters#8137
Conversation
0712608 to
529264c
Compare
rjmholt
left a comment
There was a problem hiding this comment.
This looks like important coverage to me!
One thing that strikes me is the name of the file (which I know is pre-existing). The tests here all cover Get-Module -ListAvailable scenarios, where Get-Module scenarios are mostly covered in ModuleConstraint.Tests.ps1 and the CompatiblePSEditions checks are covered in CompatiblePSEditions.Tests.ps1 (different to the ones here, they don't filter by PSEdition explicitly but do the implicity manifest check for modules on the Windows PowerShell module path).
|
@KevinMarquette Please address @rjmholt feedback about file names. |
|
Oh sorry, my feedback isn't terribly clear. I would support changing the file name to something like |
|
@adityapatwardhan We need your help. |
test/powershell/Modules/Microsoft.PowerShell.Core/Get-Module.Tests.ps1
Outdated
Show resolved
Hide resolved
test/powershell/Modules/Microsoft.PowerShell.Core/Get-Module.Tests.ps1
Outdated
Show resolved
Hide resolved
|
For the organization of test cases to make them discoverable, I think it's out of scope for this PR and should be a separate PR. |
7f7add8 to
27fdb7b
Compare
test/powershell/Modules/Microsoft.PowerShell.Core/Get-Module.Tests.ps1
Outdated
Show resolved
Hide resolved
test/powershell/Modules/Microsoft.PowerShell.Core/Get-Module.Tests.ps1
Outdated
Show resolved
Hide resolved
|
@KevinMarquette Thanks for your contribution! |
PR Summary
add test coverage for
Get-ModuleparametersFullyQualifiedName,PSEditionandRefreshPR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.[feature]if the change is significant or affects feature tests