Pester 5 no longer has function-based CodeCoverage? (Smallest granularity is modules?)

[NickBrinsmade]

General summary of the issue

In Pester 4, you used to be able to call Invoke-Pester -CodeCoverage @{ Path='path\to\my\test\file'; Function='My-FunctionName' } but this syntax no longer works and it seems like you need to use the -Configuration parameter to pass in a PesterConfiguration object made with New-PesterConfiguration.

Is there any way to achieve the function-based CodeCoverage granularity? There is no 'function' parameter that can be passed in anymore and there isn't a property in the configuration object that has this.

Describe your environment

Steps to reproduce

Expected Behavior

Current Behavior

Possible Solution? (optional)

[nohwnd]

What is what you are trying to do? Get code coverage reported just for a single function?

You are right that in Pester 5 the code coverage works only for whole files. But you should be able to filter it down. I did not implement it in 5 because I was much busier coming up with a way to do CC faster (which is now in place), and I never saw anyone mentioning code coverage with Pester that would actually use the filtering to report on just parts of file.