Unable to run "grunt jasmine_chromeapp"

[dborkan]

Seeing this issue on my Mac with a fresh clone of freedom-social-xmpp:

grunt jasmine_chromeapp
Running "jasmine_chromeapp:all" (jasmine_chromeapp) task
Building...Done.
Starting Reporter...Done.
Starting Chrome...Fatal error: spawn ENOENT

[dborkan]

Any ideas on this? This is still happening with the latest grunt-jasmine-chromeapp version 1.7.0

[willscott]

@iislucas you mentioned something as well about doing a better search for chrome on the machine.
@dborkan where is your chrome binary?

This seems like a grunt-jasmine-chromeapp bug, rather than a social-xmpp bug.

[dborkan]

Ah I think that's part of the problem. I had several versions of Chrome, but they were all at locations like "/Applications/Google Chrome Beta.app/". I just renamed "/Applications/Google Chrome Stable.app/" to "/Applications/Google Chrome.app/" and now Chrome is starting, however I'm getting some different errors now that are causing all tests to fail:

• In chrome://extensions I see the error 'content_security_policy' is only allowed for extensions and legacy packaged apps, but this is a packaged app.
• In the main.html console for the app, I see a lot of errors like Failed to load resource: net::ERR_FILE_NOT_FOUND chrome-extension://khhlpmfebmkkibipnllkeanfadmigbnj/scripts/dist/social.google.json

[willscott]

for point 1, we do set a CSP: https://github.com/willscott/grunt-jasmine-chromeapp/blob/master/tasks/jasmine-chromeapp/manifest.json#L18
willscott/grunt-jasmine-chromeapp#12

for point 2, it sounds like files aren't getting copied into the right places in this repo.

It looks like that's because when you added the jasmine-chromeapp
d3fd87e
we were still figuring out the syntax

We're now on v1.7, which uses src and paths rather than helper, because we wanted more expressivity in where scripts are placed.