Karma start throws spawn ENOENT error

[Dustin Dexter]

This is on a Windows machine, but I am trying to use Testacular/Karma.  I installed node, got jasmine and karma via NPM and installed globally. I tried to run 'karma init', but it wouldn't let me get past what testing framework i wanted to use.  I created my own, but now, when I run 'karma start', i get an error saying 'Error: spawn ENOENT'. Any ideas?

[Dustin Dexter]

Found the issue. I had to add a CHROME_BIN env variable. Oh, and i had to do a Ctrl+Enter for each step in the karma init process.

[Rory Douglas]

Is that all you did to make it work? i'm having same error (both with testacular 0.6 and karma 0.8) on Win7/64, but setting CHROME_BIN doesn't help. I'm using Angular 1.0.5, node.js 0.10.2.

[Rory Douglas]

erm nevermind, seems only the auto-launching of chrome is broken. if i manually capture browser, tests run fine, which is all i need.

[Dave Barton]

I was able to get Karma to work by setting CHROME_BIN to point to c:\progra~2\Google\Chrome\application\chrome.exe instead of using quotes, as in set CHROME_BIN="c:\program files (x86)\Google\Chrome\application\chrome.exe".   Obviously more of an issue when running on 64-bit windows.