Testacular cannot find Chrome on windows.

I recently started playing with AngularJS. After downloading the seed project and trying to run the tests with Testacular, I bumped into small issue that was not immediately obvious to resolve.

When I ran the “./scripts/test.bat” I would get the following error(s) in my console:

info: Testacular server started at http://localhost:9876/
info (launcher): Starting browser Chrome
error (launcher): Cannot start Chrome
        CreateProcessW: The system cannot find the path specified.

info (launcher): Trying to start Chrome again.
error (launcher): Cannot start Chrome
        CreateProcessW: The system cannot find the path specified.

info (launcher): Trying to start Chrome again.
error (launcher): Cannot start Chrome
        CreateProcessW: The system cannot find the path specified.

Tracked down link on a Google thread: https://groups.google.com/forum/?fromgroups=#!msg/angular/1li0HKtW56U/lKyT_VId0b0J

It appears that Testacular looks for the chrome browser in a CHROME_BIN environment variable.

To resolve the issue I ran the following PowerShell script and I was able to run the tests.

[System.Environment]::SetEnvironmentVariable("CHROME_BIN", "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe")

Your path to chrome may vary!

 

Happy Testing!

3 thoughts on “Testacular cannot find Chrome on windows.”

  1. Testacular? So I’m guessing the developers meant to play on the word “spectacular”, not “testicular”, but puns do tend to rely on edit distance…

Comments are closed.