Skip to content

Regenerate configuration table, code coverage works in parallel runs - #445

Merged
nohwnd merged 1 commit into
mainfrom
nohwnd-parallel-coverage-help
Aug 12, 2026
Merged

Regenerate configuration table, code coverage works in parallel runs#445
nohwnd merged 1 commit into
mainfrom
nohwnd-parallel-coverage-help

Conversation

@nohwnd

@nohwnd nohwnd commented Aug 12, 2026

Copy link
Copy Markdown
Member

The Run.Parallel row in the configuration table said the run falls back to sequential "when CodeCoverage is enabled", which the parallel page on the same site already contradicts ("Turning on Run.Parallel does not cost you your coverage report").

The text comes from the module, so the fix is in pester/Pester#2974. This regenerates the table from a build with that fix:

./generate-pesterconfiguration-docs.ps1 -Style Table

One row changed, so the rest of the page is in sync with 6.1.0. The page is ahead of the shipped module help until the next Pester release, but it describes behavior that is already released.

🤖

Run.Parallel still listed CodeCoverage as a reason the run falls back to
sequential, which the parallel page already contradicts. Regenerated with
generate-pesterconfiguration-docs.ps1 -Style Table against the fixed help.

🤖
@nohwnd
nohwnd merged commit ab22c79 into main Aug 12, 2026
4 checks passed
@nohwnd
nohwnd deleted the nohwnd-parallel-coverage-help branch August 12, 2026 07:56
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