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
Improve tests #274
Merged
Merged
Improve tests #274
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
dopplershift
added
Area: Infrastructure
Pertains to project infrastructure (e.g. CI, linting)
Area: Tests
Affects tests
Type: Enhancement
Enhancement to existing functionality
Type: Maintenance
Updates and clean ups (but not wrong)
labels
Dec 2, 2016
Need to check when pytest started allowing |
dopplershift
force-pushed
the
improve-tests
branch
3 times, most recently
from
December 7, 2016 01:19
864ed98
to
7a8bd3b
Compare
dopplershift
force-pushed
the
improve-tests
branch
5 times, most recently
from
December 7, 2016 16:57
e48f13e
to
bd2c547
Compare
This way we can check that their aggregate coverage through codecov is 100% and ensure that all tests are being executed.
This was causing differences in tests between Python 2 and 3.
Because builtin round behavior changed between Python 2 and 3, and matplotlib < 2.0 was using it in places, we need to monkey patch it to get consistent testing across Python versions.
This was throwing off PyCharm.
Update images to matplotlib 2.0. Also add verion-dependent thresholds. All of this (with the previous fixes) allows us to have much tighter tolerances.
It's really hard to run Python 3.3 with a matplotlib where we can have tight image test tolerances. Instead, run it alongside our 2.7 legacy build tests.
dopplershift
force-pushed
the
improve-tests
branch
from
December 9, 2016 21:30
571f367
to
a127242
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: Infrastructure
Pertains to project infrastructure (e.g. CI, linting)
Area: Tests
Affects tests
Type: Enhancement
Enhancement to existing functionality
Type: Maintenance
Updates and clean ups (but not wrong)
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.
Trying to make the text-based (station plot) tests much more robust than we have now.
Also testing out having our coverage checking include our actual tests files so that we ensure everything is being run.
A few more little things.