Updating Automation on Windows
Last Modified:
This page describes how to update Provar Automation to a new version.
If you do not yet have Automation installed on your machine, please refer to the Installing Automation on Windows page.
Uninstall the Old Version
Start your Provar update with a clean slate by uninstalling the current version.
Go to the installation location and run the uninstall.exe file.
You may be prompted to all this program to make changes. Select Yes to continue.
The Provar Uninstall wizard will walk you through the step. Click Next > to get started.
The location cannot be edited, so click Uninstall when you’re ready to proceed.
The Provar Uninstall wizard will do the work for you. It may take a moment, but the top message will state that Provar has been successfully uninstalled. Click Close to continue.
Provar will confirm that completed uninstallation. Click OK to close the wizard.
Download the New Version
Log into your Provar Success Portal. You can find the link on the far top right of the Provar.com homepage.
Find the newest Provar Releases under the Product menu.
This will take you to a table of releases currently available. You can change the List View to Current Stable Release or sort by Release Date to find the newest release with ease.
Clicking on the desired release will take you to a details page with various versions of the file available.
Make sure to select the correct version for your needs and operating system. If you don’t see it in the release download box, select “View All” to see the full available list.
Installing the New Version
The downloaded file is an executable file.
To start the installation wizard, run the file from its downloaded location.
You may be prompted to make changes.
Click Yes to continue.
Once the window pops up, click
Next >
to get started.
You must agree to the License Agreement to proceed to installation.
Select I Agree to proceed.
After accepting the license agreement, you will be prompted to choose an installation location. Windows will default to C:\Program Files\Provar.
You can browse for a new location or accept the default, then press the Install button.
Installation may take a moment. Once complete, click Next > to continue.
Installation may take a moment.
Once complete, click Next > to continue.
You did it!
Select the checkboxes to match your preference and click Finish.
Selecting a Workspace
It is recommended to leave the checkbox “Use this as the default, and do not ask again” unticked. This will allow you to switch your workspace to have multiple Test Projects. If you did not check this box, upon launching Provar Automation you will be prompted to select your Workspace. Select a recent workspace or create a new one.
NOTE: The default location (C:\Users\<username>\Provar) is where Provar stores your license and other information. This is not the same as the installation location.
Your workspace will be the home of your Test Project. It is not necessary to keep your workspace in this same location, but it is considered best practice to select a workspace location away from your chosen installation location.
The Launcher will load your most recent workspace in the “Workspace” field. You can find other Workspaces you may be using under “Recent Workspaces”.
Click Launch to start your workspace when you’re ready and pick up right where you left off.
- 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
- Improve Your Metadata Performance
- Java 21 Upgrade
- Salesforce Connection Best Practices
- 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
- Installing Provar After Upgrading to macOS Catalina
- 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