Travis CI
This support article provides step-by-step instructions to execute Provar test cases in Travis CI. Travis CI is a hosted Continuous Integration (CI) service used to build and test software projects hosted at GitHub.
For customers who want to use Provar with the Travis CI Enterprise edition, the steps are broadly similar but since you will be hosting Travis CI on your own infrastructure, please Contact Us for assistance.
Prerequisites
- Provar ANT zip file.
- Provar project with at least one test case and the associated ANT build.xml file.
- Github account.
- The Provar project is pushed into a nominated Github repository for the above account.
- Provar Execution Only (or Floating) license key pushed into the .license folder of the Github repository.
Please only upload license keys on private repositories to avoid unlicensed usage by third parties. Unlicensed access will be tracked and can cause you to be locked out of Provar until a new license key is re-issued to you.
Steps to create an account in Travis CI
The following steps can be completed using a free Travis CI account. If you have an existing paid account simply log in and jump to step three.
- Go to the Travis CI website and click Sign Up.
- Click Authorize travis-ci to log in with your GitHub credentials, then enter your GitHub password. You’re actually on GitHub.com at this point. Travis CI never sees your login information.
- When you’ve logged in, click your picture to go to profile settings.
- Find the Provar project repository and turn on Travis CI for your repo.
Sometimes it takes several minutes to sync Travis CI and Github.
That’s it! You have now set up Travis CI to track changes in your Github repository.
Add a .travis.yml file to your repository
In order for Travis CI to build your project, you will need to add a .travis.yml configuration file to the root directory of your repository.
If a .travis.yml is not in your repository, or is not valid a YAML, Travis CI will ignore it.
Here is an example file:
language: java addons: chrome: stable before_script: - "export DISPLAY=:99.0" - "sh -e /etc/init.d/xvfb start" - sleep 5 # give xvfb some time to start cache: directories: - Provar_Home script: - curl -O https://download.provartesting.com/1.9.10/Provar_ANT_1.9.10.02.zip - unzip -o Provar_ANT_1.9.10.02.zip -d Provar_Home - rm Provar_ANT_1.9.10.02.zip - xvfb-run -a ant -f DemoProject/build.xml
First, we need to mention which language we want to use. So, it’s Java here for us. By default, Travis CI is going to execute our test cases on JAVA 8 which is the current Provar supported version.
As we need to execute our UI test cases on a browser, that is why the Chrome add on is included.
To execute test cases in headless manner, we also need to install xvfb, so before executing the actual test script section we are installing xvfb.
Caching of Provar_Home directory is optional. It is recommended to enhance the Provar performance within CircleCI.
The script step contains several sub-steps. First, you should download a Provar Execution Only zip file and then unzip it into the Provar_Home location. Then you should remove the zip file since it is no longer required. The final step is the main step which executes the Provar test cases using your build.xml file and tests that are already synchronised in your Github repository.
Please refer to the following link to execute test cases on alternate browser options supported by Travis.
Parameter changes in build.xml
Step 1: First, create an environment variable for Provar_Home location.
Step 2: Click on More options -> Settings.
Step 3: Add environment variable PROVAR_HOME with the value \${env.TRAVIS_BUILD_DIR}/Provar_Home. Click on the Add button.
Step 4: Then, edit the build.xml file.
The main parameter is to edit is provar.home value is the environment variable PROVAR_HOME. After a successful execution, test reports will be generated in the location mentioned in the build.xml testproject.results parameter.
See the example build.xml.
<project default="runtests"> <property environment="env"/> <property name="provar.home" value="${env.PROVAR_HOME}"/> <property name="testproject.home" value="DemoProject"/> <property name="testproject.results" value="DemoProject/Results"/> <property name="license.path" value="${env.PROVAR_HOME}"/> <echo message="provar home is:${provar.home}"/> <taskdef name="Provar-Compile" classname="com.provar.testrunner.ant.CompileTask" classpath="${provar.home}/ant/ant-provar.jar"/> <taskdef name="Run-Test-Case" classname="com.provar.testrunner.ant.RunnerTask" classpath="${provar.home}/ant/ant-provar.jar;${provar.home}/ant/ant-provar-bundled.jar;${provar.home}/ant/ant-provar-sf.jar"/> <taskdef name="Test-Cycle-Report" classname="com.provar.testrunner.ant.TestCycleReportTask" classpath="${provar.home}/ant/ant-provar.jar;${provar.home}/ant/ant-provar-bundled.jar;${provar.home}/ant/ant-provar-sf.jar"/> <target name="runtests"> <Provar-Compile provarHome="${provar.home}" projectPath="${testproject.home}"/> <Run-Test-Case provarHome="${provar.home}" projectPath="${testproject.home}" resultsPath="${testproject.results}" resultsPathDisposition="Replace" testEnvironment="" webBrowser="Chrome" webBrowserConfiguration="Full Screen" excludeCallableTestCases="true" salesforceMetadataCache="Reload" projectCachePath="${provar.home}/.provarCaches" licensePath="${provar.home}/.licenses" testOutputlevel="WARNING" pluginOutputlevel="WARNING" stopTestRunOnError="false" invokeTestRunMonitor="true" > <fileset dir="../DemoProject/tests"> <include name="GoogleSearch.testcase"/> </fileset> </Run-Test-Case> </target> </project>
<property name="testproject.results" value="DemoProject/Results"/>
- 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
- Understanding Provar’s Use of AI Service for Test Automation
- Provar Automation
- Creating a New Test Project
- Import Test Project from a File
- Import Test Project from a Remote Repository
- Import Test Project from Local Repository
- Commit a Local Test Project to Source Control
- API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- 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
- Customize Browser Driver Location
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- 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 Data Generation
- Test Plans
- Testing Browser – Chrome Headless
- 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
- Database Testing
- Document Testing
- Email Testing
- Email Testing in Automation
- Email Testing Examples
- Gmail Connection in Automation with App Password
- App Configuration for Microsoft Connection in MS Portal for OAuth 2.0
- OAuth 2.0 Microsoft Exchange Email Connection
- Support for Existing MS OAuth Email Connection
- OAuth 2.0 MS Graph Email Connection
- Create a Connection for Office 365 GCC High
- Mobile Testing
- OrchestraCMS Testing
- Salesforce CPQ Testing
- ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices 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
- Salesforce Testing
- Recommended Practices
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- Java 21 Upgrade
- 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