-
Notifications
You must be signed in to change notification settings - Fork 7
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
Branch coverage #31
Comments
👍 I'm not yet using Coveralls on my closed source projects because it doesn't measure branch coverage so I still have to run all of my coverage reports locally. Anything we can do to push this feature up in the priority queue? I'd gladly beta test such a feature. |
Any news about this? I would love to see branch coverage in my repos.. |
Adding my vote to this. I'd definitely use it :) |
+1 |
No updates on this? I'd actually been relying on the "100% coverage" reports from coveralls, and only just now happened to look at the actual cov output and see that I have a bunch of missed branches... |
I second @jantman sentiment. As long as the programming languages I use can have |
#216 is possibly a duplicate. |
👍 for it |
+1 This would be amazing. |
Kind of surprised that this has been sitting dormant for two years. Are there any plans to implement this at all in the future? |
The lack of branch coverage statistics in coveralls.io made me switch to codecov.io. I like your interface more though, so please fix this issue so I can come back ;) |
👍 +1 |
👍 |
+1, switching to codecov.io for now |
+1 |
@jcubic I think you may be misunderstanding the term "branch coverage" here. 😉 References: |
Hey @kasperlewau, yes! We quietly released it over the weekend and are watching for issues before making a wider announcement. Let me know if you come across anything fishy. Thanks! |
@kasperlewau I still don't see it at https://coveralls.io/github/Pr0methean/BetterRandom. Is Java supported for branch coverage yet? |
Does Coveralls support branch coverage? (See example.) I know Coveralls supports "hits per line", but that alone does not really tell you if the tests have covered both branches of a conditional.
The text was updated successfully, but these errors were encountered: