-
Notifications
You must be signed in to change notification settings - Fork 641
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
Add code coverage to CI #1651
Add code coverage to CI #1651
Conversation
I modified the coverage to collect statistics only for the files in the
Not sure why the materials library in |
This feature seems mostly useful if it is integrated with the PRs (so that CodeCov posts the coverage info to the PR) — if the result is just part of the CI output then I'm worried no one will look at it. |
Codecov Report
@@ Coverage Diff @@
## master #1651 +/- ##
=========================================
Coverage ? 73.52%
=========================================
Files ? 13
Lines ? 4488
Branches ? 0
=========================================
Hits ? 3300
Misses ? 1188
Partials ? 0 |
The coverage report from Codecov for the commit is now being displayed as a comment in the PR. We can make additional customizations as described here. The full report now includes the files in the base directory |
* Add code coverage to CI * remove ignore from codecov.yml * misssing brace * specify source files and show coverage report in output * remove badge * fix path of coverage.xml to match git file structure * show Codecov report in PR
* Add code coverage to CI * remove ignore from codecov.yml * misssing brace * specify source files and show coverage report in output * remove badge * fix path of coverage.xml to match git file structure * show Codecov report in PR
Adds code coverage using Coverage.py to the CI via CodeCov.
Setting this up requires activating CodeCov for theCoverage is only run for serial Python 3.6. This setup is similar to the previous coveralls feature added in #550.NanoComp
organization on GitHub (the link to the badge will also need to be updated).See this link for a sample of what the output looks like. The current coverage for the entire Python API is 65.66%. For a breakdown by file for just the adjoint-solver module, see here.