Comments on: Debugging mocha unit tests with WebStorm step by step

By: Glenn Block

Glenn Block — Fri, 18 Jan 2013 09:48:00 +0000

@andy

Yes, it is due to the spawning. I didn’t want to go into detail which is why I put ‘It’s very important that you point to the _mocha file as you can see below.’, however if you think it is valuable to add I can.

@ryan. Glad it helped!

By: Ryan Regalado

Ryan Regalado — Fri, 18 Jan 2013 08:14:00 +0000

Thanks for posting. This was super helpful in a node.js app I’ve been debugging and writing tests for. Awesome

By: Andy Fleming

Andy Fleming — Thu, 17 Jan 2013 23:53:00 +0000

Answering my own question, but might be worth updating the post.

From the linked post:
“Pointing the run configuration to _mocha is quite important since the main mocha binary spawns a new process you cannot connect via a debugger!”

By: Andy Fleming

Andy Fleming — Thu, 17 Jan 2013 23:49:00 +0000

Quick question: Why is it “very important that you point to the _mocha file” rather than the mocha file.

Looking at the source it seems mocha is a wrapper for the “real” _mocha – but presumably they’ve done this for a reason and you’re bypassing it?

Just curious