Can't run Pester Tests in PowerShell Extension

[randyram-at-ms]

Issue Type: Bug

From a file with a Pester test, hit Run tests:

Invoke-Pester : A parameter cannot be found that matches parameter name 'Show'.
At C:\Users\<deleted>\.vscode\extensions\ms-vscode.powershell-2020.4.0\InvokePesterStub.ps1:137 char:113
+ ... Option @{IncludeVSCodeMarker=$true} -TestName $TestName -Show $pester ...
+                                                             ~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Invoke-Pester], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Invoke-Pester

PS>

Extension version: 2020.4.0
VS Code version: Code 1.44.2 (ff915844119ce9485abfe8aa9076ec76b5300ddd, 2020-04-16T16:36:23.138Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item	Value
CPUs	Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz (12 x 3592)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off_ok webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.92GB (15.10GB free)
Process Argv	.
Screen Reader	no
VM	0%

[TylerLeonhardt]

@randyram-at-ms what version of Pester are you using?

Get-Module -list Pester

cc @nohwnd

[randyram-at-ms]

3.4.0 From: Tyler James Leonhardt <notifications@github.com> Sent: Thursday, April 30, 2020 10:49 AM To: PowerShell/vscode-powershell <vscode-powershell@noreply.github.com> Cc: Randy Ramig <randyram@exchange.microsoft.com>; Mention <mention@noreply.github.com> Subject: Re: [PowerShell/vscode-powershell] Can't run Pester Tests in PowerShell Extension (#2673) @randyram-at-ms<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frandyram-at-ms&data=02%7C01%7Crandyram%40exchange.microsoft.com%7C5efb22b19c504828b5e708d7ed2ebeb6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637238657339187818&sdata=QLm%2BprV0YqZNCFVn8O%2BWhJiFb4cPrgOX5lYO2u6%2BclY%3D&reserved=0> what version of Pester are you using? Get-Module -list Pester cc @nohwnd<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnohwnd&data=02%7C01%7Crandyram%40exchange.microsoft.com%7C5efb22b19c504828b5e708d7ed2ebeb6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637238657339187818&sdata=nSExeiww8fpYbTehpLo7LHEr7f5QSypmiPyszGGvOSw%3D&reserved=0> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPowerShell%2Fvscode-powershell%2Fissues%2F2673%23issuecomment-622004903&data=02%7C01%7Crandyram%40exchange.microsoft.com%7C5efb22b19c504828b5e708d7ed2ebeb6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637238657339197779&sdata=T8JHuwGnYHeF7zcOn3%2BQB%2F4dlgS6ioWAoeird646tGo%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMFCZSMBUGZLP7RTYCS4AFLRPG2YHANCNFSM4MUIJHYQ&data=02%7C01%7Crandyram%40exchange.microsoft.com%7C5efb22b19c504828b5e708d7ed2ebeb6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637238657339197779&sdata=ppZLMZN%2ByfU%2FrUOSjKdTDqHTO%2FQHSWYXQyNDiKXgJxU%3D&reserved=0>.

[SydneyhSmith]

@randyram-at-ms looks like you are using an older version of Pester, are you able to update to the latest version and see if this issue still repros? This will help us determine if the cause is specific to this version of the module

[randyram-at-ms]

I could… but I’m using RTM Windows 10 Enterprise Version 1909, build 18363.778 and simply using the powershell that comes with that Windows build. Seems you’d want to avoid people having to upgrade powershell to fix this – it was working fine for me a month ago so there’s clearly an issue with the vscode-powershell upgrade on my box. Still willing to update powershell if it helps you debug. From: Sydney Smith <notifications@github.com> Sent: Thursday, April 30, 2020 2:08 PM To: PowerShell/vscode-powershell <vscode-powershell@noreply.github.com> Cc: Randy Ramig <randyram@exchange.microsoft.com>; Mention <mention@noreply.github.com> Subject: Re: [PowerShell/vscode-powershell] Can't run Pester Tests in PowerShell Extension (#2673) @randyram-at-ms<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frandyram-at-ms&data=02%7C01%7Crandyram%40exchange.microsoft.com%7C4683da5b130a4f7cd88308d7ed4a9d2f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637238777041632640&sdata=WlFmNsS6AJVpgDaz4%2Ba7Z0xOKdPJ23gb5knRZ%2FaUkww%3D&reserved=0> looks like you are using an older version of Pester, are you able to update to the latest version and see if this issue still repros? This will help us determine if the cause is specific to this version of the module — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPowerShell%2Fvscode-powershell%2Fissues%2F2673%23issuecomment-622113074&data=02%7C01%7Crandyram%40exchange.microsoft.com%7C4683da5b130a4f7cd88308d7ed4a9d2f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637238777041642634&sdata=6CZSPFz3r0MgBZ%2FXjV9RLdNxzDwBz39Ui5k7ztefVOI%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMFCZSMV3SHNTBCZAOAESBTRPHSELANCNFSM4MUIJHYQ&data=02%7C01%7Crandyram%40exchange.microsoft.com%7C4683da5b130a4f7cd88308d7ed4a9d2f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637238777041642634&sdata=QqdzHXUfLJVm1wB%2Baq27WaBedvjYQBlW8JwBmxYNkBA%3D&reserved=0>.

[TylerLeonhardt]

Well the ask was to just update Pester, not PowerShell itself.

This will update to the latest v4 of Pester.

Install-Module -Name Pester -Force -MaximumVersion 4.99.99

That should unblock you though I'm not sure how compatible v3 Pester tests are for v4.

I think we just need to not include the -Show parameter for v3 Pester:
https://github.com/PowerShell/vscode-powershell/blob/master/InvokePesterStub.ps1#L109

[TylerLeonhardt]

Actually if you wanna just update the script here:

$HOME\.vscode\extensions\ms-vscode.powershell-2020.4.0\InvokePesterStub.ps1

to not include the -Show parameter in any of the Invoke-Pester calls... that should unblock you too.

[rkeithhill]

Heh, I thought at the time we did this that teasing out this logic into an accessible PS script would come in handy. :-)