Yet another JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use cases including unit tests, server side functional tests and browser tests. Built for scale.
Other
8.7k
stars
786
forks
source link
Branches that don't exist get reported as missing #941
I haven't been able to test anything with toHaveStyleRule and jest-styled-components because of some issue with my configuration and/or mismatching versions, but still i thing that file should be totally covered
Here's my configuration in case I'm missing something:
I'm getting a coverage report with missing coverage for branches that aren't there (I think):
Here's the test:
Another example:
And its test:
I haven't been able to test anything with
toHaveStyleRule
andjest-styled-components
because of some issue with my configuration and/or mismatching versions, but still i thing that file should be totally coveredHere's my configuration in case I'm missing something:
package.json:
babel.config.js:
jest.setup.js:
Any help would be appreciated! Please let me know if I'm wrong and why are there any branches there... Thanks a lot!