dusk: Problem running dusk on Homestead

Finally got it working in Vagrant on Ubuntu 14.04 (not a Homestead image though). My host OS is Windows 10.

First of all, google-chrome is requried to be installed in guest OS:

$ wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
$ sudo sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list'
$ sudo apt-get update && sudo apt-get install -y google-chrome-stable

Next thing is xvfb:

$ sudo apt-get install -y xvfb

Try to start ./vendor/laravel/dusk/bin/chromedriver-linux --port=8888. If you have some errors about loading libraries (libnss3.so, libgconf-2.so.4), try this:

$ sudo apt-get install -y libnss3-dev libxi6 libgconf-2-4

When you see

$ ./vendor/laravel/dusk/bin/chromedriver-linux --port=8888
Starting ChromeDriver 2.25.426924 (649f9b868f6783ec9de71c123212b908bf3b232e) on port 8888
Only local connections are allowed.

this means ChromeDriver can be started (so SupportsChrome trait should be able to start it too). You can stop this process for now (Ctrl+C).

Run

$ Xvfb :0 -screen 0 1280x960x24 &

in a separate terminal window.

Also you may want to add your dev domain in guest’s /etc/hosts file: 127.0.0.1 domain.dev.

And finally run

$ php artisan dusk

PHPUnit 5.7.6 by Sebastian Bergmann and contributors.

.                                                                   1 / 1 (100%)

Time: 3.15 seconds, Memory: 10.00MB

OK (1 test, 1 assertion)

I didn’t try more complex tests for now, but assume they should work. The only thing I’ve noticed not working is a screenshot feature. I have blank white screen instead of actual browser window.

Edit: screenshots feature is working, just don’t load Google Fonts.

just to clarify I had the same problem - I did:

sudo apt-get update sudo apt-get -y install libxpm4 libxrender1 libgtk2.0-0 libnss3 libgconf-2-4 sudo apt-get -y install chromium-browser sudo apt-get -y install xvfb gtk2-engines-pixbuf sudo apt-get -y install xfonts-cyrillic xfonts-100dpi xfonts-75dpi xfonts-base xfonts-scalable sudo apt-get -y install imagemagick x11-apps

and then

chmod a+x ./vendor/laravel/dusk/bin/chromedriver-linux

and it seemed to have solved the problem

Lots of solutions floating around but this here is the official solution that will be included in the next vagrant homestead box. I’ve tried it and it works good

https://github.com/laravel/homestead/pull/528/files#diff-6c17dd8d21b8b745850a87b9d0de77c7

basically run

sudo apt-get update
sudo apt-get -y install libxpm4 libxrender1 libgtk2.0-0 libnss3 libgconf-2-4
sudo apt-get -y install chromium-browser
sudo apt-get -y install xvfb gtk2-engines-pixbuf
sudo apt-get -y install xfonts-cyrillic xfonts-100dpi xfonts-75dpi xfonts-base xfonts-scalable
sudo apt-get -y install imagemagick x11-apps

and then update your aliases with the latest ones which includes this new function

function dusk() {
     pids=$(pidof /usr/bin/Xvfb)
 
     if [ ! -n "$pids" ]; then
         Xvfb :0 -screen 0 1280x960x24 &
     fi
 
     php artisan dusk "$@"
 }

You can also alternatively use this release candidate homestead box which has the fix in it https://atlas.hashicorp.com/Svpernova09/boxes/nothomestead

The following, (taken from here) worked for me:

# makes sure all your repos are up to date
sudo apt-get update
# chrome dependencies I think
sudo apt-get -y install libxpm4 libxrender1 libgtk2.0-0 libnss3 libgconf-2-4
# chromium is what I had success with on Codeship, so seemed a good option
sudo apt-get install chromium-browser
# XVFB for headless applications
sudo apt-get -y install xvfb gtk2-engines-pixbuf
# fonts for the browser
sudo apt-get -y install xfonts-cyrillic xfonts-100dpi xfonts-75dpi xfonts-base xfonts-scalable
# support for screenshot capturing
sudo apt-get -y install imagemagick x11-apps

# Once all this has run through, you need to fire up xvfb on your homestead box. If you’re planning to # do this on a regular basis, you’ll want to get this setup on boot, but for the sake of testing things out:
Xvfb -ac :0 -screen 0 1280x1024x16 &

nope, just comment out the --headless line on the driver() method in DuskTestCase

OK! My answer here : https://developers.google.com/web/updates/2017/04/headless-chrome :

So I still need Xvfb?

No. Headless Chrome doesn’t use a window so a display server like Xvfb is no longer needed. You can happily run your automated tests without it.

What is Xvfb? Xvfb is an in-memory display server for Unix-like systems that enables you to run graphical applications (like Chrome) without an attached physical display. Many people use Xvfb to run earlier versions of Chrome to do “headless” testing.

is this fixing it for other people? I am still having issues on the current v1.0.5

@webcrazy same issue here (Laravel 5.5, Win10, Homestead). What makes me said, is that, it was working fine, at least for last couple of months. For me, one issue is that, screenshots are blank/white. The other one, I am facing, is getting failed tests, when I use assertPathIs() after redirect. It happens only, if I run chromedriver in headless mode. With windowed mode, all tests pass green. What is intriguing, that my tests pass green in my gitlab CI.
So this issue is even more confusing… BTW I’ve tried chromedriver 2.33 and 2.35, same result.

@browner12 Thanks. If i disabled --headless, it works as expected but if I turn on, I got error and error screenshots become blank. not sure why. looks like I will have to stick with --headless for the time being.

not really sure. might be legacy hack from before Chrome had a true “headless” mode.

seeing as Chrome “headless” was released in June of this year, this seems most likely.

Ok but what is Xvfb for then ? Xvfb -ac :0 -screen 0 1280x1024x16 & : This is running on the headless homestead VM ? How does the graphical chrome on host gets fired then ?

@tzurbaev thanks for your comment. Saved my butt.

@murribu Thank! This really help. I can run duck in Homestead.

I am still having issues on the current v1.0.5, too.

@browner12

No, I get a timeout:

Facebook\WebDriver\Exception\WebDriverCurlException: Curl error thrown for http POST to /session with params: {"desiredCapabilities":{"browserName":"chrome","platform":"ANY"}}

Operation timed out after 30001 milliseconds with 0 bytes received

@SaeedPrez On my end https://github.com/laravel/dusk/pull/70 fixed this (but haven’t run full Dusk test yet because of further connection problems that I need to solve in free time that were mentioned also in this thread)

I’m having issues running on Homestead as well, but I’m running my Vagrant box on Linux Mint. I have updated Homestead to latest, and tried using a new test site. Also, tried the various methods listed above which didn’t work.

If I follow the Dusk setup exactly, I get the following:

There was 1 error:

1) Tests\Browser\ExampleTest::testBasicExample
Facebook\WebDriver\Exception\WebDriverCurlException: Curl error thrown for http POST to /session with params: {"desiredCapabilities":{"browserName":"chrome","platform":"ANY"}}

Failed to connect to localhost port 9515: Connection refused

/home/vagrant/test/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:287
/home/vagrant/test/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:121
/home/vagrant/test/tests/DuskTestCase.php:32
/home/vagrant/test/vendor/laravel/dusk/src/TestCase.php:180
/home/vagrant/test/vendor/laravel/framework/src/Illuminate/Support/helpers.php:639
/home/vagrant/test/vendor/laravel/dusk/src/TestCase.php:181
/home/vagrant/test/vendor/laravel/dusk/src/TestCase.php:111
/home/vagrant/test/vendor/laravel/dusk/src/TestCase.php:85
/home/vagrant/test/tests/Browser/ExampleTest.php:21

ERRORS!
Tests: 1, Assertions: 0, Errors: 1.

EDIT

I have gotten a little farther by marking the /vendor/laravel/dusk/bin/chromedriver-linux executable: chmod a+x ./vendor/laravel/dusk/bin/chromedriver-linux

After making this edit, I now get a timeout error:

There was 1 error:

1) Tests\Browser\ExampleTest::testBasicExample
Facebook\WebDriver\Exception\WebDriverCurlException: Curl error thrown for http POST to /session with params: {"desiredCapabilities":{"browserName":"chrome","platform":"ANY"}}

Operation timed out after 30000 milliseconds with 0 bytes received

/home/vagrant/test/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:287
/home/vagrant/test/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:121
/home/vagrant/test/tests/DuskTestCase.php:32
/home/vagrant/test/vendor/laravel/dusk/src/TestCase.php:180
/home/vagrant/test/vendor/laravel/framework/src/Illuminate/Support/helpers.php:639
/home/vagrant/test/vendor/laravel/dusk/src/TestCase.php:181
/home/vagrant/test/vendor/laravel/dusk/src/TestCase.php:111
/home/vagrant/test/vendor/laravel/dusk/src/TestCase.php:85
/home/vagrant/test/tests/Browser/ExampleTest.php:21

ERRORS!
Tests: 1, Assertions: 0, Errors: 1.

I tried another solution from @abalozz (#10).

• Installing xvfb apt-get install xvfb
• Modifying the SupportsChrome Trait: static::$chromeProcess = new Process('xvfb-run ./chromedriver-linux', realpath(__DIR__.'/../bin'), null, null, null);

Unfortunately, this solution seems to be buggy since the tests are sometimes very slow to run.