pester-should-migration
Experimental (preview) Pester skill for migrating classic Should -Be (v5) assertion syntax to the new Should-* (v6) assertions (note the hyphen, no space), e.g. `Should -Be` -> `Should-Be`, `Should -Not -Be` -> `Should-NotBe`. Tracks Pester 6, which is still a release candidate, so this guidance may change; verified against Pester 6.0.0-rc2. Use when converting Pester v5 assertions to Pester v6 Should-* operators, modernizing a Pester test suite, or when a user asks to migrate, convert, or rewrite `Should -...` calls in .Tests.ps1 / PowerShell files.
- License 许可
- MIT
- 最近更新
- 2026-08-19
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- description
- Experimental (preview) Pester skill for migrating classic Should -Be (v5) assertion syntax to the new Should-* (v6) assertions (note the hyphen, no space), e.g. `Should -Be` -> `Should-Be`, `Should -Not -Be` -> `Should-NotBe`. Tracks Pester 6, which is still a release candidate, so this guidance may change; verified against Pester 6.0.0-rc2. Use when converting Pester v5 assertions to Pester v6 Should-* operators, modernizing a Pester test suite, or when a user asks to migrate, convert, or rewrite `Should -...` calls in .Tests.ps1 / PowerShell files.
02 资源文件 1
- 参考文档references/assertion-map.md9.3 KB
03 SKILL.md 正文
Pester Should -* → Should-* Migration
Convert classic Pester v5 assertions (Should -Be, space then parameter) to the
new Pester v6 Should-* assertions (Should-Be, hyphen, no space).
Status: experimental / preview. Verified against Pester 6.0.0-rc2. The classic
Should -Bestyle still works in v6, so migrate incrementally and keep the suite green.
Companion skill. This skill covers the optional move to the new
Should-*operators. To upgrade a suite across major Pester versions (v3→v4→v5→v6 — the runtime, mocks, and config), use the separate pester-migration skill. In v6 the classicShould -Bekeeps working, so adoptingShould-*is independent of any version bump.
When to Use
- Modernizing a Pester suite to the v6
Should-*assertions. - A user asks to migrate / convert / rewrite
Should -...calls. - You want clearer, type-aware failure messages from the new assertions.
Know This First
- Both syntaxes work side by side in Pester v6. Migration is optional and can be done one test (or one file) at a time. Nothing breaks if you leave some classic.
- Requires Pester v6+. The
Should-*commands do not exist in v5. - Negation is a separate command, not a
-Notswitch:Should -Not -Be→Should-NotBe. There is no-Notparameter on the new assertions. - The actual value still comes from the pipeline (
$x | Should-Be 1) or from-Actual(Should-Be -Actual $x -Expected 1).-Becausecarries over unchanged. - Most renames are mechanical, but several have behavior changes you must check by hand — see Gotchas.
Procedure
Step 1 — Find the classic assertions
Search the target for the classic space-separated syntax (the tell is Should -,
or Should followed by -Not):
Should - # any classic operator
Should -Not - # negated classic operator
Assert-MockCalled # also removed in v6 -> Should-Invoke
Limit the scope to PowerShell test files (*.Tests.ps1, *.ps1).
Step 2 — Apply the mapping
Most-used conversions (full list in references/assertion-map.md):
| Classic (v5) | New (v6) |
|---|---|
$x | Should -Be 1 |
$x | Should-Be 1 |
$x | Should -Not -Be 1 |
$x | Should-NotBe 1 |
$x | Should -BeExactly 'A' |
$x | Should-BeString 'A' -CaseSensitive |
$x | Should -BeGreaterOrEqual 2 |
$x | Should-BeGreaterThanOrEqual 2 |
$x | Should -BeLessOrEqual 2 |
$x | Should-BeLessThanOrEqual 2 |
$x | Should -BeLike 'a*' |
$x | Should-BeLikeString 'a*' |
$x | Should -Match 're' |
$x | Should-MatchString 're' |
$x | Should -BeOfType [int] |
$x | Should-HaveType ([int]) |
$x | Should -BeNullOrEmpty |
depends — see gotchas (no single equivalent) |
$c | Should -HaveCount 3 |
$c | Should-BeCollection -Count 3 |
$c | Should -Contain 2 |
$c | Should-ContainCollection 2 |
{ ... } | Should -Throw 'msg' |
{ ... } | Should-Throw -ExceptionMessage 'msg' |
Should -Invoke Get-Thing |
Should-Invoke Get-Thing |
Should -InvokeVerifiable |
Should-Invoke -Verifiable |
Step 3 — Check the behavioral gotchas (do NOT skip)
These do not translate by a plain rename. Read each before converting:
- Case sensitivity. Classic
Should -Beis case-insensitive on strings; so isShould-Be. But classicShould -BeExactly(case-sensitive) has no plain equivalent — useShould-BeString -CaseSensitive. (Should-Beis never case-sensitive.) Same pattern forBeLikeExactly→Should-BeLikeString -CaseSensitiveandMatchExactly→Should-MatchString -CaseSensitive. - Truthy vs. true. Classic
Should -BeTrue/-BeFalseaccept any truthy / falsy value (1,'x',0,'',$null,@()). The newShould-BeTrue/Should-BeFalseare strict (exactly$true/$false). To preserve the old loose behavior useShould-BeTruthy/Should-BeFalsy. Only use the strict ones when the value really is a boolean. BeNullOrEmptyhas no single equivalent. Pick by intent:$null→Should-BeNull; empty string →Should-BeEmptyString; empty collection →Should-BeCollection -Count 0; broad "falsy" →Should-BeFalsy. The negationShould -Not -BeNullOrEmptysimilarly splits intoShould-NotBeNull/Should-NotBeEmptyString/Should-NotBeWhiteSpaceString.- Collections. Classic
Should -Bealso compares arrays; the newShould-Beis a value assertion and errors if-Expectedis a collection ("You provided a collection to the -Expected parameter"). UseShould-BeCollectionto compare arrays.Should -Contain(single-item membership) →Should-ContainCollection. The new command also takes a collection of expected items and checks they are all present, in the right order (1, 2, 3 | Should-ContainCollection @(1, 2)). For exact, whole-collection equality useShould-BeCollectioninstead. - Pipeline unwrapping. The pipeline unwraps input: a value assertion sees
@(1)as1and@()as$null, and a typed collection ([int[]]) is re-collected as[object[]]. When the exact value or concrete collection type matters (e.g.Should-HaveType), pass it with-Actualinstead of piping. - No
Should-*equivalent.Should -Existand theShould -FileContentMatch*family have no new counterpart. Either keep the classic assertion, or rewrite with PowerShell:Test-Path $p | Should-BeTrue,(Get-Content $p -Raw) | Should-MatchString 're'. Should -BeIndirection. NoShould-BeIn. Reverse the operands:$value | Should -BeIn $collection→$collection | Should-ContainCollection $value(note the actual/expected swap), or keep the classic form.
Step 4 — Verify
Run the suite and confirm it's still green — the new messages differ, but passes must stay passes:
Invoke-Pester -Path ./tests
If a converted assertion newly fails, re-check the gotchas above (most often #2 truthy/falsy, #3 null-or-empty, or #4 collections).
Step 5 — (Optional) Enforce the new style
Once a suite is fully migrated, switch off the classic syntax so it can't creep back:
$config = New-PesterConfiguration
$config.Should.DisableV5 = $true
With this set, any remaining Should -Be throws and points at the Should-Be form.
Output
Summarize what changed: files touched, count of assertions converted, any classic
assertions intentionally left (e.g. Should -Exist), and any conversions that need
a human decision (truthy/falsy, null-or-empty, collection semantics).
Reference
- references/assertion-map.md — full operator-by-operator table with before/after examples and workarounds.
- Live command reference:
https://pester.dev/docs/commands/Should-Be(swap in anyShould-*name) for exact parameters and examples. - Concepts:
https://pester.dev/docs/assertions/should-command(value vs. collection assertions, pipeline vs.-Actual). - v5→v6 upgrade guide:
https://pester.dev/docs/migrations/v5-to-v6.
04 同仓库更多 Skills
youtube-transcript
Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com/watch?v=, youtu.be/, or similar). Supports output with or without timestamps.
youtube-thumbnail-design
YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A/B testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image
youtube-short-maker
Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: "youtube short", "make a youtube short", "shorts video", "short-form video". NOT for long-form or landscape video.
xcode-project-setup
Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or "build it in" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.
x-twitter-scraper
Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.