Update Pester to 6.0.0

[nohwnd]

Pester 6.0.0 is now released 🎉 — thanks for letting me pilot the release candidates against your suite.

This updates the earlier release-candidate pin to the final 6.0.0 and keeps the test changes needed to run on Pester 6 (already in this PR). It's the same migration you'd make yourself, so you're welcome to merge it, cherry-pick just the compatibility changes, or use it purely as a reference.

Your unit + HQRM + integration tests all pass on 6.0.0 in this PR. 🟢

The real-world CI signal from this pilot was genuinely valuable in getting 6.0.0 right. Thanks for the CI time this used, and for maintaining a suite I could test against.

This PR was co-authored by GitHub Copilot.

— Jakub & Copilot

---

This change is 

[coderabbitai]

Walkthrough

This PR pins Pester to version 6.0.0 in RequiredModules.psd1 and updates unit and integration tests for compatibility: replacing removed Assert-MockCalled calls with Should -Invoke, moving $testCases initialization into BeforeDiscovery, and adding a fall-through Get-Command mock. A changelog entry documents the changes.

Changes

Pester 6 Compatibility Migration

Layer / File(s)	Summary
Pester dependency pin and changelog RequiredModules.psd1, CHANGELOG.md	Pins Pester to 6.0.0 and adds a changelog entry describing the test migration.
BeforeDiscovery migration tests/Unit/DSC_Computer.Tests.ps1	Moves $testCases setup from BeforeEach to BeforeDiscovery for discovery-time -ForEach population.
Assert-MockCalled to Should -Invoke migration tests/Unit/DSC_SystemProtection.Tests.ps1, tests/Unit/DSC_SystemRestorePoint.Tests.ps1	Replaces Assert-MockCalled assertions with Should -Invoke, preserving mocked command names, call counts, and parameter filters.
Get-Command fall-through mock tests/Integration/ComputerManagementDsc.Common.Tests.ps1	Adds a broad Get-Command mock forwarding unmatched calls to the real cmdlet to preserve fall-through behavior.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating the Pester dependency to version 6.0.0.
Description check	✅ Passed	The description is directly related to the Pester 6.0.0 update and the associated test compatibility changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87%. Comparing base (17e10f3) to head (d268b1e).

Additional details and impacted files

@@         Coverage Diff         @@
##           main   #467   +/-   ##
===================================
  Coverage    86%    87%           
===================================
  Files        21     21           
  Lines      2083   2122   +39     
===================================
+ Hits       1805   1853   +48     
+ Misses      278    269    -9     

see 7 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@tests/Unit/DSC_SystemProtection.Tests.ps1`:
- Line 138: Update all migrated call-count assertions in
DSC_SystemProtection.Tests.ps1 to use Should -Invoke -Exactly -Times <n> -Scope
It. The affected assertions in the current test block and the other listed
locations should be changed to assert per-It counts only, matching the existing
pattern used in DSC_Computer.Tests.ps1. Use the Should -Invoke calls in this
file to locate and update each assertion so mock counts are not aggregated
across a Context or Describe.

In `@tests/Unit/DSC_SystemRestorePoint.Tests.ps1`:
- Line 116: The migrated Should -Invoke assertions in
DSC_SystemRestorePoint.Tests.ps1 are missing the required call-count qualifiers.
Update the affected test assertions to use Should -Invoke with -Exactly and
-Scope It alongside -Times 1 so the mock verification is scoped to the current
It block and checks for an exact invocation count. Apply this to both migrated
Write-Warning assertions in the test file, matching the pattern already used in
DSC_SystemProtection.Tests.ps1.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bb5c9f84-e5ca-4d3c-9eea-5665772725ef

📥 Commits

Reviewing files that changed from the base of the PR and between 17e10f3 and d268b1e.

📒 Files selected for processing (6)

• CHANGELOG.md
• RequiredModules.psd1
• tests/Integration/ComputerManagementDsc.Common.Tests.ps1
• tests/Unit/DSC_Computer.Tests.ps1
• tests/Unit/DSC_SystemProtection.Tests.ps1
• tests/Unit/DSC_SystemRestorePoint.Tests.ps1

[johlju]

@johlju reviewed 6 files and all commit messages, and made 1 comment.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on nohwnd).