[🐛 Bug]: Chromedriver binary override no longer works about webdriverio

[christian-bromann]

@NyCodeGHG thanks for raising the issue.

Let's investigate this one: let's set a higher log level for Chromedriver via wdio:chromedriverOptions. If this doesn't do anything, let's run the driver manually and see why it doesn't start any browser.

This seems like a hickup in Chromedriver and doesn't necessarily be related to WebdriverIO.

[NyCodeGHG]

Note: I pressed Ctrl+C after webdriverio started downloading chrome.
The problem is that webdriverio ignores the provided chromedriver binary and instead downloads its own

[christian-bromann]

Can you provide a reproducible example?

[NyCodeGHG]

# all of this tested in a fedora container, should also work on docker
podman run --rm -it registry.fedoraproject.org/fedora

dnf install chromedriver nodejs -y
npm install -g @wdio/cli
mkdir /wdio
cd /wdio
npm init -y
# let it create a new project, otherwise leave everything on defaults
wdio
export CHROMEDRIVER_PATH=/usr/bin/chromedriver
# here it downloads chromedriver instead of using $CHROMEDRIVER_PATH
wdio run wdio.conf.js

[wdio-bot]

Thanks for reporting!

We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!

[wdio-bot]

Thanks for reporting!

We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!