Chromedriver v115+ unsupported downloads

[JoshCrozier]

Expected Behavior

The ability to run selenium-standalone against version of Chromedriver v115+.

There were recently updates here from the official source: https://chromedriver.chromium.org/downloads

• If you are using Chrome version 115 or newer, please consult the Chrome for Testing availability dashboard. This page provides convenient JSON endpoints for specific ChromeDriver version downloading.

• For older versions of Chrome, please see below for the version of ChromeDriver that supports it.

Current Behavior

Currently, only versions prior to v115 are supported.

When computing the download URL, /LATEST_RELEASE is appended (which is utilized for the previous download URL)

selenium-standalone/lib/compute-download-urls.js

Line 54 in 9fdcf44

await resolveLatestVersion(opts, 'chrome', opts.drivers.chrome.baseURL + '/LATEST_RELEASE');

Conditional logic needs to be added to look at the newly released API for v115+ and higher: https://googlechromelabs.github.io/chrome-for-testing/last-known-good-versions-with-downloads.json

For versions 115 and newer
Starting with M115 the ChromeDriver release process is integrated with that of Chrome. The latest Chrome + ChromeDriver releases per release channel (Stable, Beta, Dev, Canary) are available at the Chrome for Testing (CfT) availability dashboard. As a result, you might no longer have a need for version selection — you could choose any available CfT version and simply download the correspondingly-versioned ChromeDriver binary.

For automated version downloading one can use the convenient CfT JSON endpoints.

If you still have a need for version selection (e.g. to match a non-CfT Chrome binary with a compatible ChromeDriver binary), you might be interested in the latest-patch-versions-per-build JSON endpoints.

[christian-bromann]

@JoshCrozier thanks for raising the issue. We are in the process of deprecating this project as it is no longer useful for the WebdriverIO project due to this effort: webdriverio/webdriverio#10767. We hope to be able to ship it by the end of this week. If you are using this package without WebdriverIO, I recommend to switch to an alternative package that allows you to use Chromedriver, e.g. this one. If you can provide a patch that resolves the problem we are committed to merge and release it.

[tehhowch]

@christian-bromann is that effort, wherein WebdriverIO will manage the drivers, being made for all officially supported versions of WebdriverIO, i.e. both 7 and 8? Or will consumers that use v7 and selenium-standalone be forced to abandon testing against valid Chrome versions despite being within the LTS support window?

[christian-bromann]

These changes will not be back ported to WebdriverIO v7, at least I am not planning to do it myself as I don't have the resources for it. I am happy to merge any contributions that come up with a fix for this.

That said, I can only urge to update to WebdriverIO v8. There is no reason for someone to stay on v7 and we have done all possible things to make the transition as easy as updating the version number. If someone has complications upgrading to v8 should raise an issue and we can work this out.

[Jasonizl]

As in opening a issue, do you mean in this project or in the webdriverIO project @christian-bromann?
Me and my team are also struggling to update from v7 to v8 because of breaking changes with how scrolling works for example.

[christian-bromann]

As in opening a issue

Yes, ideally with a reproducible example.

[udarrr]

here is fix for that #814

[christian-bromann]

Thanks @udarrr for all your work. Released as v9.0.0.