Karma Debugging - No debuggable browser found

Hi,

I have just installed IDEA 13 on a windows 7 machine. I have managed to get Karma test debugging to work about 5 times. Now it pretty much always fails with a error message in the event log: "17:11:30 Error running all: No debuggable browser found"

This is not true. I have the latest Chrome(Version 32.0.1700.41 m Aura) installed and I use it regularly to debug the applicaiton I am developing.

Other things I have observed:
- Even when I kill all the running karma tests I often find node.exe and phantomjs.exe running in my task manager
- I have completely re-installed nodejs and karma on the odd chance that something was corrupted

Anyone else encounter this?

cheers,
Florian

0
9 comments
Avatar
Permanently deleted user

One other thing: This happens both with the Karma test runnner and with the NodeJS runnner.

0

Hi,

I have just installed IDEA 13 on a windows 7 machine. I have managed to get Karma test debugging to work about 5 times. Now it pretty much always fails with a error message in the event log: "17:11:30 Error running all: No debuggable browser found"


Please try to debug JavaScript in HTML using "JavaScript Debug" Run Configuration.
If debugging is successful, then Karma tests should also be debugged.

Even when I kill all the running karma tests I often find node.exe and phantomjs.exe running in my task manager


To kill node.exe process you need to kill Karma server (there should be a tab named "Karma server").

0
Avatar
Permanently deleted user

hi,

Please try to debug JavaScript in HTML using "JavaScript Debug" Run Configuration.
If debugging is successful, then Karma tests should also be debugged.

The regular javascript debugging works fine and correctly hooks into the Chrome debugger.

To kill node.exe process you need to kill Karma server (there should be a tab named "Karma server").

I have tried this. I have even tried closing IntelliJ IDEA and Chrome. In some cases I still see the process there.

cheers,
Florian

0

The regular javascript debugging works fine and correctly hooks into the Chrome debugger.

Thanks for the info. Well, I'm puzzled.
Could you please attach here a file with content of 'Karma Server' tab?
If possible, please attach idea.log (on the main menu Help | Show Log in Explorer).
Thanks!

I have tried this. I have even tried closing IntelliJ IDEA and Chrome. In some cases I still see the process there.

WIll try to reproduce the issue on Windows.

0
Avatar
Permanently deleted user

Here are the files you requested.

Note: I was able to get the debugging to work once as a NodeJS application, and then it started failing again.



Attachment(s):
idea.log.zip
karma.out.zip
0
Avatar
Permanently deleted user

HI,

I have just made an interesting find.

If I:

  1. run the NodeJS runner called 'Karma Run',
  2. then make sure that the 'open browser after launch' feature is enabled,
  3. then I manually press the karma 'debug' button in Chrome,
  4. and then I manually setup a javascript debug runner then it works.


So it seems the problem is in how the IDEA automates the whole thing.

cheers,
Florian

PS: at least I have a work around now, clumsy, but working

0

According to idea.log, PhantomJS was captured as a slave browser in your karma tests.
Karma tests debugging is working only in Chrome and Firefox.
Just capture one of this browsers and try again.

0
Avatar
Permanently deleted user

That was it. Cool.

:)

Merry Christmas
Florian

0

Good to hear that!

Merry Christmas!

0

Please sign in to leave a comment.