Add tests for #1504 PSUseUsingScopeModifierInNewRunspaces#2005
Add tests for #1504 PSUseUsingScopeModifierInNewRunspaces#2005o-l-a-v wants to merge 6 commits intoPowerShell:mainfrom
Conversation
bergmeister
left a comment
There was a problem hiding this comment.
updated branch to run new CI, looks good otherwise, always happy to have more tests :-)
| } | ||
| } | ||
| '@ | ||
| ScriptBlock = '{ |
There was a problem hiding this comment.
thanks for making it more readable :-)
|
Are these essentially testing that the extant bug exists, and should fail when we fix the bug (meaning we'll flip their assertion)? |
|
Sorry for the late reply. I wrote the rules with the goal of them failing with current behavior. |
Gotcha, makes sense now. Do you plan to fix the issue as part of this PR? Changing it to draft for now then |
No. I just had two very concrete examples that I wanted to add somewhere for when this maybe gets fixed in the future. |
|
Got it, will leave open as a draft PR then. Thanks! |
PR Summary
Wrote two tests for issue #1504. The issue is not fixed yet, but I had two scenarios that could easily be added to the relevant test file.
Repro to wrongfully trigger
PSUseUsingScopeModifierInNewRunspaces, which I added to test:PR Checklist
.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.