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 mentioned below to fix this issue.
This issue occurs more commonly in work environments with advanced network security restrictions. To fix this issue, you will need to manually download the most up-to-date version of the Provar extension. Here’s how!
How to get the Extension ID?
To get the Extension ID, please see the Chrome web store link for the given Provar release. 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 there are no ChromeDrivers 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, click the “more” icon in the upper-right (three vertical dots), click More Tools, Extensions and then select 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 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 given Provar release, which can be found in the Provar Success Portal.
- Close this window, the Test Builder and Provar desktop.
- Go to Provar’s workspace folder (same as step 5)/.chromeProfiles.
- Copy the profile0 folder and paste it in 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.
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- 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
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- 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 Provar Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Provar 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 Provar 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
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Dynamic Forms
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Performance Best Practices
- Testing best practices
- Troubleshooting
- Browsers
- Configurations and permissions
- Connections
- DevOps
- Error messages
- 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
- Update to Opportunity field validation behaviour
- Licensing, installation and firewalls
- Memory
- Test Builder and test cases
- Release notes