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

Supporting interactive debugger for tests #2775

Closed
jcrben opened this issue Apr 21, 2017 · 2 comments
Closed

Supporting interactive debugger for tests #2775

jcrben opened this issue Apr 21, 2017 · 2 comments
Labels
status: waiting for author waiting on response from OP - more information needed type: question support question

Comments

@jcrben
Copy link

jcrben commented Apr 21, 2017

I've never been able to get my debuggers or breakpoints to work inside tests. Typically using Webstorm or Intellij Ultimate. Just tried again today with node v7.7.4 and Intellij 2017.1 since I noticed that a Jetbrains developer added support for child process debugging to ava: avajs/ava#874

Thoughts on adding this functionality, perhaps by taking a close look at ava's approach? It's also possible that this will be more widely available once nodejs/node#5025 lands; also a feature request at nodejs/node#9621

If this is already supported, some tips would be handy. Noticed this issue #1091 where someone was talking about --debug-brk so maybe I'm missing something

@drazisil drazisil added type: feature enhancement proposal status: waiting for author waiting on response from OP - more information needed labels Apr 21, 2017
@boneskull
Copy link
Contributor

@jcrben I don't have this issue, so I'm going to need more information about your configuration. Can you send me a project or something small & reproducible?

The only times when I do run into problems is when there are several transpilation steps.

@boneskull boneskull added type: question support question unconfirmed and removed type: feature enhancement proposal labels Jun 3, 2017
@jcrben
Copy link
Author

jcrben commented Jun 11, 2017

Hmm, I think it must have been something in my setup - either the project or how I was setting up the IntelliJ launch configuration. I tried reproducing it with a small test case using the VSCode Mocha Tests configuration at https://github.com/Microsoft/vscode-node-debug/blob/7dacdc985ad42e45c31d5e4a986201bc780de13c/package.json#L211 and it seems to work OK.

@jcrben jcrben closed this as completed Jun 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting for author waiting on response from OP - more information needed type: question support question
Projects
None yet
Development

No branches or pull requests

3 participants