Coveralls branch percentage bug?
See original GitHub issueI’m not sure if this is a bug in badgen or Coveralls API, but shields.io seems to be returning the expected 100% while badgen seems to be using a percentage from a recent PR.
Badgen URL: https://flat.badgen.net/coveralls/c/github/expressjs/morgan/master
shields.io URL: https://img.shields.io/coveralls/expressjs/morgan/master.svg?style=flat-square
Rendered: Badgen: shields.io:
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Coverall branches [[0,0]] missed meaning? - Stack Overflow
Taken is either '-' if the basic block containing the branch was never executed or a number indicating how often that branch was...
Read more >bcoe/c8 | Coveralls - Test Coverage History & Statistics
Run Details. 79 of 95 branches covered (83.16%). Branch coverage included in aggregate %. 559 of 582 relevant lines covered (96.05%).
Read more >Coveralls Coverage Reports · Codefresh | Docs
Coveralls is a web service that allows users to track the code coverage of their application over time in order to optimize the...
Read more >python-coveralls - PyPI
Python interface to coveralls.io API. ... but using travis-ci or travis-pro will allow Coveralls to fetch branch data, comment on pull requests, and...
Read more >Start measuring code coverage with Jest, Travis CI and ...
If you wish to promote your build status or coverage percentage you can get some cool badges from Travis and Coveralls.io to put...
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 FreeTop 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
Top GitHub Comments
It looks like shields.io is not even using an API for coveralls is what’s happening – it just loads
https://coveralls.io/repos/github/expressjs/morgan/badge.svg?branch=master
under the hood, looks at theLocation
response header and parses the percentage from that. I wonder why they go through that trouble 🤔 Maybe the Coveralls API has just always been broken?This is amazing, thank you!