Installing Provar After Upgrading to MacOS Catalina
You may experience an issue when trying to run the Provar installer after upgrading to macOS Catalina. Specifically, you may encounter the following error message when installing Provar.
Provar_2.0.2.017_macos_signed.pkg can’t be opened because Apple cannot check it for malicious software. This software needs to be updated. Contact the developer for more information.
Why am I experiencing this issue?
Apple introduced a new feature in macOS Catalina that prevents software (downloaded from the internet) from running unless Apple has approved it. This security feature is designed to prevent users from accidentally downloading malware.
What is Provar doing to fix this?
We are actively working to get the Provar installer approved by Apple. Until this issue is resolved, a manual workaround is required.
How can I use Provar in the meantime?
You can use the following steps to install the latest version of Provar.
Step 1: Download the Provar installer and note where the installer was downloaded on your computer.
Step 2: Open up a terminal. This can be done by opening the Applications folder in the Finder. Open the Utilities folder and double-click the Terminal application.
Step 3: If the default download folder was used in step one, paste the following into Terminal.
cd Downloads; xattr -d com.apple.quarantine [Provar installer file]
Where [Provar installer file] = the exact name of the installer file you are using, for example:
cd Downloads; xattr -d com.apple.quarantine Provar_2.0.2.020_macos_signed.pkg
Please note, you will need to modify the command listed above if you downloaded the Provar installer files into a folder other than Downloads. Specifically, replace Downloads with the folder name where the Provar file is located.
Step 4: Paste the following command into Terminal to run the installer.
open [Provar installer file]
Where [Provar installer file] = the exact name of the installer file you are using, for example:
open Provar_2.0.2.020_macos_signed.pkg
That’s it! You can then follow the standard steps to install Provar as usual.
- 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 Automation
- 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
- Provar Manager
- Provar Manager Setup and User Guide
- Installing Provar Manager
- Configuring Provar Manager
- How to Use Provar Manager
- Managing Your Testing Life Cycle
- Provar Manager Test Execution
- Test Executions and Defect Management
- Provar Manager Test Coverage
- How to Integrate Provar Manager
- 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
- Provar Manager Plugins
- Uploading Existing Manual Test Cases to Provar Manager with DataLoader.Io
- Provar Grid
- 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
- Salesforce Testing
- Best Practices
- Troubleshooting
- Release Notes