Getting strange failures in dusk, and wrong chromedriver version printed. SOLUTION - development

Getting strange failures in dusk, and wrong chromedriver version printed. SOLUTION

TLDR in bold below.

Just going to post this because I ran in to it today.

Seems like I’m always riding the wave of my laptop’s chrome version, the current version of chromedriver, and whatever version of chromedriver is currently shipping with Laravel Dusk.

I saw that Chrome just ticked up to 65, and chromedriver updated to 2.36 last night. Laravel Dusk doesn’t have the latest, so I manually copied the latest chromedriver into ‘vendor/laravel/dusk/bin’ to give it a try, maybe that would fix my weird failing tests.

Test output was this:

6) TestsBrowserMyCoolTest::testMyFeatureWorks FacebookWebDriverExceptionUnknownServerException: unknown error: call function result missing 'value' (Session info: chrome=65.0.3325.146) (Driver info: chromedriver=2.33.506106 (8a06c39c4582fbfbab6966dbb1c38a9173bfb1a2),platform=Mac OS X 10.13.3 x86_64) 

Notice the “chromedriver=2.33”. That’s weird because chromedriver was on 2.35, and now i manually updated it to 2.36, why is it 2.33?

On a whim I deleted all of the chromedriver executables from ‘vendor/laravel/dusk/bin’.

The tests ran… same error… but they ran and chrome opened… wtf.

Turns out there is a bad thing that can happen. The chromedriver process can get stuck running, and Dusk will just use it instead of launching a new process.

On a mac, open up Activity Monitor and kill the one or more ‘chromedriver-mac’ processes, and then it will start using the executable shipped with Laravel Dusk.

submitted by /u/cat5inthecradle
[link] [comments]

from Laravel Questions and Answers https://laravelquestions.com/rlaravel/getting-strange-failures-in-dusk-and-wrong-chromedriver-version-printed-solution/
via Lzo Media