CI Testing and Code Coverage
See original GitHub issueI see the Travis script uses pytest-cov, does this test runner report code coverage?
Do you, @akaszynski, by chance have the coverage reported to a service like codecov?
This would be a major help for me to figure out what still needs testing as I’ve added quite a bit of untested code in the last 24 hours
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
CI/CD Basics & Code Coverage
Code coverage analysis is measuring how well your unit tests exercise the production code. ▫Code coverage works like this: 1. Compile the project...
Read more >Adding test coverage to your CI pipeline | Coveralls and CircleCI
You push changes to your code at your SCM (ie. · Your CI service builds your project, runs your tests, and generates your...
Read more >Test coverage visualization - GitLab Docs
With the help of GitLab CI/CD, you can collect the test coverage information of your favorite testing or coverage-analysis tool, and visualize this ......
Read more >What is Code Coverage? | Atlassian
Code coverage is a metric that can help you understand how much of your source is tested. It's a very useful metric that...
Read more >Including Code Coverage in a Continuous Integration Process
The process for producing code coverage results (as binary .tcz results files) from applications running under a Continuous Integration (CI) system is the ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I’ve yet to take the time to get travis-ci talking with codecov. As much as I don’t want to, I have to test it locally as it can’t be 100% tested without X11. If I were you, I’d test for coverage locally with:
I’ll look into adding support for a coverage report. BTW, thanks for adding the tests!
I think I figured it out! See #31