Context and request
The scheduled Process-PSModule run on main has failed every night since Pester 6 became the default in the shared framework. The repository is pinned to Process-PSModule v5.5.7 while v6.1.15 is current, and tests/Json.Tests.ps1 pins RequiredVersion = '5.8.0'. Until this is resolved no other change to the repository can be verified, because there is no green baseline to compare against.
This PBI covers restoring the pipeline and bringing the test suite onto the structure the standard defines. Both children touch tests/Json.Tests.ps1, so they are grouped here to keep their sequencing explicit.
Scope
In scope: the pinned workflow reference, the Pester requirement in the test suite, and the test suite's Describe/Context/It structure.
Out of scope: test coverage of new behaviour, which belongs with the issues that introduce that behaviour, and the CodeCoverage.PercentTarget: 95 setting in .github/PSModule.yml, which stays as-is.
Aggregate acceptance criteria
- The scheduled and pull-request
Process-PSModule runs succeed on Linux, macOS, and Windows.
tests/Json.Tests.ps1 declares the Pester 6 requirement the standard specifies and the suite runs unchanged under it.- The suite's structure matches the PowerShell Function Test Specification so a reader can locate the tests for any command by name.
- Code coverage still meets the 95% target configured in
.github/PSModule.yml.
Technical decisions
The workflow bump and the Pester requirement change ship together: v6 of the framework is what requires Pester 6, and splitting them leaves main red between the two merges. The structural rework of the suite is a separate deliverable because it is a large mechanical diff with no behavioural effect, and reviewing it alongside a pipeline change would hide regressions in both.
PR #23 and PR #26 both address the pipeline half. Reconcile them into the single delivery rather than merging both.
Implementation plan
Delivery is tracked through the native sub-issues on this PBI.
Context and request
The scheduled
Process-PSModulerun onmainhas failed every night since Pester 6 became the default in the shared framework. The repository is pinned toProcess-PSModulev5.5.7 while v6.1.15 is current, andtests/Json.Tests.ps1pinsRequiredVersion = '5.8.0'. Until this is resolved no other change to the repository can be verified, because there is no green baseline to compare against.This PBI covers restoring the pipeline and bringing the test suite onto the structure the standard defines. Both children touch
tests/Json.Tests.ps1, so they are grouped here to keep their sequencing explicit.Scope
In scope: the pinned workflow reference, the Pester requirement in the test suite, and the test suite's
Describe/Context/Itstructure.Out of scope: test coverage of new behaviour, which belongs with the issues that introduce that behaviour, and the
CodeCoverage.PercentTarget: 95setting in.github/PSModule.yml, which stays as-is.Aggregate acceptance criteria
Process-PSModuleruns succeed on Linux, macOS, and Windows.tests/Json.Tests.ps1declares the Pester 6 requirement the standard specifies and the suite runs unchanged under it..github/PSModule.yml.Technical decisions
The workflow bump and the Pester requirement change ship together: v6 of the framework is what requires Pester 6, and splitting them leaves
mainred between the two merges. The structural rework of the suite is a separate deliverable because it is a large mechanical diff with no behavioural effect, and reviewing it alongside a pipeline change would hide regressions in both.PR #23 and PR #26 both address the pipeline half. Reconcile them into the single delivery rather than merging both.
Implementation plan
Delivery is tracked through the native sub-issues on this PBI.