Resolving failed to create ChromeDriver error
In some cases, you may experience compatibility issues when Google releases new versions of the Google Chrome browser. This can prevent your Automation tests from running correctly.
Users affected by this issue generally see a failed to create ChromeDriver error when attempting to execute test cases in any run mode, including via Apache Ant in conjunction with any continuous integration solution.
See the example error message below.
To resolve this issue, you should update your ChromeDriver version.
Disabling Auto-Update
Step 1: Disable Automation’s auto-update feature (ChromeDriver versioning) by entering the provar.ini file at the installed location. Typically, this is added at the end of the script.
-Dcom.provar.chromedriver.versioningSupported=false
Example (click to enlarge):
For Apache Ant execution, the user can use the following commands to set this variable:
For Windows Set ANT_OPTS to:
-Dcom.provar.chromedriver.versioningSupported=false
For Linux or Mac Export ANT_OPTS to:
-Dcom.provar.chromedriver.versioningSupported=false
Step 2: Delete any ChromeDriver folder inside the user home folder. {UserHome}/Provar/.chromeDriver.
Note: Ensure that there are no ChromeDriver processes running. Kill the processes if there are any.
Step 3: Execute the test case to launch the browser session.
What should I do if I don’t have permissions to update my provar.ini file?
Refer to this help page for an alternative way to override your ChromeDriver version using your project’s lib folder.
If you implement this solution and are still encountering difficulties, please get in touch with support@provartesting.com for additional help.
- Provar Automation
- Installing Provar Automation
- Updating Provar Automation
- Using Provar Automation
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- Functions
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Override auto-retry for Test Step
- Managing test steps
- Namespace org testing
- NitroX
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI license Check
- Reload Org Cache
- Reporting
- Running tests
- Searching Provar with find usages
- Secrets management and encryption
- Setup and teardown test cases
- Tags and Service Level Agreements (SLAs)
- Test cycles
- Test plans
- Testing browser options
- Tooltip testing
- Using the Test Palette
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript locator support
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- ProvarX™
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- DevOps
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines Using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team Foundation Server
- Version control
- Provar Automation trial guide and extensions
- Salesforce Testing
- Provar Manager
- Best Practices
- Troubleshooting
- Release Notes