Use the URL created in the last step to retrieve a small file containing the version of ChromeDriver to use. Take the Chrome version number, remove the last part, and append the result to URL "". Here are the steps to select the version of ChromeDriver to download:įirst, find out which version of Chrome you are using. These patches may or may not coincide with updates to Chrome. īefore a new major version of Chrome goes to Beta, a matching version of ChromeDriver will be released.Īfter the initial release of a new major version, we will release patches as needed. 20 supports all Chrome versions that start with. See for more details.Įach version of ChromeDriver supports Chrome with matching major, minor, and build version numbers. Specifically:ĬhromeDriver uses the same version number scheme as Chrome. Which version to select depends on the version of Chrome you are using it with. We maintain multiple versions of ChromeDriver. If there is no entry for the version yet, fall back to the latest-versions-per-milestone JSON endpoint instead.Īlternatively, you can use the LATEST_RELEASE_ endpoints at the new location. to match a non-CfT Chrome binary with a compatible ChromeDriver binary), look up the Chrome binary’s version in the latest-patch-versions-per-build JSON endpoints to find the corresponding ChromeDriver version. If you still have a need for version selection (e.g. 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.įor automated version downloading one can use the convenient CfT JSON endpoints. The latest Chrome + ChromeDriver releases per release channel (Stable, Beta, Dev, Canary) are available at the Chrome for Testing (CfT) availability dashboard. Starting with M115 the ChromeDriver release process is integrated with that of Chrome.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |