How to Skip Chromedriver Version Check in SeleniumBase

[webmoskal]

I would like to know if there is a way to skip or bypass this check during test execution.

[mdmintz]

--driver-version="keep" / driver_version="keep"

SeleniumBase/seleniumbase/plugins/sb_manager.py

Line 77 in 3bb813f

driver_version=None, # Set the chromedriver or uc_driver version to use.

See the docs on specifying the driver version.

If you're keeping your driver version, then SeleniumBase won't try to download a new one.
(Unless you don't have any driver at all.) Compatibility is not guaranteed.

[mdmintz]

The error message explained: "The chromedriver version (121.0.6167.85) detected in PATH at /usr/local/bin/chromedriver might not be compatible with the detected chrome version (126.0.6478.126); currently, chromedriver 126.0.6478.126 is recommended for chrome 126.*, so it is advised to delete the driver in PATH and retry"

Also, upgrade to a newer version of SeleniumBase. And if selecting a specific driver version, use only the major version number (eg. 126 instead of 126.0.6478.126). The driver version doesn't always match the browser version.

[webmoskal]

I understand that the version might not be compatible. What I'm trying to avoid is for the library to download a new version. I've upgraded to 4.28.3. Even when passing --driver-version="121" or --driver-version=121, it still attempts to download Chromedriver version 126.

[mdmintz]

--driver-version is the pytest way for BaseCase tests.
If using SB(), use SB(driver_version="keep")

[webmoskal]

I really appreciate your prompt responses. Please forgive my ignorance. I've been using @pytest.mark.usefixtures("sb"). I've also tried using the following with --driver-version=121 through CLI and BaseCase:

from seleniumbase import BaseCase
BaseCase.main(__name__, __file__)

still attempts to download.

[mdmintz]

If the driver didn't exist or wasn't compatible, then it probably would try to download a new driver as an alternative to failing outright.