[Christoph Bergmeister (bergmeister)]

Add an optional -TestPath parameter to build.ps1 -Test so contributors can run a single Pester test file without launching the full suite. The path is resolved as a literal file path; omitting it preserves the existing full-suite behavior. Validated with the targeted UseConsistentIndentation test file and the full test suite.

This help with local development so that one doesn't need to keep spawning test shells and more importantly help Copilot verify changes more easily.

[Copilot]

🟡 Changes recommended

Regression tests are needed for Test-ScriptAnalyzer’s new path-selection behavior, including single-file selection, apostrophe preservation, invalid-path rejection, and the default four-directory selection.

1 open issue

• Add regression tests for Test-ScriptAnalyzer path selection · New

What changed in this PR

Adds optional -TestPath support to build.ps1 -Test, allowing contributors to run a single Pester test file while preserving the default full-suite behavior.

Changes:

• Exposes TestPath in the test parameter set and forwards it to the build module.
• Resolves the supplied path literally, rejects directories, and escapes apostrophes when constructing the Pester invocation.

File	Description
build.psm1	Selects and validates the requested test file, retaining the existing suite directories by default.
build.ps1	Adds the optional TestPath parameter and passes it to Test-ScriptAnalyzer.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Test paths on custom PowerShell drives pass validation but fail in child processes because Resolve-Path.Path preserves drive names unavailable there; use .ProviderPath instead.

2 open issues

• Use ProviderPath for custom PowerShell drive paths · New
• Add regression tests for Test-ScriptAnalyzer path selection

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues are recorded for the optional -TestPath support.

1 open issue

• Add regression tests for Test-ScriptAnalyzer path selection

1 resolved since last review

• Use ProviderPath for custom PowerShell drive paths

_{Review effort: Balanced}

[Christoph Bergmeister (bergmeister)]

🟢 Approval recommended

No active review issues are recorded for the optional -TestPath support.

1 open issue

• Add regression tests for Test-ScriptAnalyzer path selection

1 resolved since last review
Review effort: Balanced

Copilot fix

[Copilot]

🟢 Approval recommended

No active review issues are recorded for the optional -TestPath support.

...

The requested regression coverage is already present in 6a4cc32 (single file, apostrophes, missing path, directory rejection, and the four default suite directories). I ran BuildModule.tests.ps1; all 20 tests pass.

[Copilot]

🟡 Changes recommended

The path escaping leaves typographic apostrophes unchanged, causing generated PowerShell script blocks to fail parsing for valid paths containing those characters.

1 open issue

• Escape typographic apostrophes in PowerShell paths · New

1 resolved since last review

• Add regression tests for Test-ScriptAnalyzer path selection

_{Review effort: Balanced}