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

When coverage is enabled, debugging Typescript is broken #531

Closed
Gorthog opened this issue Dec 10, 2019 · 1 comment
Closed

When coverage is enabled, debugging Typescript is broken #531

Gorthog opened this issue Dec 10, 2019 · 1 comment

Comments

@Gorthog
Copy link

Gorthog commented Dec 10, 2019

Environment

  1. node -v: v12.13.1
  2. npm -v: 6.12.1
  3. npm ls jest: jest@22.0.4
  4. your vscode-jest settings if customized:

"jest.pathToJest": "npm run jest:watchAll --",
"jest.runAllTestsFirst": false,
"jest.showCoverageOnLoad": true,

  1. Operating system: Ubuntu 18.04.2 LTS via WSL2

Prerequisite

  • are you able to run jest test from command line? yes
  • how do you run your tests from command line? (for example: npm run test or node_modules/.bin/jest) npm t

Steps to Reproduce

clone https://github.com/sinapis/typescript-jest

place a breakpoint in file src/vowel-counter.ts:3

run "debug jest" task

Expected Behavior

breakpoint is hit

Actual Behavior

no breakpoint is hit

The problem seems to be code coverage. if code coverage is disabled (change .settings:14 from "true" to "false") the breakpoint is hit while debugging.

@Gorthog
Copy link
Author

Gorthog commented Dec 16, 2019

This is a known issue for jest. Not related to vscode extension. closing.

@Gorthog Gorthog closed this as completed Dec 16, 2019
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

1 participant