Repository navigation
Tests: Test-PSBuildPester #102
Description
Activity
Decision (2026-07-07): The sub-issue bodies under #17 previously said "use Pester 5 syntax." They have been updated to target Pester 6.0.0, which was released as stable today; Pester 5 simultaneously moved to maintenance mode (critical/security fixes only).
Rationale and guardrails:
- Scope: this affects only this repository's own test suite (the framework used to run
tests/). The shipped module's compatibility contract —Test-PSBuildPesterimporting Pester with-MinimumVersion 5.0.0and the manifest'sRequiredModulesfloor — is unchanged. Consumers on Pester 5 remain fully supported. - Pinning: Pester will be pinned to exactly
6.0.0inrequirements.psd1(not a floating minimum) and bumped deliberately as 6.0.x patches land, since the release is brand new. - Syntax: new tests use the classic
Should -Beassertion syntax, which is valid in both Pester 5 and 6, rather than the newShould-*assertion family. This keeps every new file trivially backportable to Pester 5.9 if 6.0.0 proves too raw. - Tests: Test-PSBuildPester #102 special case:
Test-PSBuildPestertests are Pester-testing-Pester, so the innerInvoke-Pesterruns in a subprocess and is matrixed across Pester 5.x and 6.x to continuously verify the Pester 5 consumer contract. Details in that issue's body.
No code has been started yet; this records the targeting decision before work begins on #97 (shared fixture module) and the rest of the batch.
Generated by Claude Code
- Scope: this affects only this repository's own test suite (the framework used to run
- added a commit that references this issue
on Jul 10, 2026
Add Pester 6 integration tests for
Test-PSBuildPester.Scenarios to cover:
BeforeAll/AfterAllblocks and container/discovery errors also fail the build, not just failedIttests (see Also fail on Pester block/container failures (not just failed tests) #128)Scope note: the block/container-failure scenario fails against current code —
Test-PSBuildPester.ps1gates only onFailedCount. The fix (includeFailedBlocksCountandFailedContainersCountin the gate, mirroring #128's change to the repo's ownpsakeFile.ps1) is in scope for the same PR as these tests, so the PR merges green. If #128 is extended to cover the shipped function first, this PR only contributes the regression test.Implementation note: these tests are Pester-testing-Pester, and two Pester versions cannot coexist in one session. Run the inner
Invoke-Pesterin a subprocess (Start-Job, astests/build.tests.ps1already does) so the inner Pester version is independent of the outer test framework. Then parameterize the inner run across both Pester 5.x and 6.x — the shipped function keeps supporting Pester 5 consumers, and this matrix is what verifies that contract.Target Pester 6.0.0 (outer framework) with classic
Shouldsyntax — see notes on #17. Parent issue: #17