Run Under ANT with macOS Catalina
If you upgrade to macOS Catalina (version 10.5 or newer versions), you may experience pop up messages when attempting to use Provar Run Under ANT.
To resolve these issues, you can use the following instructions.
You can also refer to the following support articles to learn more about using Provar with Apache Ant:
- Apache Ant, Java JDK and environment variables
- Apache Ant: Generating a build file
- Apache Ant Task Parameters
- Ant licensing
- Proxy execution
Configure Java
Step 1: Download Java Development Kit (JDK) for macOS Catalina and install it on your machine using the prompted instructions.
Step 2: Navigate to the user home location of the computer where Provar is installed.
Step 3: Find the .bash_profile. The .bash_profile may be hidden. If so, use command+shift+. to make hidden files visible.
Note: The command above does include a period after the second plus sign.
Step 4: If you still do not see the .bash_profile, use the following command within the terminal:
touch .bash_profile
Step 5: Right-click on the .bash_profile file and select Open With > TextEdit
Step 6: Add the following command:
export JAVA_HOME=$(/usr/libexec/java_home)
Step 7: Export JAVA_HOME to PATH with the following command:
export PATH=$PATH::$JAVA_HOME/bin
Step 8: Restart your machine.
Step 9: Type the following command:
java -version
Note: It should now display the JDK version information. The subversion may be different than the screenshot below.
Configure Apache Ant
Step 1: Start by downloading and installing Apache Ant.
Step 2: Once the file has been downloaded, copy it to your preferred location.
Open the terminal and navigate to the location where you copied the downloaded file. You can now use the following command to extract the file.
$ tar vxf apache-ant-1.10.9-bin.tar.gz
Step 3: Navigate to the user home location of your computer.
Step 4: Right-click on .bash_profile and select Open With > TextEdit
Step 5: Add the following commands to change the path of Apache Ant:
export JAVA_HOME=$(/usr/libexec/java_home)
export ANT_HOME=/Users/sudarshan.singh/Ant/apache-ant-1.10.9
export PATH=$PATH:$ANT_HOME/bin:$JAVA_HOME/bin
Step 6: Restart your machine.
Step 7: Open the terminal and navigate to Applications.
Step 8: Enter the following command in the terminal to open Provar:
open Provar.app
Step 9: Right-click on any test case and select RunUnderAnt. A dialog box will open to configure the build file and run your test cases.
- 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