test: Convert workflow test scripts to use PowerShell and Pester#122
Merged
test: Convert workflow test scripts to use PowerShell and Pester#122
Conversation
- Replace bash conditionals with Pester Should assertions - Change shell from bash to pwsh for all validation steps - Update environment variable syntax from $VAR to $env:VAR - Replace echo with Write-Host for PowerShell compatibility - Simplify test logic using Pester's built-in assertion methods 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
vaind
changed the title
vaind
force-pushed
the
feat/convert-tests-to-pwsh-pester
branch
from
053e37b to
e2a92f0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
bashtopwshfor all validation steps$VARto$env:VARechowithWrite-Hostfor PowerShell compatibilityTest plan
The tests now use cleaner Pester syntax like:
$env:BASE_BRANCH | Should -Be "main"instead of bash conditionals$env:LATEST_TAG | Should -Match "^[0-9]+\.[0-9]+\.[0-9]+$"for regex matching$env:PR_URL | Should -BeNullOrEmptyfor empty value checks🤖 Generated with Claude Code