How do you debug Jasmine tests with Resharper?

Question

I can't find a way to debug (walk through) JavaScript code when running Jasmine tests with Resharper in Visual Studio 2012. I tried running tests with browser (Chrome) but the test runner closes the port as soon as the test is run and so I cannot put a breakpoint in the code. Also tried running in Internet Explorer and put breakpoints in Visual Studio but it won't attach to the process. My test has a lot of ///reference scripts that Resharper includes automatically in the test runner but I don't want to manually do this for every test that I want to debug. Please help me understand this. If you have a jasmine test that is failing, then how do you debug it?

My workaround so far is not to use Resharper for debugging. Do the manual work: Get Jasmine Standalone Test Runner and include all references in script tags and include the test itself. Then debug in the browser's developer console. — orad, Apr 26 '13 at 00:28
Do I understand correctly that Re# runner opens the browser and you want to debug your specs in the browser? — zbynour, Apr 26 '13 at 06:36
@zbynour Can't do that because it closes the http port as soon as the test is done. — orad, May 02 '13 at 22:44

Torbjörn Nomell · Answer 1 · 2015-10-09T05:31:27.037

33

Since I didn't got debugger; to work I found another solution. By adding the following to my test, resharper won't be notified that the test has finished so we can set debug breakpoints in the opened browser (I use chrome) and update (F5) the page.

jasmine.getEnv().currentRunner_.finishCallback = function () {};

Since Jasmine 2.0 you need to use:

ReSharperReporter.prototype.jasmineDone = function () { };

Stop the tests in resharper testrunner window when you're done.

Also this can be done for QUnit

QUnit.moduleDone = function(){}

edited Oct 09 '15 at 05:31

answered Jun 13 '13 at 12:53

Torbjörn Nomell

3,020
2
24
20

Not the most obvious solution :) And kudos to @Kestas for the Jasmine 2.0 part – Torbjörn Nomell May 06 '15 at 09:03
2

Also, if the tests are in TypeScript files, you'll get an error on access the `ReSharperReporter` global variable. One work around is to use syntax like this: `window['ReSharperReporter'].prototype.jasmineDone = function () { };` – zumalifeguard Nov 02 '15 at 20:36

score 19 · Accepted Answer · edited May 23 '17 at 12:09

19

Try to use debugger keyword. Simply add the following line to the code you want to debug (perhaps into the spec):

debugger;

It invokes any available debugging functionality. It doesn't work in IE but works pretty well in Chrome (you wrote you use it so I guess it's enough just for debugging).

Of course, after that be sure to remove the debugger keyword! Perhaps there is no really simple way how to avoid it in production code in general (in case you will use it not only in spesc) but if you are interested in this SO question could be helpful.

edited May 23 '17 at 12:09

Community

1
1

answered May 03 '13 at 05:54

zbynour

19,747
3
30
44

1

Great, I thought `debugger;` was supported in IE only because I used it before but didn't know it existed in Chrome also. Thanks! – orad May 08 '13 at 20:25
3

This doesn't seem to work for me within Chrome as it happily continues execution without ever jumping to debugger. Any other suggestions? – Matt Klinker May 23 '13 at 14:44
1

@mklinker excuse me please for too long response time... The only thing which came to my mind is to open developer tools in the browser (because it invokes "any available debugging funxtionality" so no debugger opened means it happily continues as you wrote). But I don't know whether it is possible to do that (in which way you open the browser). Currently I use Testacular runner so it is easy to open dev tools in the captured browser (because it remains opened). – zbynour Jul 01 '13 at 14:21
3

This won't do the job due to ReSharper opens a new page each time you press "Run Unit Test" and you cannot hit F12 fast enough to open the developer console on your browser. And ReSharper randomizes the port where the test server is running so the browser cannot remember you hit F12 already. – Marcel May 04 '16 at 08:12

score 1 · Answer 3 · edited May 23 '17 at 12:33

1

As I posted on Debugging jasmine tests with resharper and phantom js

I got debugger; to work by setting IE 11 as my test browser in ReSharper options. The cool thing is that you can set your breakpoints in the Visual Studio version of the code and set through and debug using Visual Studio. You really do not need to interact with the browser.

edited May 23 '17 at 12:33

Community

1
1

answered Feb 16 '16 at 17:53

Jason Bowers

496
6
12

jolySoft · Answer 4 · 2017-02-09T15:52:38.277

0

I know this is an old question and this answer is slightly off topic but if you don't want to interfere with the callback Chutzpah test runner context menu could support you here. Run the tests in resharper/phantomjs (so you don't get tab explosion) and debug in Chrome (or the your preferred browser) fired off a right click:

Chutzpah Test Runner Context Menu Extension

edited Feb 09 '17 at 15:52

answered Feb 03 '17 at 16:25

jolySoft

2,948
2
30
34

How do you debug Jasmine tests with Resharper?

4 Answers4

Linked