Skip to content

Add support for CoverageReport output preferences #1995

Open
@bryanbcook

Description

@bryanbcook

Hey Pester Team,

I think it would be useful if you could control the verbosity of the coverage report independently from the Output preference.

Motivation: we have a set of Pester tests that are running as part of our CI, using Azure DevOps. We're using the PesterConfiguration to set the Output to Detailed, which adds an extra level of helpful logging. A side-effect of this setting is that the CodeCoverage report is displayed in full in the build output. Some of our uncovered lines include Azure DevOps "##vso" logging statements, which are incorrectly parsed by the build agent as malformed statements.

Presently, the coverage report is controlled by the output preference. Perhaps a new preference setting could be added to the CodeCoverageConfiguration?

$config.Output.Verbosity = "Detailed"
$config.CodeCoverage.OutputVerbosity = "Normal"

or

$config.Output.Verbosity = "Detailed"
$config.Output.CoverageVerbosity = "Normal"

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions