-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Add branch coverage to coveralls statistics #4444
Comments
And also as you commented in another PR, we should try to make "failures" ignore anything less than .5% or such. |
Unless I'm mistaken, coveralls.io has simply started to show branch coverage, hasn't it? The rest depends entirely on what code we actually run in our tests, i.e. do we actually run all branches everywhere? (I doubt it, there are lots of places where we don't deliberately try to cause faults, for example) |
Or do you have to switch something on to display branch coverage? I've looked around a bit, but can't find such a switch. If there is one, someone please point it out, thank you. |
coveralls needs to be told to display them - that's in project Settings → Badge and Token → Branch Coverage checkbox near "Include in Aggregate %" after both of those things are done, a new run should have two new columns in the source file listing - branch hits and branch misses |
Ok, thanks for the info. I've just changed the settings at Coveralls, and pushed a PR to add the flags in our .travis.yml |
Fixes openssl#4444 [extended tests]
Coveralls.io recently gained support for measuring not only line coverage but also branch coverage: lemurheavy/coveralls-public#31 (comment)
I'd like to see it reported openssl builds
The text was updated successfully, but these errors were encountered: