Running Provar on Linux


The following page describes how to set up Provar to run tests on Linux and how to troubleshoot common issues with setup. These steps can be applied both to Linux GUI and Linux Server (Non-GUI).

Note that this setup could also be performed on a Windows machine which does not have Provar installed. In this case, however, it is recommended that you just install Provar then follow the steps outlined in the main guide, beginning at Introduction to Test Scheduling.

Note: The following steps have been tested against Ubuntu 16.04. Other Linux versions have not been tested.

Generating the Build.xml File

Ensure that you have installed Java 1.8 or later and ANT 1.9.0 or later prior to completing the steps below.

To generate the Build.xml, we recommend using Run Under ANT on a machine which has Provar installed, then customizing the file to run on Linux, as below. Refer to this sample file for an example of a build file configured for use without Provar installed.

The three main property tags that need to be reconfigured are provar.home, testproject.home and testproject.results:

  • p​rovar.home contains the location where the Provar installation was unzipped to. On Windows this defaults to C​:\ProgramFiles\Provar
  • t​estproject.home is the folder that contains the Test Project .​testproject file
  • t​estproject.results is where the test run’s results should be written

Additional properties:

  • maxMemory defines the maximum memory that the plug-in can use. This is an optional tag and can be excluded if wanted
  • <​taskdef> ​defines the R​un-­Test-­Case ​task, together with its classpath
  • The Run­-Test-­Case tag contains execution configuration and runs one or more Test Cases or Test Folders

Note that, while the classpath on <​taskdef>​ allows different Provar versions to be run on the same machine, ANT always looks in its lib folder first. This means that c​lasspath​ entries will be ignored if the same .jar files exist in the ANT’s lib folder.


Step 1: Set path and Environment variables:

  • Ant and Java should be set under PATH
  • Create ANT_HOME environment variable
  • Create PROVAR_HOME environment variable (set ProvarHome location as defined in step 3, e.g. /Downloads/ProvarHome)

Step 2: Add your Provar license to the following location {USERHOME}\Provar\.licenses.

Note: You can generate this license file on the machine where Provar is installed and paste it here.

Step 3: Set up Provar libraries. Create a ProvarHome folder (e.g. /Downloads/ProvarHome) then download and unzip at ProvarHome location. ProvarHome should contain the following folders:

Step 4: Set up your Provar Project: Create a ProvarProject folder (e.g. /Downloads/ProvarProject ) then download and unzip Provar Project at ProvarProject location.

Step 5: Trigger the execution by going to the location of build.xml {ProvarProject}\{Project}\ANT and running the following command: ant –f build.xml

You should see execution logs on the terminal. A results file will be created at the location defined in build.xml. (The default location is {ProvarProject}\{Project}\ANT .) 


License details are required.  License path: null

Description: The logs show the message “License details are required.  License path: null” although the license has already been added to the Build.xml file.

Solution: Try the following:

  • Check entry of Provar License Path in Build.xml file
  • Check file location and compare path added to build.xml file.
  • Ensure that all cases match: Linux is case sensitive

Error while loading shared libraries: libX.….: cannot open shared object file: No such file or directory

Solution: Try the following:

  • Install package with the following command: sudo apt-get install libxi…. libgconf-2-4
  • Check version of chrome browser: download a compatible chrome driver from here, then unzip and paste into the Project lib folder

[WebDriverException: unknown error: Chrome failed to start: exited abnormally

Description: Console logs show the above error while executing Provar test cases through Jenkins.

Solution: Try the following:

  • Check installed chrome version and compatible chrome driver version
  • Try this solution from StackExchange

Leave A Comment