Releases: pester/Pester
5.3.0-rc1
5.3.0-beta1
5.3.0-beta1
Issues Fixed
- Add Ability to Override Properties on New-MockObject #1838
- Added Run.SkipRemainingOnFailure option #2023
- Added FileContentMatchMultilineExactly should assertion #2030
- Added Filter.ExcludeLine option #2016
- Fix broken link to pester.dev assertions page #2024
- Enable additional plugins to be added via $additionalPlugins internally #2020
See full log here
5.3.0-alpha5
5.3.0-alpha5
Issues Fixed
- Add PSObject boxing support in PesterConfiguration #1978
- Azure Devops & Github Actions error logging #1996
- Add missing container-parameters to Data #1986
- Update InvokeVerifiable error message and add negate support #1976
- Adds support for Register-ArgumentCompleter #1979
- Fix throwing on missing folders #2012
- Add option to disable TestDrive and TestRegistry #2008
- Fix failure on zero analyzed commands #2001
- Fix tracer state on cancelled Pester run with new CodeCoverage #1998
- Log conflicting variables in Should -Invoke -ParameterFilter #1973
- make Value-property setter private in options #1994
- Improve operator-help returned from Get-ShouldOperator #1988
- Limit output information for failed tests #1975
- Add analyzerrule for object-commands #1753
- Update reporttheme output to remove hard coded colour names #1934
- Update output for Discovery and Filter #1969
- Add formatdata to ensure list view for all sections in PesterConfiguration #1964
- Removed StartMessage from output #1968
- Build on PS5.1 #1966
See full log here
5.3.0-alpha4
- Fixes coverage of default values in param block when the new CC is used.
See in the previous releases how to test it and compare the old CC with the new, and let me know please.
5.3.0-alpha3
Broken build, don't use.
5.3.0-alpha2
- 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.
4.10.2-beta1
- Added parameter for Alias in HaveParameter (#1463)
- Fixes #1028 - Code Coverage for proxy functions/steppablePipelines (#1494)
- Many gherkin runner fixes and improvements (#1276)
Full log 4.10.1...master
5.2.2
5.3.0-alpha1
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 up. At least it does in our CI pipeline.