-
I'm always getting zero branch coverage in my cobertura files
lcov.info for a file
```
SF:/packages/adaptivecards/lib/adaptive_backplane/adaptive_root.dart
DA:16,1
DA:32,2
DA:81,1
DA:84,2
DA…
-
```
If you call gcov with "gcov -b -c", it provides enough information that you
can measure both branch and condition coverage. It would be really nice if
CoverStory handled them also.
(If you do wor…
-
```
If you call gcov with "gcov -b -c", it provides enough information that you
can measure both branch and condition coverage. It would be really nice if
CoverStory handled them also.
(If you do wor…
-
```
If you call gcov with "gcov -b -c", it provides enough information that you
can measure both branch and condition coverage. It would be really nice if
CoverStory handled them also.
(If you do wor…
-
```
If you call gcov with "gcov -b -c", it provides enough information that you
can measure both branch and condition coverage. It would be really nice if
CoverStory handled them also.
(If you do wor…
-
Hi @trautonen, we're rolling out branch coverage support for Coveralls.io and have landed it in two other integration libraries:
Node: nickmerwin/node-coveralls@d571dac
Python: coveralls-clients…
-
## 🐛 Bug Report
Jest reports wrong branch coverage percentage. Uncovered lines are correct.
## To Reproduce
### **EDIT**
- added `console.log(1/2)` so that branches are not empty. Still wrong/…
-
```
If you call gcov with "gcov -b -c", it provides enough information that you
can measure both branch and condition coverage. It would be really nice if
CoverStory handled them also.
(If you do wor…
-
```
If you call gcov with "gcov -b -c", it provides enough information that you
can measure both branch and condition coverage. It would be really nice if
CoverStory handled them also.
(If you do wor…
-
```
If you call gcov with "gcov -b -c", it provides enough information that you
can measure both branch and condition coverage. It would be really nice if
CoverStory handled them also.
(If you do wor…