Closed voidgraphics closed 2 weeks ago
Can you run php artisan dusk:chrome-driver --detect
and try again
Of course. The problem persists:
I don't really understand what just happened but here it is: on my colleague's machine, the prepare
method of DuskTestCase
is never called, so it does not start the chrome driver process. I suspected the same was happening to me, so I added a dd('test')
to it, and it did show on my machine.
The interesting part is that after removing the dd()
, now dusk seems to work:
I did not change anything really.
It's hard to debug what's missing on the initial install. not calling prepare()
might indicate and old PHPUnit installs. The error earlier might indicate missmatch version between Chrome and ChromeDriver.
The prepare
issue is indeed on an older project, but that problem is different, let's ignore it for now.
I tried making yet another fresh Laravel project, and doing the exact steps I described before:
laravel new dusk-project # I chose Pest as the testing framework, don't know if it also fails with phpunit
cd dusk-project
composer require laravel/dusk --dev
php artisan dusk:install
php artisan dusk
I still get the dusk error. However, running php artisan dusk
a second time, it works:
I tried doing this on two different machines and I get the same result.
Dusk Version
8.2
Laravel Version
11.26
PHP Version
8.3.11
PHPUnit Version
11.3.6
Database Driver & Version
No response
Description
Error message when running
php artisan dusk
on a fresh laravel install:Steps To Reproduce