samedi 17 octobre 2020

Jest coverage missing branches on import statement inside lcov report

I am trying to figuring out why I am having missing branches on ignored import files when checking the Jest Coverage lcov report.

I have 100% line coverage, but other types of coverage (statement, branch and functions) are pretty low. I wasn't sure about the reason so I checked the HTML report that jest creates with lcov, and when I checked, I saw that there are a lot of import statements that are marked with many missing branches warnings.

E.g (report on coveralls): enter image description here

Not sure what a missing branch warning over an import means. So my concern is, why do I have a warning on an import statement? how do I cover an import statement? am I missing additional configuration?

Aucun commentaire:

Enregistrer un commentaire