Details of the scenario you tried and the problem that is occurring
It is very complicated to get the code coverage for a certan function or class through CLI. Suggest adding a command that can make it less difficult:
Invoke-PesterWithCodeCoverage: runs Pester with required configuration and returns a PesterObject. The command should take an optional PesterConfiguration parameter, but use default if not specified.
Get-CodeCoverageResult: The command should take the parameters:
PesterObject (mandatory)
Name (optional, array of class and function names being tested)
AddSource (optional, only applicable when built module using ModuleBuilder)
Type (optional, either Missed, Executed or All - defaults to Missed only)
Should add a new property Type to the resulting objects with Missed or Executed
Returns the CommandsMissed
$config = New-PesterConfiguration
$config.Run.Path = @('<test paths>')
$config.CodeCoverage.Enabled = $true
$config.CodeCoverage.Path = @('./output/builtModule/<ModuleName>')
$config.CodeCoverage.CoveragePercentTarget = 0
$config.Output.Verbosity = 'None'
$config.Run.PassThru = $true
$result = Invoke-Pester -Configuration $config
# After running above, get all commands that was missed with a reference to the SourceLineNumber in SourceFile.
$result.CodeCoverage.CommandsMissed | Where-Object { $_.Function -eq '<FunctionName>' -or $_.Class -eq '<ClassName>' } | Convert-LineNumber -PassThru | Select-Object Class, Function, Command, SourceLineNumber, SourceFile
Steps to reproduce the problem
Expected behavior
Current behavior
Suggested solution to the issue
The operating system the target node is running
Version and build of PowerShell the target node is running
Version of the module that was used
Details of the scenario you tried and the problem that is occurring
It is very complicated to get the code coverage for a certan function or class through CLI. Suggest adding a command that can make it less difficult:
Invoke-PesterWithCodeCoverage: runs Pester with required configuration and returns a PesterObject. The command should take an optionalPesterConfigurationparameter, but use default if not specified.Get-CodeCoverageResult: The command should take the parameters:PesterObject(mandatory)Name(optional, array of class and function names being tested)AddSource(optional, only applicable when built module using ModuleBuilder)Type(optional, either Missed, Executed or All - defaults to Missed only)Should add a new property
Typeto the resulting objects withMissedorExecutedReturns the CommandsMissed
Steps to reproduce the problem
Expected behavior
Current behavior
Suggested solution to the issue
The operating system the target node is running
Version and build of PowerShell the target node is running
Version of the module that was used