Skip to content

Pester CodeLens Isn't Triggered When Describe is Module-Qualified #928

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mattmcnabb opened this issue Jun 28, 2017 · 1 comment · Fixed by PowerShell/PowerShellEditorServices#1998
Labels
Area-Pester Issue-Bug A bug to squash.

Comments

@mattmcnabb
Copy link
Contributor

When I use the module-qualified command name Pester\Describe, the Code Lens for running tests is not triggered:

image

System Details

PS Repos:\> code -v
1.13.1
379d2efb5539b09112c793d3d9a413017d736f89
PS Repos:\> $pseditor.EditorServicesVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
1      4      1      0


PS Repos:\> code --list-extensions --show-versions
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
PS Repos:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.15063.413
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.15063.413
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
@daviwil
Copy link
Contributor

daviwil commented Jun 28, 2017

Didn't expect that one, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Pester Issue-Bug A bug to squash.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants