-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No captured browser #2
Comments
The same karma.conf and specs run and pass with PhantomJs as the selected browser. |
What happens when you run this command in the terminal? /Users/me/Workspace/Narma/bash-launcher.sh https://www.google.com |
So then with sudo
then with sh instead of sudo
On Wed, 15 Jun 2016 at 12:03 noamtcohen notifications@github.com wrote:
|
run: sudo chmod +x /Users/me/Workspace/Narma/bash-launcher.sh
mkdir /Users/me/Workspace/Narma/test
/Users/me/Workspace/Narma/bash-launcher.sh https://www.google.com |
|
same error :( |
Lets try to isolate the problem. Create an empty directory and put
run: cd NewTestDirectory
./bash-launcher.sh https://www.google.com |
I checked this and I'm getting the same output in the terminal but nodewebkit opens with google.com |
Sorry, yes that does work, but the window does not come to the front. Same On Wed, 15 Jun 2016 at 13:39 noamtcohen notifications@github.com wrote:
|
I'm getting the same error for some reason, I guess it is some update to karma since I haven't used this project for a while. I see that there is a NodeWebKit launcher on npm: This should be a good alternative. |
Os X El Capitan
Node 6.2.1
Karma 0.13.22
Karma cli 1.0.0
Nodewebkit 0.11.6
When running
karma start
I getI have the correct path in my
karma.conf.js
The text was updated successfully, but these errors were encountered: