Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

line number incorrect even in a simple example (Node 7 and no React) #412

Closed
Tuizi opened this issue Jan 10, 2018 · 2 comments
Closed

line number incorrect even in a simple example (Node 7 and no React) #412

Tuizi opened this issue Jan 10, 2018 · 2 comments

Comments

@Tuizi
Copy link

Tuizi commented Jan 10, 2018

  • Issue
    Line number in coverage result table are not correct. The line number sometimes correspond to an empty line or a line with a }.
    I know that there is an issue with line number when using Node 8 and React 16, but I just did a small example using Node 7 and without React... Pure Typescript and line numbers are not correct.

  • Expected behavior
    Line number in the coverage result should match line of the Typescript files

  • Link to a minimal repo that reproduce this issue

Clone https://github.com/Tuizi/ts-jest-issue-repo and npm install && npm test

@Tuizi
Copy link
Author

Tuizi commented Jan 11, 2018

"mapCoverage": true, in seems to be the solution for my issue.

@GeeWee GeeWee closed this as completed Jan 12, 2018
@chiubaka
Copy link

For anyone stumbling upon this late, the mapCoverage Jest option was removed and its behavior has been enabled by default. See here: jestjs/jest#5177

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants