{"id":69775,"date":"2019-12-31T15:32:05","date_gmt":"2019-12-31T10:02:05","guid":{"rendered":"https:\/\/www.vskills.in\/certification\/tutorial\/?p=69775"},"modified":"2024-04-12T14:21:56","modified_gmt":"2024-04-12T08:51:56","slug":"appium-chromedriver","status":"publish","type":"page","link":"https:\/\/www.vskills.in\/certification\/tutorial\/appium-chromedriver\/","title":{"rendered":"Appium-Chromedriver"},"content":{"rendered":"\n

Go back to tutorial<\/a><\/p>\n\n\n

Appium-Chromedriver<\/strong><\/h1>\n
\"appium-chromedriver\"
appium-chromedriver<\/figcaption><\/figure>\n

Appium supports automating Android web pages in Chrome as well as for the built-in Browser. Also, Appium support the hybrid apps which are Chrome-backed. This is done by managing a Chromedriver instance and proxying commands to it when necessary. Further, it comes bundled with the latest version of Chromedriver, installed through the npm package appium-chromedriver (Github: appium-chromedriver).<\/p>\n

But unfortunately, with each update to Chromedriver there is an increase in the minimum supported version of Chrome. Therefore, the older devices are often unable to be automate with the bundled version.Further, you can also configure Appium to use a particular Chromedriver version, either at install time, or by either passing the –chromedriver_version config property.<\/p>\n

Also, a version can be specified at runtime, by specifying the –chromedriver-executable server flag, along with the full path to the Chromedriver executable which was manually downloaded.<\/p>\n

How to automate discovery of compatible Chromedriver<\/strong><\/h3>\n

From the Appium it has been always easy to pick the correct Chromedriver for the version of Chrome under test. Moreover, Appium only comes bundled with the Chromedriver most recently released at the time of the Appium version’s release. Further, more Chromedriver versions can be downloaded and either placed inside the Appium installation or in a custom location, indicated to Appium with the chromedriverExecutableDir desired capability. This capability is the absolute path to the directory in which you have placed one or more Chromedriver executables.<\/p>\n

As well, since new versions of Chromedriver may be available that were not when an Appium version was released, a custom mapping of Chromedrivers to the minimum Chrome version they support can be given to Appium through the chromedriverChromeMappingFile desired capability. This should be the absolute path to a file with the mapping in it.<\/p>\n

How to install network issues?<\/strong><\/h3>\n

At the time of installation of Appium , it requires you to download Chromedriver. Therefore, there is a possibility that there could be network problems that make the install fail.<\/p>\n