Looking for something in particular?

Salesforce CPQ Testing

Salesforce CPQ is a Configure-Price-Quote solution built on Salesforce Lightning. Salesforce CPQ has certain elements that make it a challenge to test using standard automation methods such as Selenium.

How does Automation Support Salesforce CPQ Testing?

These tags are visible in the page’s HTML. This makes them resistant to testing using traditional locators such as Field IDs and XPaths. While CSS locators can work, they tend to be brittle and complex to construct.

Automation has been extended to support and offer a guide in Salesforce CPQ testing on several fronts, with a specialized type of locator available for buttons, links, and text fields. Automation also supports testing Salesforce CPQ tables, tabs, and standard screens.

Support for Salesforce CPQ v216.8

Automation supports the mapping and execution of Salesforce CPQ v216.8. Earlier versions of Salesforce CPQ used Shadow DOM elements which Salesforce removed without prior notice in the 216.x versions. Provar has resolved the issues reported to date and extended support for the By Salesforce CPQ to include the following CPQ screens:

  • Choose Price Book
  • Edit Quote:
    • Fields and buttons
    • Table mapping
    • Action icons
  • Favorite Lookup: Table and button support
  • Product Selection:
    • Table
    • Search Product
    • Buttons
    • Filter
  • Configure Product:
    • Buttons and Tables
    • Tab Option Layout
    • Wizard Option Layout
    • Section Options Layout
    • Filter Screen and buttons
    • Options in Category
    • Section Option with Tab

Testing Salesforce CPQ

Salesforce CPQ pages can be mapped in the usual way using the Test Builder. Automation will recognize standard Salesforce functionality and map it using standard Salesforce layouts.

Mapping Standard CPQ Fields

Standard CPQ fields can be mapped in the usual way using the Test Builder. Note that standard CPQ fields will use Automation’s standard Salesforce locators:

Below is the same step in Automation.

Mapping Custom CPQ Fields

Custom CPQ fields can also be mapped using the Test Builder.

Below is a draft test step mapping Test Builder’s Additional Dis. (%) field.

Below is the corresponding On Screen test step in Automation.

Review Provar on G2
Documentation library

Trying to raise a case with our support team?

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