-
Notifications
You must be signed in to change notification settings - Fork 322
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
Basic Install Chromedriver Does Not Start (Windows) #55
Comments
Also from within a vagrant box running debian I get what looks like a shell script, `
` |
It does work on Mac though, but doesn't work when it's running in vagrant. |
It cannot work in vagrant box (based on Windows 10) too. I've got the same error with @Sieabah. |
@Sieabah @vuongggggg Try dev-master branch for this (PR with fix was already merged) |
@mnabialek Nice! Thank you so much. It's work. @Sieabah Try |
I had the same problem and this thread solved it for me. Thanks! My pc runs Windows 10, with the Homestead Vagrant box. |
I got Dusk working with the solutions mentioned above on Windows 7 and Homestead Vagrant. It does however take upwards of 20+ seconds to execute the default tests included. Does anyone know how to speed this up? |
I'll get to testing this tomorrow. |
Can this be closed? |
I try with dev-master and don't work for me, still getting connection refused |
I running over ubuntu, apache2 and php7. But i see that issues and ... I do not want to blow away. Trying execute the code inside SupportsChrome trait on tinker and i get null when start the process. May be smoething is wrong (permissions, locations etc etc) |
@deleugpn i work around on this work with phantomjs. And ... in the past year i work with the facebok web driver but with selenium and it work fine! |
@deleugpn it's work! Using phantomjs, but running it on another terminal.
and then
And it works fine. But, and it is a great but.... After this work for me, phantomjs thrown an error and I look for this githubgist https://gist.github.com/flamingbear/10506888 And the port 9515 (DuskTestCase default port) ever is taken by the crhomedriver, i don't know why... But killing its process, its works, unfortunately i'm killing it after each dusk running... not all was a great solution, but it work for me. Changing the port for another unused, by example 4444... i get green in each test running. This workaround i take from a friend and looking in this work https://twitter.com/laravelphp/status/826534379551936514 |
I got the same problem and found out what the problem on my side was: I had (running Win7) two local environment variables installed: |
This appears to still be an issue. |
how to start chromedriver manually on linux? |
Closing this issue because it's already solved, old or not relevant anymore. Feel free to reply if you're still experiencing this issue. |
Did a fresh install of laravel and the ran composer require laravel/dusk, following the scaffolding and the chrome driver doesn't work. Am I supposed to be running something outside of running the tests that is meant for dusk to connect to?
`
$ ./vendor/bin/phpunit -c phpunit.dusk.xml
PHPUnit 5.7.7 by Sebastian Bergmann and contributors.
`
The text was updated successfully, but these errors were encountered: