Coverage Report - incorrect lines about ts-jest HOT 11 CLOSED

+1 for this

from ts-jest.

Guys, not sure if is related but I'm a bit confused:

• I only get the remapped folder when I'm in watch mode. But, in that case the coverage gets crazy and it gets lowered a lot
• It works better just by running "jest --no-cache --coverage", but still the coverage is not correct. It gives me statements and branches not covered (even in comments), and they are.

Coverage: https://coveralls.io/github/coosto/ShortcutJS
Tests: https://github.com/coosto/ShortcutJS/tree/master/test

Wanted to open an issue but I think this one is related. Any known workaround in the meanwhile?

from ts-jest.

I have to admit current coverage ergonomics causes confusions between what to trust / what to not to trust, and also what is not possible.

1. Console / terminal output summary
   : @kulshekhar is correct, it is known issue and cannot have workaround at the moment. refer attached issue comment for detail. (#42 (comment)) It may need some documentation / instruction for this.

2. What coverage report is accurate?
   coverage/remapped is one you need look into. reports directly under coverage is original one created via jest, and remapped is actual coverage postprocessed by jest. I've made those orgnization without give much caution by I was too familiar jest generated reports under coverage, and it makes sense to preserve original for anyone need to take look into those. probably remove orignal coverage or support #61 might have less confusion.

from ts-jest.

would it be possible for you to create a minimal repo that reproduces this issue?

from ts-jest.

Yep, here it is:
https://github.com/tyleralves/tsJestExample

from ts-jest.

thanks @tyleralves

I'll try to take a look at this as soon as I find some time!

from ts-jest.

@tyleralves I was trying this out now and just noticed the edited part of the original issue. I think this is a known issue.

Note that I haven't worked on the coverage part I'm not too familiar with it. I hope @kwonoj can confirm/refute this

from ts-jest.

#101 is related as well related to console summary.

from ts-jest.

Closing in favor of #101

from ts-jest.

The --no-cache option works for me

from ts-jest.

I do not have the remapped folder inside coverage.

How can I get an accurate/remapped coverage report?

from ts-jest.