Bump Pester to 6.1 - #475
Merged
Merged
Conversation
HeyItsGilbert
force-pushed
the
chore/bump-pester-6.1
branch
from
September 13, 2026 00:19
4fab645 to
ee3c2be
Compare
There was a problem hiding this comment.
🔵 Needs a closer look
Conditional JSON templates with an explicit empty default still resolve to $null; distinguish missing defaults from empty defaults and add regression coverage.
Pull request overview
Updates the project to Pester 6.1.0 and adds support for explicit empty text defaults in manifest processing.
Changes:
- Pins Pester to 6.1.0.
- Updates Pester test and mock behavior.
- Adds empty-default handling and regression coverage.
File summaries
| File | Description |
|---|---|
tests/Help.tests.ps1 |
Updates empty -ForEach test handling. |
tests/Get-PlasterManifestPathForCulture.Tests.ps1 |
Updates Pester mock setup. |
tests/EmptyDefaultTextParameter.Tests.ps1 |
Adds empty-default regression coverage. |
requirements.psd1 |
Pins Pester to 6.1.0. |
Plaster/Private/Resolve-ProcessParameter.ps1 |
Supports explicit empty defaults. |
Plaster/Private/Read-PromptForInput.ps1 |
Supports empty input handling. |
Plaster/Private/ConvertFrom-JsonManifest.ps1 |
Preserves explicit empty JSON defaults. |
Review details
- Files reviewed: 3/3 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Test Results 4 files 288 suites 1m 10s ⏱️ Results for commit 0b3bd1a. ♻️ This comment has been updated with latest results. |
Merged
HeyItsGilbert
added a commit
that referenced
this pull request
Sep 13, 2026
## [2.1.4] - 2026-09-13 ### Fixed - Explicit empty text defaults in JSON manifests now remain empty rather than being treated as absent, while blank prompt input is accepted only when a default is declared ([#474](#474), closes [#473](#473)) - Pester 6.1.0 compatibility for mocks and empty `-ForEach` data sets ([#475](#475))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
-ForEachbehaviorVerification
./build.ps1 -Task Test(249 passed, 0 failed, 2 skipped)