Fix failing psakeFile Pester task - LocalizationParser default culture and psake configuration #11
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.
The CI pipeline was failing with Pester test errors due to two main issues in the PowerShell localization testing infrastructure.
Issues Fixed
1. LocalizationParser Missing Default Culture
The
LocalizationParser.ps1script was failing when noUICultureparameter was provided. The script usesImport-LocalizedDatawhich requires a specific culture to locate files in culture-specific subdirectories (e.g.,en-US/Example.psd1,fr-FR/Example.psd1). When running in environments with invariant culture, the localization files couldn't be found.Before:
After:
2. Outdated Pester Configuration Syntax
The
psake.ps1build script was using deprecated Pester configuration syntax that's incompatible with Pester 5.x. The script was attempting to create a[PesterConfiguration]object directly and use-PassThruas a parameter.Before:
After:
Validation Results
All tests now pass successfully:
The CI pipeline Pester task will now execute successfully without the previous
Import-LocalizedDataerrors.Fixes #10.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.