Documentation

Looking for something in particular?

ProvarDX Commands

These are the current commands available for ProvarDX.

To learn more about using ProvarDX, visit our documentation about getting started.

Provar Automation Commands

Generate a boilerplate property file.
Example:

sf provar automation config generate -p provardx-properties.json --json

Flags:

Required:

  • -p | --properties-file
    Path to the properties file that will be generated.

    • Optional:

  • -n | --no-prompt
    Don’t prompt to confirm file should be overwritten.
  • –json
    Format response output as json.

    • Load a property file to be used in subsequent commands.
    Example:

    sf provar automation config load -p myproperties.json --json

    Flags:

    Required:

  • -p | --properties-file
    Path to the properties file.

    • Optional:

  • –json
    Format response output as json.

    • Set one or more properties in the properties file.
    Examples:

    sf provar automation config set environment.testEnvironment="SIT"

sf provar automation config set environment.testEnvironment="SIT" environment.webBrowser="Ch
rome"

sf provar automation config set testCases='["tests/myTestCase.testcase","tests/testSuite1/myTestCase1.testCase"]'

    Flags:

    Required:

  • None

    • Optional:

  • –json
    Format response output as json.

    • Get a property from the properties file.
    Example:

    sf provar automation config get environment.testEnvironment

    Flags:

    Required:

  • None

    • Optional:

  • –json
    Format response output as json.

    • Validate a property file is a well-formed ProvarDX property file.
    Example:

    sf provar automation config validate

    Flags:

    Required:

  • None

    • Optional:

  • –json
    Format response output as json.

    • Install Provar Automation.
    Example:

    sf provar automation setup --version 2.12.1

    Flags:

    Required:

  • None

    • Optional:

  • -v | --version
    Provar Automation build version number.
  • –json
    Format response output as json.

    • Compile PageObject and PageControl Java source files into object code using the configuration set in the properties file.
    Example:

    sf provar automation project compile

    Flags:

    Required:

  • None

    • Optional:

  • -v | --version
    Provar Automation build version number.
  • –json
    Format response output as json.

    • Refresh metadata for a specified Salesforce connection and store it in the folder set in the properties file.
    Example:

    sf provar automation metadata download -c MySalesforceConnection

    Flags:

    Required:

  • -c | --connections
    Comma-separated list of names of Provar Salesforce connections to use, as defined in the project.

    • Optional:

  • –json
    Format response output as json.

    • Run the tests as specified in the loaded properties file.
    Example:

    sf provar automation test run

    Flags:

    Required:

  • None

    • Optional:

  • –json
    Format response output as json.

    • Provar Manager Commands

    Load the alias or username to be used in subsequent commands to connect to Provar Manager.
    Example:

    sf provar manager connect -o my-scratch-org --json

    Flags:

    Required:

    • None

    Optional:

    • -o | --target-org
      Username or alias set in the SF CLI which corresponds to the Provar Manager org.
    • --json
      Format response output as json.

    Retrieve test cases related to the provided user stories (issues) or metadata components, for a given test project.
    Examples:

    sf provar manager testcase retrieve -p MyTestProject -t Apex -m "ApexClass:MyApexClass,YourApexClass;ApexPage" --json

sf provar manager testcase retrieve -p MyTestProject -t ProvarAutomation -i "TM-766,TM-718"

    Flags:

    Required:

    • -p | --test-project
      Test Project Key to filter by.
    • -t | --test-automation-tool
      Test Automation tool used to automate the tests.
      Allowed values: Apex, ProvarAutomation

    Optional:

    • -l | --test-plan
      Test Plan Name. Use if you want to retrieve test instance file paths.
    • -m | --metadata-components
      Semicolon-separated list of metadata components, grouped and prefixed by their metadata type.
    • -n | –ignore-metadata
      Semicolon-separated list of metadata types to ignore from METADATA-COMPONENTS or METADATA-FILE.
    • -f | --metadata-file
      Path to a text file that contains the list of metadata components in source format.
    • -i | --issues
      A comma-separated list of issue names (ISS-000000), issue external keys, or issue external IDs.
    • -o | --output
      Output to a specific file instead of stdout.
    • --json
      Format response output as json.

    Feedback

    Was this article helpful for you?
    Documentation library

    Trying to raise a case with our support team?

    Log into the Success Portal

    We use cookies to better understand how our website is used so we can tailor content for you. For more information about the different cookies we use please take a look at our Privacy Policy.

    Scroll to Top