Skip to content

Document mock invocation history in 6.0.0 release notes#2813

Merged
nohwnd merged 1 commit into
mainfrom
nohwnd-rc2-release-notes
Jun 29, 2026
Merged

Document mock invocation history in 6.0.0 release notes#2813
nohwnd merged 1 commit into
mainfrom
nohwnd-rc2-release-notes

Conversation

@nohwnd

@nohwnd nohwnd commented Jun 29, 2026

Copy link
Copy Markdown
Member

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 -Invoke assertion fails, using the latest example from the Pester docs.

Changes to docs/6.0.0.md

  • New "Mock invocation history" subsection under Mocking changes. It shows the recorded call history printed on a failed Should -Invoke, including how [*] (matched the parameter filter) and [ ] (didn't) are marked, with the Order.Tests.ps1 example from the docs. The one-line "Mock history" bullet is reworded to point at it.
  • Intro framing finalized — dropped the "first release candidate" wording for final 6.0.0 phrasing (matching the maintained 6.0.0 release notes draft).

Line endings keep the repo's CRLF convention (.gitattributes eol=crlf).

- 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 nohwnd merged commit 88946a1 into main Jun 29, 2026
3 checks passed
@nohwnd nohwnd deleted the nohwnd-rc2-release-notes branch June 29, 2026 22:06
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant