‍

ATS will retrieve the correct driver version based on the browser version retrieved from the test. Based on the browser version, ATS will automatically download the correct driver version. There's no need to configure versions manually.

‍

Why does Agilitest needs Web drivers?

Agilitest is a software solution installed on your computer and regularly updated at launch.

In fact, without any additional configuration, Agilitest currently supports 5 browsers:

• Chrome
• Firefox
• MSEdge
• Brave

‍

Agilitest’s philosophy is to provide support as quickly as possible for the latest browser versions, and that's why web drivers are used to communicate with browsers. It can allows a very fast support as soon as the Selenium drivers we rely on are updated to these latest versions.

As a result, the Agilitest update will bring with it the latest driver version and drive the latest browser version, and generally you don't have to do anything because :

• If you update your browser, this should have no impact on the operation.
• If you don't update it, well, it's often possible for the latest driver to provide backward compatibility with previous browser versions, and in most cases this works out fine.

‍

Configure a specific version of a Driver

Adding new browser versions to Agilitest requires editor configuration in .atsProperties file

To configure a new browser, insert the following lines in your .atsProperties file:

<browser>
<name>chromium</name>
<driver>chromiumdriver</driver>
<path>D:\tools\chromium\chrome.exe</path>
</browser>

‍

The name badge lets you name the browser as it will be printed in Agilitest. A certain number of names are reserved as we adapt to the specificities of each browser: chrome, firefox, etc... You will therefore only be able to modify the driver and executable path for a browser already known to Agilitest.

The driver tag tells Agilitest the name of the .exe driver to load, which is located in the directory user/.actiontestscript/drivers/directory.

‍

You can access all web driver versions by system via this link: https://actiontestscript.com/releases/ats-drivers/

‍

The path tag indicates the path to the browser executable.

For example, if you want to use Firefox 60 ESR, the procedure is as follows:

• Download and install Firefox 60 ESR in a different directory from your Firefox installation.
• Complete the following lines in your .atsProperties file:

<browser>
<name>firefox</name>
<path>D:\tools\firefox60ESR\firefox.exe</path>
</browser>

‍

In the case of Firefox, the driver used should be compatible with the latest version and the ESR version, so there's no need to add a driver change.

To specify the MSEdge path, you can use the following lines:

<browser>
<name>msedge</name>
<path>C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe</path>
</browser>

‍

Related error message:

‍

To correct this error, you simply have to configure the ATS configuration file manually.

This can be accessed directly from the editor via the "Settings" menu in the top right-hand corner of the editor.

Then click on the "Edit configuration" button

‍

The file will be automatically opened with your default file editor:

All you need to do is define the path specifically set up on your system to access the executions files of the target browsers.

‍