Uh oh!
There was an error while loading. Please reload this page.
Pester v5 - #366
Conversation
|
Azure Pipelines successfully started running 1 pipeline(s). |
Howard Wolosky (HowardWolosky)
commented
Dec 15, 2022
Mark (@tigerfansga) - You'll need to sign the CLA via the bot using the command Still looking through the test failures to see if there's anything there related to your changes... |
Mark (tigerfansga)
commented
Dec 15, 2022
That is strange on the CLA because I had accepted it. I can get that done later today. I'm not sure I'll be able to review any requested changes till after the New Year. |
Error message has changed. Modifying test to simply capture that a failure occurred (without validating the string itself)
Mark (tigerfansga)
commented
Dec 15, 2022
@microsoft-github-policy-service agree |
Removes the specific error message check from the `Throw` validation of some tests since the wording of the exception message keeps changing.
Howard Wolosky (HowardWolosky)
commented
Dec 16, 2022
/azp run PowerShellForGitHub-CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Update the PowerShell extension in VS Code to take advantage of the fact that the tests are now Pester 5 compatible. This allows each individual block to have a Run/Debug link associated with it.
Disabling the tests since they no longer work.
Disabling since classic projects have been deprecated.
Disabling since classic projects are no longer supported.
Uh oh!
There was an error while loading. Please reload this page.
Howard Wolosky (HowardWolosky)
commented
Dec 16, 2022
/azp run PowerShellForGitHub-CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Howard Wolosky (HowardWolosky)
commented
Dec 16, 2022
/azp run PowerShellForGitHub-CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Howard Wolosky (HowardWolosky)
commented
Dec 16, 2022
I cleaned up the remaining work in here and got it merged in. Thanks so much to Mark (@tigerfansga) for taking this work on and moving the project forward. It's HUGE that we can now run individual tests directly within VS Code now that we're on Pester 5. |
Description
Update pester test for Pester v5 support
Issues Fixed
References
Checklist
Comment-based help added/updated, including examples.Formatters were created for any new types being added.New/changed code continues to support the pipeline.Changes to the manifest file follow the manifest guidance.Relevant usage examples have been added/updated in USAGE.md.