Skip to content

Chrome Driver Update

The browser driver must remain synchronized with the current version of Google Chrome to ensure stable automation. This activity covers identifying the correct version, navigating the appropriate download portal based on version thresholds, and the manual or automated replacement process.

Configuration Parameters

Field Description Requirement
Chrome Version The current build version of the installed Google Chrome browser. Required
Operating System The target platform (Windows, Linux, or Mac) for the driver. Required
Worker Path The local directory where the Robusta Worker driver is located. Required
CLI Method Automated retrieval using the "Chrome for Testing" command-line interface. Optional

[^1]: Required fields must be configured for the activity to execute successfully.

Action Types & Examples

Version Matching

Aligning the browser major version with the corresponding driver binary. - Format: string (Major.Minor.Build.Patch) - Example Result: "122.0.6261.129"

Automated Update (CLI)

Using command-line tools to fetch the latest stable driver version. - Format: string (Command Line) - Example Result: "npx @puppeteer/browsers install chromedriver@latest"

Implementation Examples

Field Setup - Browser Check: Navigate to chrome://settings/help to find the current version. - Worker Directory: C:\RobustaWorkerCE\driver

Execution Parameters - Process Name: chromedriver.exe (Must be terminated before replacement). - CLI Command: npx @puppeteer/browsers install chromedriver@122

Google has changed the distribution method for Chrome Driver starting with version 115. Use the logic below to determine the correct download source:

1. Legacy Versions (v114 and Below)

For older versions, the link follows a predictable pattern based on the major version. - Base URL: https://chromedriver.chromium.org/downloads - Structure: https://chromedriver.storage.googleapis.com/[Full_Version]/chromedriver_win32.zip

2. Modern Versions (v115 and Above)

Modern versions use the Chrome for Testing (CfT) dashboard. Links are now JSON-based or can be accessed via the dashboard. - Dashboard: https://googlechromelabs.github.io/chrome-for-testing/ - Link Structure: https://storage.googleapis.com/chrome-for-testing-public/[Version]/win64/chromedriver-win64.zip

Technical Notes

Termination Requirement: You must close all active chromedriver.exe instances via Task Manager or taskkill /F /IM chromedriver.exe /T before attempting to replace the file.

Auto-Selection: For versions 115