2

I am using mocha to test my code. I am using node inspector to debug my code.

bash mocha test/test.* --debug-brk

This works but not so well. It stops at the first line of code in mocha. I want it to stop it at my code. I tried using the 'debugger' key word to make a manual breakpoint but some how it does not stop there.

tusharmath
  • 10,622
  • 12
  • 56
  • 83
  • This question has some useful information on using mocha+node-inspector: http://stackoverflow.com/questions/14285201/whats-the-least-resistance-path-to-debugging-mocha-tests – Simon Lang Mar 19 '14 at 03:55

2 Answers2

3

Try placing a breakpoint at the bottom of the mocha library per this issue. For some reason that allows debugger statements in your modules to pause the node debugger.

However it doesn't seem to stop at debugger statements in the spec itself. I have a SO question highlighting that problem.

Community
  • 1
  • 1
Thomas
  • 5,736
  • 8
  • 44
  • 67
1

I was on the latest node version, using the node-debug command (to launch node-inspector and having the same issues you were. Here's what I'm rolling with currently:

Using the following versions:

  • node: 0.11.13 (I downgraded from latest) <-- I specifically had to use this one
  • mocha: 2.2.1 <-- might work with any
  • node-inspector: 0.9.2 <-- might work with any

Start your tests using the following command:

  • node-debug _mocha test/unit-tests.js

Navigate to your test file and start putting in breakpoints, then hit run. I usually put one up by the 'requires' of my test file, and several within my 'it' functions.

Hope that helps, and that one day this kind of thing will just work :P

Got the idea to downgrade node from here: https://www.bountysource.com/issues/7978672-script-is-resumed-as-soon-as-node-inspector-is-loaded

And the command from here: https://github.com/node-inspector/node-inspector#how-do-i-debug-mocha-unit-tests

Jacob McKay
  • 2,776
  • 1
  • 19
  • 20