Test Builder Not Working Correctly
If you’ve recently installed Provar and are having trouble using the Test Builder (e.g., after right-clicking on objects, the Add to Test Case option doesn’t display), it can be related to a Chrome browser compatibility issue.
You can quickly check to see if your Chrome Extension is causing the issue by looking at the top right-hand corner of your Chrome browser. If you don’t see a small Provar icon (which indicates that you have the Provar extension working correctly), you can take the steps below to fix this issue.
This issue occurs more commonly in work environments with advanced network security restrictions. To fix this issue, you must manually download the most up-to-date version of the Provar extension. Here’s how!
Before starting, double check that the Provar Chrome extension has been white-listed.
You may need to contact your system administrator for assistance.
How Do I Get the Extension ID?
Please see the Chrome web store link for the Provar release to get the Extension ID. This link is available against the relevant Provar release in the Provar Success Portal. The Extension ID is a 32-character string at the end of the Chrome web store link.

Above: View of the Extension ID in the Chrome web store link of a Provar release.
Option 1
Load from Chrome Store
1. Exit the Provar desktop application:
Ensure that no Chrome drivers are running on your machine. To verify, open the Task Manager/Activity Monitor and end tasks associated with chromedriver.exe.
2. Delete the Provar extension from all Chrome browsers on your local machine:
You can do this by opening Chrome, clicking the “more” icon in the upper-right (three vertical dots), clicking More Tools, Extensions, and then selecting Remove.
3. Navigate to the Provar Installation Folder:
Open provar.ini file in a text editor with administrator privileges.
Add this line to the end of the provar.ini file in the Provar installation directory:
-Dcom.provar.tooling.chrome.extensionId=ahcaopmmbcfojipcghpceejhghaepadp
You can skip step-3 if you don’t have administrator privileges.
4. Go to your Provar Workspace folder:
This is usually located at %USER_HOME%/Provar/Workspaces/
Delete .chromeProfiles folder from this directory (may require admin privileges). You’ll need this folder again, so leave it open.
5. Launch Provar Automation:
Run any test case with Test Builder.
6. Open a new tab in Chrome:
Add the latest Provar extension in the browser. You can download this from the Chrome Web Store link for the Provar release, which can be found in the Provar Success Portal.
Stop the session from Test Builder.
7. Return to the Workspace/.chromeProfiles folder:
Go back to the folder from step 4.
Copy the profile0 folder and paste it into this folder. Repeat this to have a minimum of 5 additional profile folders and override each profile folder with profile0 by renaming the copies (profile1, profile2, etc).
8. Relaunch Provar:
Open this same workspace/project. Run any test case using Test Builder, and you should see the Provar extension icon at the top right of the Chrome browser. Right clicking on any page elements should provide an option to Add to Test Case.
Option 2
Load from Provar Installation Directory
1. Exit the Provar desktop application:
Ensure that no Chrome drivers are running on your machine. To verify, open the Task Manager/Activity Monitor and end tasks associated with chromedriver.exe.
2. Delete the Provar extension from all Chrome browsers on your local machine:
You can do this by opening Chrome, clicking the “more” icon in the upper-right (three vertical dots), clicking More Tools, Extensions, and then selecting Remove.
3. Navigate to the Provar Installation Folder:
Open provar.ini file in a text editor with administrator privileges.
Add this line to the end of the provar.ini file in the Provar installation directory where the Extension ID matches the value mentioned above.
-Dcom.provar.tooling.chrome.extensionId=ahcaopmmbcfojipcghpceejhghaepadp
You can skip step-3 if you don’t have administrator privileges.
4. Go to your Provar Workspace folder:
This is usually located at %USER_HOME%/Provar/<Workspace_name>/
Delete .chromeProfiles folder from this directory (may require admin privileges). You’ll need this folder again, so leave it open.
5. Launch Provar Automation:
Trigger Chrome launch via Test Builder with any Provar test case and wait for the browser window to open.
6. Access Chrome Extensions Page:
In the opened Chrome browser, go to: chrome://extensions/
7. Enable Developer Mode:
Toggle the Developer mode switch in the top-right corner.

8. Load Unpacked Extension:
Click the “Load unpacked” button.
9. Select Extension Folder:
In the file dialog, navigate to the plugin path in your installation folder,
\provar\plugins\com.provar.chrome.seleniumExtension_*\target\build\app\ where the * is the version number.
Click “Select Folder” (choose the app folder directly). The extension should now be installed.
Stop your Test Builder session.
10. Re-run Your Test Case:
Re-execute the test case.
If a Chrome alert appears (e.g., “Load of unpacked extension is disabled by your Administrator”), click “OK” to continue.
- Home
- System Requirements
- Browser and Driver Recommendations
- Installing Provar Automation
- Updating Provar Automation
- Licensing Provar
- Granting Org Permissions to Provar Automation
- Optimizing Org and Connection Metadata Processing in Provar
- Using Provar
- Understanding Provar’s Use of AI Service for Test Automation
- Provar Automation
- Creating a New Test Project
- Import Test Project from a File
- Import Test Project from a Remote Repository
- Import Test Project from Local Repository
- Commit a Local Test Project to Source Control
- Salesforce API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- Creating Test Cases
- Custom Table Mapping
- Functions
- Debugging Tests
- Defining a Namespace Prefix on a Connection
- Defining Proxy Settings
- Environment Management
- Exporting Test Projects
- Exporting Test Cases into a PDF
- Japanese Language Support
- Override Auto-Retry for Test Step
- Customize Browser Driver Location
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Test Builder
- ProvarDX
- 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 – Chrome Headless
- 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
- Database Testing
- Document Testing
- Email Testing
- Email Testing in Automation
- Email Testing Examples
- Gmail Connection in Automation with App Password
- App Configuration for Microsoft Connection in MS Portal for OAuth 2.0
- OAuth 2.0 Microsoft Exchange Email Connection
- Support for Existing MS OAuth Email Connection
- OAuth 2.0 MS Graph Email Connection
- Create a Connection for Office 365 GCC High
- Mobile Testing
- OrchestraCMS Testing
- Salesforce CPQ Testing
- ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices Testing
- DevOps with V2
- Introduction to Provar 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
- 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
- Version Control
- Salesforce Testing
- Recommended Practices
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- Java 21 Upgrade
- Testing Best Practices
- Automation Planning
- Supported Testing Phases
- Provar Naming Standards
- Test Case Design
- Create records via API
- Avoid using static values
- Abort Unused Test Sessions/Runs
- Avoid Metadata performance issues
- Increase auto-retry waits for steps using a global variable
- Create different page objects for different pages
- The Best Ways to Change Callable Test Case Locations
- Working with the .testProject file and .secrets file
- Best practices for the .provarCaches folder
- Best practices for .pageObject files
- Testing Best Practices
- Troubleshooting with V2
- How to Use Keytool Command for Importing Certificates
- Browsers
- Configurations and Permissions
- Add Permissions to Edit Provar.ini File
- Configure Provar UI in High Resolution
- Enable Prompt to Choose Workspace
- Increase System Memory for Provar
- Refresh Org Cache Manually
- Show Hidden Provar Files on Mac
- Java Version Mismatch Error
- Unable to create test cases, test suites, etc… from the Test Project Navigation sidebar
- Connections
- DevOps with V2
- Error Messages
- Provar Manager 3.0 Install Error Resolution
- Provar Manager Test Case Upload Resolution
- Administrator has Blocked Access to Client
- JavascriptException: Javascript Error
- Resolving Failed to Create ChromeDriver Error
- Resolving Jenkins License Missing Error
- Resolving Metadata Timeout Errors
- Test Execution Fails – Firefox Not Installed
- Selenium 4 Upgrade
- Licensing and Installation
- Memory
- Test Builder
- Release Notes