pester-should-migration
Preview skill migrating Pester Should -Be v5 assertions to v6 Should-* syntax.
About
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.
At a glance
- Category
- Developer tools Testing and QA
- Made for
- Developers
- Pricing
- Free
- Access
- No sign-in
Category, summary and these details are StealthStack's reading of the publisher's own listing. Check the publisher's page before you rely on them.
Capabilities
The crawler did not record capability metadata for this resource. Inspect the endpoint directly to see what it exposes.
Provenance
- Discovered
- Relayed by github
- Identifier
- urn:air:github.com:github:awesome-copilot:pester-should-migration
- Catalog host
- github.com · via github registry
- Anchor check
- Not anchored
- Last crawled
- seen 9d ago
Discovered through github.com's registry, not anchored by StealthStack. We relay the listing as-is; we have not checked that the URN authority matches the publishing host. How trust works →