Introduction

During a Hybrid Execution, Testsigma Agent running on your local machine communicates with the Web Browser installed on your machine using the selenium driver files specific to the respective browser.

When a major version update for the browser is released, an update to the driver might be needed as well.


Driver files for all the browser versions till date are included by default in the drivers archive file that you can download from the links given below:

Windows 32bit | 64bit

Mac 32bit | 64bit

Linux 32bit | 64bit


Download the drivers specific to your OS and place them in drivers folder along with the Apache Tomcat working directory.


Location of Driver files

Given below are the default drivers versions included in the drivers archive file(at the time of writing this article) and their organization in the filesystem.




Adding Drivers Manually

For newer releases of browser versions, we might need to add the updated driver versions manually.


When new browser versions are released, a newer driver version will be released on SeleniumHQ Downloads page.


And here are the direct links to WebDrivers of most popular Browsers:

Firefox - GeckoDriver(Hosted on Github)

Chrome - ChromeDriver(Hosted on Google Sites)

Microsoft Internet Explorer - InternetExplorerDriver

Microsoft Edge - Edge Driver

MacOS Safari - SafariDriver


We just need to download the file from there and place it in the directory for the respective browser after creating a new folder with the driver file version as its name.


For Example, let us assume that the installed version of Google Chrome browser is v56.

Assume that a new version, say v60 is released and a new driver version v2.35 is also released that is compatible with the new browser version.


We need to download the driver file for version 2.35, create a directory named '2.35' inside the 'googlechrome' directory within 'drivers' directory and place the driver file in the newly created folder. The driver file will have an exe extension for Windows and no extension for Linux/Mac.


Once that is done, we can start executing tests on the newest version of the corresponding Browser. You can follow the same procedure for all the other browsers as well.