Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Missing Coverage with TravisCI, Jest #341
I'm having trouble getting code coverage to be displayed through Code Climate. I have used the
I'm using Jest, which outputs lcov to
Here is my
Here is some relevant info from
Hey @stevenAtGeneralUI , sorry for the delay in getting to this. Taking a look our backend, I can confirm that we're receiving valid test payloads for your repo. However, we haven't yet received a payload from your default branch. Currently, we only display coverage info for the default branch in the UI. Coverage info for non-default branches is visible in Github by using our browser extension. Once you upload a coverage payload from your default branch, let me know if you're still failing to see that info as expected. Thanks.
referenced this issue
Sep 1, 2018
I believe I'm experiencing this issue as well.
I'm basing this off of the Travis CI set-up described here:
Doesn't seem to work at all; I just see the umbrella for configuring code coverage forever.
FYI the information on configuring code coverage is pretty buried. I was rather annoyed to click on the configure code coverage button and see my token and basically zero info on how to do it. For that, I had to go to the docs, and from there, I had to very carefully read to find a small link to examples and to find the Travis CI example. Which doesn't work. Bummer.
@davehenton My opinion regarding the documentation is that if you click on set-up code coverage, you should see your token and a list of guides on how to use it. Experienced users then don't have to scroll/look down to get the token (what they came for) and inexperienced users will get straight to the info they need. Also, offering any settings to tweak the set-up when CC already knows it's not configured yet doesn't really make sense. But I digress. ;)
This seems to have "fixed itself."
I'm not sure of this but what seems to have been the case was: My code was failing because I had less than 80% coverage; when I tapered down what was being included to just the core src files and the code style passed, it showed up in CC. Either way the json was being sent (as told by the debug flag). It would seem to me that the coverage icon needs 3 states: not-set-up, failing, and passing-with-x-percent-coverage.