Fix test runner double printing in non-verbose mode #1158
Merged
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## dev #1158 +/- ##
=========================================
- Coverage 68.09% 68% -0.09%
=========================================
Files 37 37
Lines 2282 2285 +3
Branches 398 399 +1
=========================================
Hits 1554 1554
- Misses 659 662 +3
Partials 69 69
Continue to review full report at Codecov.
|
ajtritt
approved these changes
Jan 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When running
python test.pynot in verbose mode, theColoredTestRunnerdouble printed test result outputs, i.e., the '.', 'F', 'E', and 's'. 172 unit tests generated 344 '.'s. This PR fixes that.