Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Branch coverage
See original GitHub issueApparently, Coveralls now supports branch coverage.
https://github.com/lemurheavy/coveralls-public/issues/31#issuecomment-284375195
I don’t see the changes to the web API documented yet, but I do see that the Node client seems to support it via the branches key. branches is a sibling of coverage in the dictionary the client submits to Coveralls.
https://github.com/nickmerwin/node-coveralls/commit/15750503b69c3143b3020fa5d4fe4fc1d455356e https://coveralls.io/github/nickmerwin/node-coveralls?branch=master
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@jvarho great catch, ok that’s fixed now:
https://coveralls.io/builds/10504337/source?filename=coveralls%2Fapi.py#L184
@TheKevJames ah good call, that’s fixed now – branch coverage won’t show for a build when total branches is zero, so no need for that extra check.