Skip to content
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

Making Pester StrictMode compliant again. #274

Merged
merged 1 commit into from
Feb 2, 2015

Conversation

dlwyatt
Copy link
Member

@dlwyatt dlwyatt commented Feb 2, 2015

We received a bug report that Pester was breaking if StrictMode were set for the whole PowerShell session. (We've been enabling it at the beginning of each test script, but apparently that's not enough to ensure compliance. We'll need to enable it before calling Invoke-Pester in our build jobs instead.)

All of these errors have been fixed.

We received a bug report that Pester was breaking if StrictMode were set for the whole PowerShell session.  (We've been enabling it at the beginning of each test script, but apparently that's not enough to ensure compliance.  We'll need to enable it before calling Invoke-Pester in our build jobs instead.)

All of these errors have been fixed.
dlwyatt added a commit that referenced this pull request Feb 2, 2015
Making Pester StrictMode compliant again.
@dlwyatt dlwyatt merged commit 4de2ee7 into pester:master Feb 2, 2015
@dlwyatt dlwyatt deleted the StrictModeFixes branch February 2, 2015 03:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant