What's Changed
If you have ideas for breaking (and other changes) that should happen in Pester 6 and that are not in Pester 6 milestone, please let us know in discussion, in the issue you want to link, or in a new issue 🙏
Assert assertions are becoming part of Pester
Assert assertions were migrated to Pester, and we will continue improving them here. They are published as Should-Be and similar aliases (no space) from the Pester module, as well as Assert-Equal functions. (Because of the naming limitations we cannot use Should-* directly.
The assertions are split into 4 categories, generic, type specific, collection, and equivalency. See this doc for the initial documentation. There will be more I promise.
Pester supports only 5.1 and 7
We've dropped support for PowerShell 3, 4, 6 and early 7. All of those versions are officially out of support by Microsoft. This will help us modernize the code base and further improve performance.
More changes:
- Set profiler based CodeCoverage as default by @nohwnd in #2456
- Remove Pending status by @nohwnd in #2457
- Ignore PassThru when run fail while using Run.Exit by @fflaten in #2303
- Shorten TestDrive directory name by @splatteredbits in #2239
- Add null check for $host.UI and its properties to avoid race condition (#2383) by @kborowinski in #2468
- Hide legacy-only parameters in Invoke-Pester by @fflaten in #2446
- Remove Should legacy syntax error by @fflaten in #2445
- Fix NRE in mock debug log for native commands by @fflaten in #2480
Internal and Infrastructure changes:
- Remove blank output in PesterThrow.Tests.ps1 by @fflaten in #2460
- Hide failing output that always scares me by @nohwnd in #2461
- Replace New-Object calls with ::new() by @fflaten in #2469
- Replace deprecated macOS 11 image with 13 in CI by @fflaten in #2482
- Report code coverage that includes P tests by @nohwnd in #2478
New Contributors
- @kborowinski made their first contribution in #2468
Full Changelog: 5.6.0-rc1...6.0.0-alpha1