coverage via coveralls in CircleCI #515
Closed
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.
Types of changes
(None of the above - changes are made to CI pipeline)
Motivation and Context / Related issue
The objective was to have code coverage made publicly accessible via https://coveralls.io
To achieve this, the following changes were made:
pytest
&unittest
to run viacoverage
coverage
indev_requirements.txt
, followed bycoveralls
in CircleCI configcoveralls
parallel
tocoveralls
as CircleCI taskscoveralls
to combine allparallel
uploads under single runHow Has This Been Tested (if it applies)
Testing changes made to CircleCI config is tricky. Most of the code was tested via opening this PR and letting CircleCI run on this new config. Some obscure parts were tested in a personal CircleCI environment.
Checklist