sbtqa/chromedriver-bin

tba

chromedriver-bin's Issues

Chrome 116

После изменений политики выпуска chromedriver

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), look up the Chrome binary’s MAJOR.MINOR.BUILD version in the latest-patch-versions-per-build JSON endpoints to find the corresponding ChromeDriver version.

Alternatively, you can use the LATEST_RELEASE_ endpoints at the new location.

Необходим механизм автоматической загрузки драйверов из новых истоников.

Either upload beta chromedriver versions ahead of time, or build an automated way to update the version

For instance, today chrome went from v101 to v102, and the 102 artifact wasn't here. So we have to notice our broken builds, do an emergency PR here, and then move to the v102. However v103 is already up on chrome already. If we uploaded both the 102 (stable) and 103 (beta) versions, then the versions would exist ahead of time, and chrome go-live day for the next major version won't be such a fire drill.

Alternatively, some process might be developed to do this automatically, though I understand that this maybe a harder task.