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 ChromeDriver 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!
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.
Steps for Test Builder to work correctly
- Contact your system administrator to verify that the Provar Chrome extension has been white-listed.
- 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.
- 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.
- Go to the location where Provar is installed (C:Program FilesProvar on Windows).
- 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
- Go to your Provar Workspace folder (Usually USER_HOME%/Provar/Workspaces/PROJECT_NAME/).
- Delete .chromeProfiles folder from this directory (may require admin privileges).
- Launch Provar as an administrator (this may require administrator approval or intervention) and open any test case in the Test Builder.
- Open a new tab in Chrome and 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.
- Close this window, the Test Builder, and the Provar desktop.
- Go to Provar’s workspace folder (same as step 5)/.chromeProfiles.
- Copy the profile0 folder and paste it into this folder for however many additional profile folders are present. Override each profile folder with profile0 by renaming the copies profile1, profile2, etc.
- Launch Provar (not as the system administrator) and open this same workspace.
- Open any test case using Test Builder, and you should see the Provar extension icon at the top right of the Chrome browser.
- Provar Automation
- 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 Automation
- API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- 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
- Japanese Language Support
- Override Auto-Retry for Test Step
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Automation
- 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 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
- Provar Manager
- How to Use Provar Manager
- Provar Manager Setup
- Provar Manager Integrations
- Release Management
- Test Management
- Test Operations
- Provar Manager and Provar Automation
- Setting Up a Connection to Provar Manager
- Object Mapping Between Automation and Manager
- How to Upload Test Plans, Test Plan Folders, Test Plan Instances, and Test Cases
- Provar Manager Filters
- Uploading Callable Test Cases in Provar Manager
- Uploading Test Steps in Provar Manager
- How to Know if a File in Automation is Linked in Test Manager
- Test Execution Reporting
- Metadata Coverage with Manager
- Provar Grid
- DevOps
- 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
- Masking Provar Credentials on CI
- Salesforce Testing
- Best Practices
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- 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
- Troubleshooting
- How to Use Keytool Command for Importing Certificates
- Browsers
- Configurations and Permissions
- Connections
- DevOps
- Error Messages
- Provar Manager 3.0 Install Error Resolution
- Provar Manager Test Case Upload Resolution
- Administrator has Blocked Access to Client
- JavascriptException: Javascript Error
- macOS Big Sur Upgrade
- 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, Installation and Firewalls
- Memory
- Test Builder and Test Cases
- Release Notes