vscode-adapter
vscode-adapter copied to clipboard
pester
Run PowerShell Pester Tests with Visual Studio Code
Bumps the dependencies group with 3 updates: [actions/cache](https://github.com/actions/cache), [pnpm/action-setup](https://github.com/pnpm/action-setup) and [release-drafter/release-drafter](https://github.com/release-drafter/release-drafter). Updates `actions/cache` from 3 to 4 Release notes Sourced from actions/cache's releases. v4.0.0 What's Changed Update action to node20...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps the dependencies group with 14 updates: | Package | From | To | | --- | --- | --- | | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `20.10.6` | `20.12.7` | | [@types/vscode](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/vscode)...
Hiya, Nice extension, thank you! Is there a way we can see the code coverage as we can other extensions like the Jest extension?
There is a mismatch between how placeholders are expanded in the "Pester Tests" (vscode-adapter) extension, and how they are expanded in Pester. I would expect them to be expanded the...
If any of these activities occur, it can invalidate the tests without the filesystemwatcher being aware.
When I create Sample.Tests.ps1 and place it in a directory, I get an error. The following error occurs. An error occured running Pester: Cannot find path 'C:\Work\縺ｻ縺偵⊇縺箪Sample\Tests\' because it does...
I have pester tests that need parameters passed at runtime in order to execute the tests. An example would be: ``` param($deviceName, $artifactDirectory, $CustomTarget) BeforeAll { ...setup tests } Describe...
Nest contexts don't appear to display results correctly in the test explorer pane. ``` powershell BeforeDiscovery { $testCases = @( @{ Name = "fizz" }, @{ Name = "buzz" },...
https://github.com/pester/vscode-adapter/blob/0e89baf59024f5c27952acedb886324a1778930e/src/log.ts#L34-L35 Ref: https://code.visualstudio.com/updates/v1_66#_output-channel-with-custom-language-id
Right now the way the run works is a bit of a hodgepodge, I would like to very definitively define the following run scenarios (with the bolded already implemented) 1....