-
Notifications
You must be signed in to change notification settings - Fork 512
Setting to Disable Pester Code Lens #3613
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
Setting to Disable Pester Code Lens #3613
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If possible, we should add a high-level test here that asserts the CodeLens are (and are not) correctly enabled on Pester test files.
Co-authored-by: Andy Schwartzmeyer <[email protected]>
Co-authored-by: Andy Schwartzmeyer <[email protected]>
Sorry about the 5.1 failure, it's still flaky but I also think the "can start Pester tests from file (which also tests debugger)" test is really freaking important. |
I got the Pester setting issue sorted, no idea why a direct assignment didn't work but implementing an Update method did. |
@andschwa works as expected now |
PowerShell/PowerShellEditorServices#1585 has now been merged, this is required to complete the feature. |
Allows the Pester Codelens to be disabled so as not to confuse users who want to use an alternate Pester Test Runner
Correlated PSES PR: PowerShell/PowerShellEditorServices#1585
Resolves #3430
PR Summary
PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an
x
between the square brackets.Please mark anything not applicable to this PR
NA
.WIP:
to the beginning of the title and remove the prefix when the PR is ready