Different types of coverages

[pavelsaman]

This is more of a question about the reasoning about the different types of coverages and total coverage.

In parser.js, line, function, and branch coverages are counted, but then only lines results are taken into account when counting the total coverage.

Why is branch and function coverage dropped? If only line coverage should be taken into account, why parse lines related to branch and function coverage in the parser? It's extra work that's dropped a few moments down the line.
Can the total() function return 3 numbers (lines, branch, function total coverages), instead of one?

[simon-something]

It looks like #293 would add branch coverage (found this issue as I need this too, branch coverage is, imo, a more interesting metric for CI check) - do you still have time to maintain this @simonecorsi or should we fork away? Happy to PR/review this changes if you need!

[simonecorsi]

@drgorillamd I've been pretty busy but I think we can work this out, if the author of the PR is still active

[simon-something]

@simonecorsi np, happy to help (even tho busy too;) - it looks like the PR author has been consistently commiting... timestamps for the past couple of months, not 100% sure they're still active beside what looks like a bot.
Happy to open a new PR to add it, "soon" :D

[simonecorsi]

@drgorillamd Is the feature in the PR by the author in line with the feature you need? In that case, I can proceed with a major release.

My only concern is understanding if this is what you need (I only need the check on the total). It seems to me that including the count of branches with the total might not be what you are asking for, but rather having a granular control to choose whether to check the total or the branches. In this case, I would say that I can merge the PR, but then you would definitely need to make another one to adapt it to your use case