github pester/Pester 5.3.0-alpha2

latest releases: 6.0.0-alpha5, 6.0.0-alpha4, 6.0.0-alpha3...
pre-release3 years ago
  • Improves the tracer based code coverage, please try it and let me know where it is different from the current CC. This is how you do it:

There is now $configuration.CodeCoverage.UseBreakpoints experimental flag that allows you to use Profiler based code coverage instead of breakpoints based code coverage.
Here is a fuller example of generating CC for your code base using both methods.

https://gist.github.com/nohwnd/3a29c8f4afc21329a146b5cba953d503

If you can please try it and compare the xmls. E.g. open both in vscode and use the Compare active file with... command from the command pallete. You should see only difference on the top in timestamps.

This should work from PS3 PS4 up. At least it does in our CI pipeline. (PS3 has some weird issues I can't figure out, like not being able to enumerate collections and so on, so use at your own risk.)

The tracer based CC also cannot process default values in parameters, so it reports them as missed.

5.3.0-alpha1...5.3.0-alpha2

Don't miss a new Pester release

NewReleases is sending notifications on new releases.