-
Notifications
You must be signed in to change notification settings - Fork 391
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
Add tests for #1504 PSUseUsingScopeModifierInNewRunspaces #2005
base: main
Are you sure you want to change the base?
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.
updated branch to run new CI, looks good otherwise, always happy to have more tests :-)
} | ||
} | ||
'@ | ||
ScriptBlock = '{ |
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.
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
,.ps1
and.psm1
files have the correct copyright headerWIP:
to the beginning of the title and remove the prefix when the PR is ready.