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
Line where call operator is used is reported as not covered by Pester's codeCoverage capabilty.
ie : $scriptCmd = {& $wrappedCmd @PSBoundParameters }
Code coverage report :
File Function Line Command
Pester version : 4.4.2 C:\Program Files\WindowsPowerShell\Modules\Pester\4.4.2\Pester.psm1
PowerShell version : 5.1.14409.1005
OS version : Microsoft Windows NT 6.1.7601 Service Pack 1
3. Expected Behavior
Report this line as covered
4.Current Behavior
Missing coverage
5. Possible Solution
Tag or mark a line as "excluded" from coverage report ?
6. Context
I'm trying to get a 100% covered code but got only 98% cause of this line :-/
Thanks for help or advise ;)
The text was updated successfully, but these errors were encountered:
@KreizIT Thans for the issue, the code coverage works by setting breakpoints, so it's possible that we either missed it or the breakpoint cannot be set there. Will review this.
1. General summary of the issue
Line where call operator is used is reported as not covered by Pester's codeCoverage capabilty.
ie : $scriptCmd = {& $wrappedCmd @PSBoundParameters }
Code coverage report :
File Function Line Command
ProxyCmd.ps1 Write-TrueHost 29 $scriptCmd = {& $wrappedCmd @PSBoundParameters }
ProxyCmd.ps1 Write-TrueHost 29 & $wrappedCmd @PSBoundParameters
2. Describe Your Environment
Pester version : 4.4.2 C:\Program Files\WindowsPowerShell\Modules\Pester\4.4.2\Pester.psm1
PowerShell version : 5.1.14409.1005
OS version : Microsoft Windows NT 6.1.7601 Service Pack 1
3. Expected Behavior
Report this line as covered
4.Current Behavior
Missing coverage
5. Possible Solution
Tag or mark a line as "excluded" from coverage report ?
6. Context
I'm trying to get a 100% covered code but got only 98% cause of this line :-/
Thanks for help or advise ;)
The text was updated successfully, but these errors were encountered: