Provar
his article will discuss various steps required to configure Provar (new and older versions) in AutoRABIT.
Supported Version:Provar version 2.2.0
Provar Integration Steps with AutoRABIT (for version 2.2.0)
The first step in integrating Provar is adding the same configurations in AutoRABIT that you have set in Provar and uploading the 'provar license properties' file under the Plugin section.
Login to your AutoRABIT account.
Click on the Admin module go to the My Account tab from the AutoRABIT home page.
Under the Plugins section, select the Provar checkbox.
Fill in Provar info in the next popup screen:
Name: Enter a name of your choice (max. of 126 characters). The name should not include any special characters except "-".
Web Browser Configuration: Choose the Web Browser Configuration as Desktop Full Screen.
Web Browser Provider Name: Choose Desktop as Web Browser Provider Name.
Web Browser Device Name: Choose the Web Browser Device Name as Desktop Full Screen.
Exclude Callable Test Cases: To exclude callable test cases from execution, select this checkbox.
LicenseFile: Browse the provar licenseâs properties file from your local system and upload it here. This license file will be used by all users activated for their clients. You can even download the recently uploaded license file if needed. The license properties file should contain the information in the same order as shown below:
#Thu Jul 05 15:52:26 IST 2018
licenseStatus=Activated
licenseType=FixedSeat
licenseKey=XXXXX-XXXXX-XXXXXX-XXXXX-XXXXX
lastOnlineAvailabilityCheckUtc=153078614616
Click on OK once you're done filling in the Provar information.
Ensure the above configurations are saved in AutoRABIT by clicking on the Save button. It is an important step, otherwise, all modifications will be lost and you will have to configure Provar from the beginning.
Integration steps with AutoRABIT( for version older than 2.2.0)
To integrate previous Provar versions with AutoRABIT, refer to the below steps:
A. Configuring in Provar IDE
Set the Web Browser to Desktop: Full Screen
Select the Provider Name to Desktop and the Browser Configurations to Full Screen.
If test cases are running under ant, make sure that the build file consists of the following run test case configurations.
webBrowserConfiguration="Desktop Full Screen"
webBrowserProviderName="Desktop"
webBrowserDeviceName="Desktop Full Screen"
B. Integrate Provar as a plugin on the 'My Account' page
Login to your AutoRABIT account.
Go to the My Account tab from the AutoRABIT home page.
In the Plugins section, select the Provar checkbox under Test Types.
Fill in the required Provar details to integrate with AutoRABIT:
Name (mandatory field): Enter a name of your choice (max. of 126 characters). The name should not include any special characters except "-".
License File: Browse the provar licenseâs properties file from your local system and upload it here. This license file will be used by all users activated for their clients.
The license properties file should contain the information in the same order as shown below:
#Thu Jul 05 15:52:26 IST 2018
licenseStatus=Activated
licenseType=FixedSeat
licenseKey=XXXXX-XXXXX-XXXXXX-XXXXX-XXXXX
lastOnlineAvailabilityCheckUtc=153078614616
Once the file gets uploaded, you can view the name of the file which you have under the License File field. You can even download the license file if required.
Click Save to save the Provar configuration in AutoRABIT.
Adding Provar configuration in CI Job
Now, you're done with the integration of Provar as a plugin with AutoRABIT, let's see how we can use it while running CI Job.
Navigate to the Create CI Job page, found under the CI Jobs tab.
On the next page, select one of the criteria for running the CI Job. For example, Run Test Automation Scripts
Next, give the job a descriptive name in the CI Job Name field.
Go to the Test section. In this section, you need to select Provar to run the functional test cases to test the functionality of the code being deployed to production.
Select Fetch Test Cases From as Provar.
Select your Version Control Repository and its mapped Branch.
Now, you need to add the Test Cases Root path and Test Cases Execution path.
Test Cases Root path: Enter the test case root path till the .testproject file
Test Cases Execution Path: Enter the test cases execution path here. For example- tests/sample. If not specified, all the test cases from the 'tests' folder will get executed.
Cross-browser compatibility testing needs to be performed to ensure if the rendering of data is correct across multiple browsers. Select the browser in which you would like to run the test cases.
Fill in other section details as required and click on Save.
So, once the configured CI job is run and the build is triggered, Provar will review the code changes and functional review information can be found in the CI Job Result under the Functional Tests section. Here, you can find the status of the functional test done along with other details such as the number of components that successfully got reviewed, the number of components failed to review, components that are about to get reviewed or are in the queue.
Troubleshooting
While triggering a build for Provar configured CI job, AutoRABIT application throws the error: 'Provar Plugin is not enabled. Please contact your Administrator and try again.'
Reason: Typically this happens if you have built a CI Job with the provar configured in our application. However, for whatever reason, your org admin has disabled the Provar plugin for your account. Therefore, if you trigger a build for Provar configured CI job, our application will throw the previously described error, as your account is no longer configured with the Provar plug-in. Another scenario in which you would like to fetch the provar configured CI job with other test cases will promptly notify you that your CI job is already configured with the provar.
Last updated
