Setting Apache Ant environment variables
Introduction to Apache Ant
Apache Ant or ANT is a command-line tool for driving software processes. In Provar, ANT can be used to run a Provar test suite via the command line or using a Continuous Integration (CI) server such as Jenkins. This is achieved by configuring and executing Provar Compile and Run tasks in ANT, using a build file.
Before a build file can be generated, first make sure that you have Apache Ant and Java JDK installed, and that their environment variables have been correctly configured. Follow the steps below to complete these actions.
Installing Apache Ant
Start by downloading and installing Apache Ant.
To download Apache Ant, visit this page. (In case this link is not available, visit the Apache website, go to the downloads section, select a mirror site directory, then navigate to ant/ and then binaries/). Choose your preferred version (1.8 or later), then download the version file ending in bin.zip, e.g. apache-ant-1.9.4-bin.zip.
Note: Earlier versions of Provar may work but have not been tested.
Once the file has been downloaded, extract it to your preferred location. Take a note of the directory, e.g. C:\apache-ant-1.10.7 or /Users/hetty.bw/apache-ant-1.10.7, as you will need to add this information to an environment variable (see below).
Setting the ANT_HOME Environment Variable On Windows
Step 1: Open the System Control panel, then select the Advanced tab.
Step 2: Click the Environment Variables button. The following dialog will appear.
Step 3: Click the New button.
Step 4: In Variable name, enter ANT_HOME, and in Variable value, enter the directory to which Apache Ant was extracted previously, e.g. C:\apache-ant-1.9.4.
Step 5: Then click the OK button.
Step 6: Go to the Path variable within the System variables section and click on the Edit button.
Step 7: Click the New button and type %ANT_HOME%\bin in the row at the bottom of the list.
Step 8: Click OK and restart your system.
Setting the ANT_HOME Environment Variable on a Mac
Step 1: Navigate to your User Home folder. The fastest way to do this is using Shift + Command + H, or you can open Finder, select Go in the menubar and then click Home.
Step 2: Navigate to Library > LaunchAgents folder. If you can’t see this folder, your computer may not be showing hidden files. To show hidden files, open Terminal and paste the following command:
defaults write com.apple.finder AppleShowAllFiles YES
Step 3: Then press the Return key. Then right-click on the Finder icon in the dock and select Relaunch. (If you do not see this option, restart your computer to achieve the same result.) Navigate back to User Home, then go to Library > LaunchAgents folder.
If there is no existing environment.plist file
Create a new file in that folder called environment.plist. This can be done by opening a text editor, saving the file as environment.plist (ensuring no other filetype suffix is added) and adding this into the LaunchAgents folder.
You may not be able to save the file directly to the LaunchAgents folder, since this is a hidden folder. If this is the case, save the file to Desktop, then open Finder and move the file manually to the LaunchAgents folder.
In the new, empty file, add the contents below.
Make sure that you modify the contents by replacing /Users/ravindra/apache-ant-1.9.6 and /Users/ravindra/apache-ant-1.9.6/bin with the same filepath you recorded when installing Apache Ant (see above).
Note that the second entry (PATH) should have /bin added at the end of it, while the first entry (ANT_HOME) should not.
Paste the following into the empty file.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>my.startup</string> <key>ProgramArguments</key> <array> <string>sh</string> <string>-c</string> <string> launchctl setenv ANT_HOME /Users/hetty.bw/apache-ant-1.10.1 launchctl setenv PATH $PATH:/Users/hetty.bw/apache-ant-1.10.1/bin </string> </array> <key>RunAtLoad</key> <true/> </dict> </plist>
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reload Org Cache
- 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
- Test Palette introduction
- Control test steps
- List compare
- Read test step
- String test steps
- UI Test Steps
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Salesforce CPQ testing
- ServiceMax testing
- Skuid testing
- Vlocity testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for sending emails via the Provar Command Line Interface (CLI)
- Continuous integration
- Azure DevOps
- Running a Provar CI task in Azure DevOps
- 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
- Circle CI
- GitLab CI
- Travis CI
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team foundation server
- Version control
- Zephyr Cloud and Server (Beta)
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Service Cloud console testing
- Visualforce Testing
- Testing best practices
- Configurations and permissions
- Error messages
- Licensing, installation and firewalls
- Test Builder and test cases
- Release notes