Document mock invocation history in 6.0.0 release notes#2813
Merged
Conversation
- Add a "Mock invocation history" subsection with the example from the Pester docs, showing the call history printed when a Should -Invoke assertion fails and how matched/unmatched calls are marked. - Drop the "first release candidate" framing from the intro for final 6.0.0 wording. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
nohwnd
added a commit
that referenced
this pull request
Jun 29, 2026
The intro reword this commit originally carried was superseded by #2813 on main, which already dropped the release-candidate framing. Keep only the thank-you pluralization, since there were multiple release candidates. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
nohwnd
added a commit
that referenced
this pull request
Jun 30, 2026
…#2815) * Update 6.0.0 release notes for parallel data and wall-clock durations The committed 6.0.0 notes still described the rc1 parallel runner. Fold in the two user-facing parallel changes made since then: - Parametrized file containers (New-PesterContainer -Path ... -Data @{...}) now run in parallel, with their -Data handed to each worker, so only in-memory ScriptBlock containers fall back to the sequential path. - A parallel run reports its total Duration as wall-clock elapsed time and leaves the per-phase run totals (user, framework, discovery) blank, since the files overlap; the per-phase breakdown stays on each container. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Pluralize release candidates in 6.0.0 notes thank-you The intro reword this commit originally carried was superseded by #2813 on main, which already dropped the release-candidate framing. Keep only the thank-you pluralization, since there were multiple release candidates. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
1 participant
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
Follow-up to #2810 (which imported the 6.0.0 release notes). This adds documentation of the mock invocation history that Pester v6 prints when a
Should -Invokeassertion fails, using the latest example from the Pester docs.Changes to
docs/6.0.0.mdShould -Invoke, including how[*](matched the parameter filter) and[ ](didn't) are marked, with theOrder.Tests.ps1example from the docs. The one-line "Mock history" bullet is reworded to point at it.Line endings keep the repo's CRLF convention (
.gitattributeseol=crlf).