Disabling automatic chromedriver download

[ElSnoMan]

Aloha Carlos!

First of all, thank you for a fantastic product, we love it here!
Is there any way to avoid automatically downloading the chrome driver when running the tests?

We have an issue in a machine where we have the driver installed manually since the machine can not be exposed to the internet, but Pyleniumio still tries to download the version. The location of the cache is unknow to us, so we can’t manually put the executable there. Any ideas?

Mahalo!

Andres

[ElSnoMan]

Hello Andres!

💡 Pylenium uses WebDriverManager to automatically manage the driver binaries given the browser(s) installed on the machine.

For example, if your machine has Google Chrome version 93.0.4577.63 installed, then WebDriverManager will look within ~/.wdm folder for a chromedriver executable that matches that version. If one doesn't exist, then it will download it and use that - all automatically.

💡 If you want to use a local driver executable instead, then set the local_path field within pylenium.json

For example, if I downloaded the chromedriver and left it in my /Downloads folder, my pylenium.json would look like this (observe the driver.local_path field):

{
  "driver": {
    "browser": "chrome",
    "remote_url": "",
    "wait_time": 10,
    "page_load_wait_time": 0,
    "options": [],
    "capabilities": {},
    "version": "latest",
    "experimental_options": null,
    "extension_paths": [],
    "webdriver_kwargs": {},
    "local_path": "/Users/carlos/Downloads/chromedriver"
  },
  "logging": {
    "screenshots_on": true
  },
  "viewport": {
    "maximize": true,
    "width": 1440,
    "height": 900,
    "orientation": "portrait"
  }
}

Now all of the tests in my suite would run against the local chromedriver 🎉