Pester.bat no longer enables strict mode.#172
Merged
dlwyatt merged 1 commit intopester:Betafrom Aug 3, 2014
Merged
Conversation
This change was originally made to ensure that Pester's unit tests are run with strict mode enabled, so we would catch any bugs. However, making this change in Pester.bat affects all users of Pester (or at least the ones who use the convenience batch file for integration.) Pester's unit test scripts have since each been modified to enable Strict Mode at the beginning of each file, and we should no longer require this to be set in Pester.bat. This way, users of Pester are not forced to write their test scripts in a way that is StrictMode-compatible.
dlwyatt
added a commit
that referenced
this pull request
Aug 3, 2014
Pester.bat no longer enables strict mode.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change was originally made to ensure that Pester's unit tests are run with strict mode enabled, so we would catch any bugs. However, making this change in Pester.bat affects all users of Pester (or at least the ones who use the convenience batch file for integration.)
Pester's unit test scripts have since each been modified to enable Strict Mode at the beginning of each file, and we should no longer require this to be set in Pester.bat. This way, users of Pester are not forced to write their test scripts in a way that is StrictMode-compatible.