Skip to content

Support for chrome-for-testing#1

Open
laggykiller wants to merge 1 commit intosaizk:mainfrom
laggykiller:main
Open

Support for chrome-for-testing#1
laggykiller wants to merge 1 commit intosaizk:mainfrom
laggykiller:main

Conversation

@laggykiller
Copy link

Latest versions of chrome has to be downloaded via chrome-for-testing: https://chromedriver.chromium.org/downloads

Latest stable release of chrome could not be downloaded from https://chromedriver.chromium.org/ and not listed (e.g. https://chromedriver.storage.googleapis.com/LATEST_RELEASE_115)

Instead, stable and newer releases should be checked from chrome-for-testing API such as https://googlechromelabs.github.io/chrome-for-testing/known-good-versions-with-downloads.json (See: https://github.com/GoogleChromeLabs/chrome-for-testing#json-api-endpoints), then downloaded from url that looks like https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/115.0.5790.170/win64/chrome-win64.zip

Note that this PR is a bit messy (e.g. adding '-chrome-for-testing' to the end of version number to mark that the version of chrome has to be downloaded from chrome-for-testing). but it works. See if you want to change the structure of your code such that my dirty hack is not needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant