5.2.0-beta1

[nohwnd]

🔥 This is outdated go to 5.2.0-rc1 instead

5.2.0-beta1

Issues Fixed

• Add $PesterBoundParameters to -MockWith and -ParameterFilter scriptblocks #1916
• Fix mock behavior for Mock and Should -Invoke #1915
• Resolve class metadata in the correct scope #1913
• Add Pester assembly version check during module import #1790
• Fix output of fullname filter in log #1893
• Add New-PesterConfiguration cmdlet to create [PesterConfiguration] #1728
• Disable CodeCoverage in CI switch #1911
• Add option to throw on failure #1908
• Rename Script.ps1 to Pester.ps1 #1907
• Ensure plugins are null #1900
• Isolate test files and scriptblocks to run in their it's own script scope #1889
• Report failures in discovery into result object #1898
• Fix setting passed on parent block when some blocks are not run #1897
• Fix testdrive example #1894

See full log here

---

This discussion was created from the release 5.2.0-beta1.

[nohwnd]

There are two notable changes:

• Mocks are behaving way more consistently when multiple mocks for the same command are used in different modules. I believe that the behavior is way more predictable now. If you see unexpected behavior please report it. The mock cleanup on cancelled runs is also better, because it looks into all loaded modules as well as into user scope, so you should not get orphaned mocks anymore.

  There is a good discussion in Fix mock behavior for Mock and Should -Invoke #1915 as well as an example of the behavior in this gist.

• -CI parameter no longer enables CodeCoverage
  I looked into CC performance and even thought there are some improvements to the setup time, we will never be able to have it fast on versions that don't have the powershell profiler. I can make it work on PS5 as well with some ugly hacks, but the default CC that is using breakpoints and not the profiler will always be rather slow. For that reason I disable the CC in the CI switch. Advanced user can easily enable it again using the configuration object, which you can now also create using New-PesterConfiguration which is recommended over [PesterConfiguration]::Default because it will load Pester module.

[nohwnd]

Go to 5.2.0-rc1 instead