Add tox environment factors to tox and travis ci #11
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.
Summary
Refactors coveralls coverage as tox environment factors and implements them in Travis CI.
Description
Previously, #10 fixed the integration between Travis CI and Coveralls; however, updating Coveralls coverage still ran repetitive tests. This costs about 35 seconds of build time per build.
Further digging in tox's config settings revealed conditional settings.
The idea is to make coverage a conditional setting of the
py37
tox environment, which Coveralls will updateafter_success
. This way, Coveralls coverage will get updated only after running thepy37-coverage
environment instead of after every environment.By doing this, Coveralls should be updated during
py37
unit tests instead of running a second set of unit tests to update Coveralls. In theory, this should save around 35 seconds of build time.While I was at it, I added coverage reports to the coverage testenv. This environment is intended to run locally as a testing tool rather than in a CI build.
Team Notifications
Me, myself, and I