Run single test in Pester v5

[nohwnd]

This shows the lense on every Describe \ Context and It.

To test this you need Pester v5 ( branch filter-by-lines or once merged v5.0), you will also need the updated extension from vscode-powershell repo (branch same as here). Once your VSCode is started with the new version (after running the extension by F5), open a .Tests.ps1 file and load Pester v5.

Get-Module Pester | Remove-Module ; Import-Module Projects/Pester/Pester.psd1

WIP:
Once merged this will show the menu for all versions of Pester are we able to somehow figure out the version of Pester beforehand and only use the new approach when Pester v5 is loaded?

If not, should we add opt-in setting? Pester v5 is still far from ready, but I want to use this with beta which will be soon available 🙂

Ready:
Added opt-in setting for Pester5 that will enable the code lens for all items, otherwise it will use the standard Describe-only lense. This old lense works for both Pester v4 and v5, it just does not take full potential of v5. l used an option, instead of trying to detect which Pester version would be loaded because I don't want to guess, and I also want to force loading of Pester v5 when the code lense for it is specified. Using the existion VSCode configuration infrastructure this can be enabled per workspace.

[nohwnd]

This should be now good to go. When can I expect it in PowerShell and PowerShell Preview extension?

[TylerLeonhardt]

Since we're in a crunch time to ship PSReadLine in the PowerShell stable extension, this will not make that.

However, it will be in the next preview after that whi h will probably be a week or two after that goes out. So maybe by the end of the month.

[TylerLeonhardt]

This should be good now.

[TylerLeonhardt]

gah need to fix a test now :)

[nohwnd]

[TylerLeonhardt]

Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- src/PowerShellEditorServices/Services/CodeLens/PesterCodeLensProvider.cs  1
         

Clones added
============
- test/PowerShellEditorServices.Test.E2E/LanguageServerProtocolMessageTests.cs  14
         

See the complete overview on Codacy

[TylerLeonhardt]

I've changed the verb to use to be consistent with the useLegacyReadLine setting.