How to debug coverage source remap? about ts-jest HOT 6 CLOSED

Also output in console is seems to be wrong - probably we have to investigate and fix it.

: I've investigated this and currently it's not possible.

Jest writes coverage by delivering result to coverage reporter while collecting all test results. Console output for coverage happens at this time, before testresultprocessor being invoked. So its output is before-mapping, then coverage processor takes over try to remap its results.

It is because design of test result processor limitation, details at here : jestjs/jest#1907 (comment) unless there's upstream changes to have specific hooks invoked to return mutated results back to jest or change behavior of current hooks, there isn't way to achieve this.

from ts-jest.

If you want to give it a spin:

• clone repo
• npm i
• jest --coverage --no-cache
  Coverage will be in coverage folder found in project root.

from ts-jest.

Ok, I've found out what is wrong. Our coverage is in ./coverage/remapped folder, not in ./coverage and it could be confusing. Also output in console is seems to be wrong - probably we have to investigate and fix it.

from ts-jest.

By using reporters in package.json :
"coverageReporters": [ "html", "text", "lcov", "lcovonly", "json" ],

Differences:

• html goes into ./coverage/remapped/html , original is ./coverage . The file structure is also not the same: remapped contains an additional src folder.
• lcov is missing completely, original is ./coverage/lcov-report .
• json goes into ./coverage/remapped/coverage.json , original is ./coverage/coverage-final.json . Filename differs.

lconvonly seems to have right filename: ./coverage/remapped/lcov.info , original is ./coverage/lcov.info .

from ts-jest.

Please note coverage processor do not exactly follow configurations of jest.

html: it's generated by remap-istanbul via remapped source mapping. It is expected to have different structure. coverage processor does not touch folder structure other than output location.
lcov: for some reason remap to lcov from jest's output simply doesn't work, so remapping is skipped.

Filename differs

: it is expected. Jest does not exposes which configuration they're using (for example, file name) so coverage processor does not have way to know what was original file name saved and match with it. Instead, it tries best effort to create possible coverage report with own naming https://github.com/kulshekhar/ts-jest/blob/master/src/coverageprocessor.ts#L41

from ts-jest.

Closing in favor of #101

from ts-jest.