Provar Integration

Owned by Hemalatha
Jun 13, 2022
3 min read

Description: Provar is an end-to-end test automation solution designed especially for Salesforce, which is designed to be usable by developers and non-developers alike. Provar supports the testing of a wide range of Salesforce functionality. Utilize Provar in Opsera to run test cases against a Salesforce Org of your choice using the following instructions.

Prerequisites: Prior to provar pipeline integration through Opsera, ensure there is a properly configured Provar, SFDC Configurator and Source Repository tool (Bitbucket, Github or Gitlab) saved in Opsera’s Tool Registry.

Tool Registry Configuration

  1. Navigate to Tool Registry and click + Create New Tool button.

  2. Locate the Provar tool and click Select Tool button.

  3. In the Create New Tool form, provide a Tool Name and any other field values.

  4. Click Create button to save the tool.

  5. Navigate to the new tool’s License tab and make the selections:

    License Type - From the drop-down, select the Provar license type you are configuring. Choose Trial, FixedSeat or Floating.
    License Key - Paste from Provar portal.

  6. Click Save button to save the values and configure a pipeline using the tool.

Provar Pipeline Configuration

  1. Create a new pipeline step. In Step Setup, select Provar from Tool drop-down and provide a unique Step Name. Click Save button.

  2. Click the settings gear to configure the step.

  3. In Step Setup, provide values:

    Provar Tool - Select the configured Provar tool from Tool Registry.
    Salesforce Tool - Select a properly configured SFDC Configurator Tool.
    SCM Service Type - Select a Source Code Management service type. Choose from Bitbucket, Github, or Gitlab.
    SCM Tool - Choose the properly configured Source Code Management tool from Opsera’s Tool Registry.
    Repository - Select a Repository fetched from your SCM.
    Branch - Select a Branch fetched from the selected SCM repository.
    Ant Target - user defined field(non Mandatory) - is the target name from build.xml file. If there are multiple targets you can specify the target which you want run.
    Ant Build XML Path - user defined field(non Mandatory) - by default build file path is ../ANT/ . if any changes in the directory can be specified here.

  4. Once the Step Configuration selections have been made, click the Save button and close. You can now trigger the pipeline.

  5. Click Start Pipeline button to trigger the pipeline. Once the pipeline has completed the run, view the Report in Pipeline Logs.

Pipeline Logs



Â