You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixed crash when running pester older than 3.4.5 (#2888)
* Fixed crash when running pester older than 3.4.5
Calling Invoke-Pester with the -show param was
breaking tests if running a version of pester
older than 3.4.5
Moved logic for building spalt to call
invoke-pester into a function and only added the
show parameter if running pester 3.4.5 or newer
* Update InvokePesterStub.ps1
Co-authored-by: Tyler James Leonhardt <[email protected]>
* Update InvokePesterStub.ps1
Co-authored-by: Tyler James Leonhardt <[email protected]>
Co-authored-by: Tyler James Leonhardt <[email protected]>
if ($MinimumVersion5-and$pesterModule.Version-lt"5.0.0") {
90
-
Write-Warning"Pester 5.0.0 or newer is required because setting PowerShell > Pester: Use Legacy Code Lens is disabled, but Pester $($pesterModule.Version) is loaded. Some of the code lense features might not work as expected."
90
+
Write-Warning"Pester 5.0.0 or newer is required because setting PowerShell > Pester: Use Legacy Code Lens is disabled, but Pester $($pesterModule.Version) is loaded. Some of the code lens features might not work as expected."
91
91
}
92
92
93
93
94
+
functionGet-InvokePesterParams {
95
+
$invokePesterParams=@{
96
+
Script=$ScriptPath
97
+
}
98
+
99
+
if ($pesterModule.Version-ge'3.4.0') {
100
+
# -PesterOption was introduced before 3.4.0, and VSCodeMarker in 4.0.3-rc,
101
+
# but because no-one checks the integrity of this hashtable we can call
0 commit comments