In windows 10, does laravel dusk always open the 'chrome' browser? about dusk

[josealgardataborges]

and eventually i get this: http://prntscr.com/e11ns9

[Symfony\Component\Process\Exception\ProcessTimedOutException]
The process ""C:\webdev\www\duskproject.app\vendor\bin\phpunit.bat" "-c" "C:\webdev\www\duskproject.app\phpunit.dusk.xml" """ exceeded the timeout of 60 seconds.

[alex-LE]

I get the same timeout error. It seems that the Symfony ProcessBuilder has a default timeout of 60s.
My test is currently running > 70s and so i get the timeout. If is set the timeout to a higher value, it works.

Even if i split my tests into smaller classes/files i get the timeout.

A timeout of 0 seems to prevent the Exception, added PR for that.

[KayLeung]

Either Chrome or Firefox is not a headless browser. You could try PhantomJS or wait to see if anyone bind it to nighmare.js

[deleugpn]

Can this be closed?

[josealgardataborges]

@deleugpn If it's a feature not a bug, please do close it.

[deleugpn]

It is indeed a feature. Not only that, it's the core concept of Dusk. The goal is to run the tests on an actual browser to have a better sense of the behavior of your application. It is possible to run Dusk on a headless machine using Xvfb. My CentOS can run a simple login test in a couple of seconds with 1 CPU Core and 1500MB of RAM.