mardi 25 août 2020

Why is jest code coverage report showing inconsistent values?

I am trying to get 100% branch coverage. According to Jest's coverage report each individual file shows 100% coverage but "All files" report shows 96.97%.

If each file is 100%, shouldn't All files also be 100%?

The files that show 0 don't seem to be matter as a previous pull request shows the same files with 0% coverage but "All files" branch cov as 100%. It is only since adding in my new code / feature that I appear to have dropped coverage.

I am running the following to run my tests and get a coverage report:

jest --coverage --watchAll

Am I missing test coverage or is there an inconsistency with the way jest reports coverage?

code coverage report

Aucun commentaire:

Enregistrer un commentaire