wrong tests being marked when line-number out of sync

[connectdotz]

Environment

1. node -v: 8.9.1

2. npm -v: 3.10.10 (yarn: 1.7.0)

3. npm ls react-scripts (if you haven’t ejected): n/a

4. Operating system: macOS 10.13.5

Steps to Reproduce

the vscode-jest repo is the perfect example. It currently has source-map issue which caused the ts src line number got out of sync with the generated js files that used by jest. add a simple failed test case to make sure the actual test error line number reported by jest falls to the other test block.

Expected Behavior

it's ok not to mark the actual line that caused the error since the linenumber is wrong, but we should not mark the wrong test when the name clearly does not match.

Actual Behavior

The itBlock where the line number falls into, as well as the itBlock matches the actual failed test by name, will both be marked as failed.

---

Note we are looking for someone to take responsibility around keeping create-react-app up to date and working, could this be you?

[connectdotz]

vscode-jest 2.9.0 has shipped with jest 23.x support and more, which should address this issue. Feel free to reopen if otherwise.