We're here to help

Version 2.0.4

Above: View of the Rename the Test Step functionality within the Test Builder.

 

Executive summary


We’re happy to announce the release of Provar 2.0.4 which is now available in the Provar Success Community.

This release is designed to:

  • Make it easier to create and manage tests directly within the Test Builder
  • Reduce test maintenance and rework by natively adapting to Salesforce metadata changes
  • Enhance information security for web service requests

 

 

Key updates at a glance


Expanded support for new features in Salesforce Spring ’20

  • Provar version 2.0.3 marked the official launch of our support for the Salesforce Spring ’20 release
  • Provar version 2.0.4 is designed to expand upon that native testing functionality to support your adoption of new Salesforce features, in addition to the latest version of Salesforce CPQ

 

Run mode changes within the top navigation toolbar

  • With Provar version 2.0.4, the Test Builder icon will remain as a stand-alone icon within the top navigation toolbar with the Run (without debug) icon displayed to the right
  • You can also click the caret next to Run to execute your selected tests using Debug and Run Under ANT as options within the drop-down menu

 

Disable test steps and rename test steps directly within the Test Builder

  • These changes are part of our ongoing efforts to provide more flexibility as you create and debug tests, letting you do more directly from Test Builder

 

Send client SSL certificates for web services

  • With 2.0.4, you can now send authentication certifications easily to enhance data security

 

 

Table of contents


Driver and browser updates

  • Chrome 80 compatibility check
  • GeckoDriver and Firefox compatibility

 

Salesforce Spring ’20

  • Clone Opportunities or Campaigns along with their related records
  • Prepare for Google Chrome’s changes in SameSite cookie behavior
  • Permission Set Groups

 

Test Builder

  • Enable and disable test steps in Test Builder
  • Rename test steps in Test Builder

 

System

  • Run mode changes within the top navigation toolbar
  • Add, Edit and Delete custom headers using REST and SOAP API connections
  • Support for client certificates for REST and SOAP web services (Beta)
  • SOAP web service authentication
  • Remove unwanted values populated in the test case XML

 

Salesforce

  • Edit Price Book entries from the Price Book object and add Products from the Price Book object
  • Directly navigate to an app using the appId or appDeveloperName URL parameters

 

Salesforce CPQ

  • Auto-paginate support for Salesforce CPQ tables
  • Provar now supports version 224.7 of Salesforce CPQ

 

 

Driver and browser updates

Chrome 80 compatibility check


ChromeDriver 80 is packaged together as part of Provar version 2.0.4 to keep your tests running smoothly.

 

Who does this impact?

Provar customers who are currently using or would like to upgrade to Chrome 80.

 

Why is this important?

Packaging ChromeDriver 80 as part of Provar version 2.0.4 eliminates the risk of incompatibility issues.

For example, if you have already upgraded to Chrome version 80, you may have previously experienced a failed to create ChromeDriver error when creating or executing Provar tests. This applied to all run modes, including Test Builder, and also via Apache Ant in conjunction with any continuous integration solution.

As a result of this change, Provar version 2.0.4 can now work seamlessly with Chrome 80 and you should not experience this error message. If you are using older versions of Google Chrome you may need to downgrade your driver.

 

How can I use this feature?

With Provar version 2.0.4, this is now standard functionality available for all customers enterprise-wide. You do not need to make any adjustments within Provar.

 

What are the browser and driver combinations that you recommend using Provar 2.0.4 via Chrome?

 

Note: Google Chrome’s changes in SameSite cookie behavior


The Google Chrome version 80 release changes the default cross-domain (SameSite) behavior of cookies. This change enhances security and privacy, but requires customers and partners to test custom Salesforce integrations that rely on cookies. 

 

Who does this impact?

  • Lightning Experience and Salesforce Classic users of Google Chrome 80 or later
  • Users testing custom Salesforce integrations that rely on cookies

 

Why is this important?

Some custom integrations that rely on cookies no longer work in Google Chrome. Cookies don’t work for non-secure (HTTP) browser access including any community, portal, site, or Outlook or Gmail integration in your org. 

This change particularly affects, but is not limited to, cross-domain communication and integrations using iFrames.

 

What should I do?

To learn more about how this may impact you, please refer to this Salesforce help page to learn more.

 

GeckoDriver and Firefox compatibility


Provar version 2.0.4 uses the latest GeckoDriver v0.26.0 which supports the latest version of Firefox version 71.0 to keep your tests running smoothly!

 

Who does this impact?

Provar users creating and managing tests that use a Firefox internet browser.

 

Why is this important?

Driver and browser version incompatibility issues prevent Provar from running as expected.

 

How can I use this feature?

With Provar version 2.0.4, this is now standard functionality available for all customers enterprise-wide. You do not need to make any adjustments within Provar.

 

Salesforce Spring ’20

Clone Opportunities or Campaigns along with their related records


New with the Salesforce Spring ’20 release, users can use the Clone with related records action to create recurring Opportunities and Campaigns instead of having to find and add related items one-by-one when they recreate those records.

Provar version 2.0.4 supports the testing of this new feature using the Clone with related records screen.

 

Who does this impact?

  • Lightning Experience users
  • Organizations who decide to enable this new feature

 

Why is this important?

This Provar enhancement is designed to natively support the testing of this new feature within Salesforce.

 

How can I use this feature?

You can test this feature using standard mapping procedures.

Above: Select records to clone with a Salesforce Opportunity

Above: Select records to clone with a Salesforce Campaign

 

Permission Set Groups 


Salesforce made Permission Set Groups generally available with the release of Spring ’20. You can start testing this new feature right away with any version of Provar since Provar version 2.0.4, and prior versions, are all compatible.

 

What are Permission Set Groups?

Permission set groups can help you consistently and reliably assign permissions to a group of users and assign users a single permission set group instead of multiple permission sets.

 

Key benefits:

  • Permission set groups combine selected permission sets to provide all of the permissions that users need for their job function
  • You can easily identify and review all added and removed permissions before they become part of your permission ecosystem
  • Using the muting permission feature, you can access more granular control over permissions to ensure you’re complying with the principle of least privilege

 

Who does this impact?

Lightning Experience and Salesforce Classic users can optionally choose to implement this new feature. You can start using and testing this new feature with Provar 2.0.4, and prior versions as well.

 

Why is this important?

This is a new, optional feature offered by Salesforce that is natively supported by Provar for testing.

 

How can I use this feature?

Due to our unique metadata integration, this does not affect Provar tests. Once you add a permission set group to a user, simply refresh your metadata within the Org Browser and Provar tests will run with the users’ new permissions.

 

Test Builder

Enable and disable test steps in Test Builder 


You can now enable and disable test steps directly within the Test Builder.

 

Who does this impact?

All users working within the Test Builder.

 

Why is this important?

This new feature is designed to simplify the process of managing tests directly within the Test Builder by eliminating the need to toggle to Provar Desktop.

 

How can I use this feature?

If you would like to temporarily disable a test step, simply pause the execution of the test and right-click the test step within the Test Builder. Within the pop-up menu, select Disable the Test Step.

To enable a previously disabled test step, you can simply follow the same steps listed above and select Enable the Test Step from the pop-up menu.

Above: View of Test Builder Enable the Test Step functionality. 

 

Rename test steps in Test Builder 


You can now rename test steps directly within the Test Builder.

 

Who does this impact?

All users working within the Test Builder.

 

Why is this important?

Provar does a good job of naming steps automatically. However we do recommend adding more meaningful names to UI Assert steps in particular. This new feature is designed to simplify the process of managing tests directly within the Test Builder by eliminating the need to toggle to Provar Desktop to make the change.

 

How can I use this feature?

If you would like to rename a test step, simply pause the test and right-click the test step within the Test Builder. Within the pop-up menu, select Rename the Test Step and enter the new test step description.

Above: View of the Rename the Test Step functionality within the Test Builder. 

 

System

Run mode changes within the top navigation toolbar


Who does this impact?

All Provar users.

 

What is changing?

With the launch of 2.0.3, we combined the Run options within the top navigation toolbar of Provar Desktop into a single drop-down menu. Since then, we have received some helpful usability feedback to improve our UI/UX. As a result, we are introducing an updated version of this feature as part of our ongoing efforts to optimize your experience using Provar.

In Provar version 2.0.3, when you clicked the Test Builder icon in the top navigation toolbar of Provar Desktop, the drop-down menu revealed Run/Debug, Run Under ANT and Test Builder. As part of this change, the Run without debug functionality was moved and only accessible via the Navigator by right-clicking a test case.

With Provar version 2.0.4, the Test Builder icon will remain as a stand-alone icon within the top navigation toolbar with the Run (without debug) icon displayed to the right. You can also click the caret next to Run to execute your selected tests using Debug and Run Under ANT as options within the drop-down menu.

In addition, we have also rolled back changes to the Test Runner to restore the version 1.9.13 icons for consistency in the Test Runner toolbar. We may revisit this again in the future as we continue to make strides towards optimizing the navigation.

 

Why is this important?

These UI/UX updates are designed to help simplify the process of creating and managing tests within Provar Desktop by making the interface more intuitive to navigate.

 

How can I use this feature?

This is now standard functionality available for all customers enterprise-wide. You do not need to make any adjustments within Provar.

Above: View of new top navigation toolbar within Provar Desktop.

 

Add, Edit and Delete custom headers using REST and SOAP API connections


You can send custom headers for REST and SOAP web service connections instead of passing the information via every web request. HTTP headers allow the client and the server to pass additional information with an HTTP request or response to help systems talk to each other and communicate the right information.

Common examples include information about the resource to be fetched, the client requesting the resource and additional information about the response, such as its location or about the server providing it.

 

Who does this impact?

Provar testers with test cases that involve web service requests.

 

Why is this important?

This new feature is designed to help you save time initializing and maintaining these connections. This can also help you reduce the duplication of headers across multiple web service requests by specifying the repeated header information on the web service connection.

 

How can I use this feature?

The following includes instructions for providing custom headers by creating a new REST or SOAP API connection. Note: You can also refer to our Creating a web service connection support article for more information. 

Step 1: To create a REST or SOAP web service connection, navigate to the Connections tab of the Testing Settings view and click the green plus sign icon.

Step 2: Give the connection a name then select Connection Type: Generic Web Service. In the drop down menu to the right, select a sub-type of Rest Web Service or SOAP Web Service..

Step 3: Add the URL of the REST or SOAP connection and select the appropriate connection subtype from drop-down menu. For example, Basic Authentication, AWS Authentication, etc. Based on the connection subtype that you selected, you will be asked to enter additional information.

Step 4: Within the Custom Headers section, click the green plus sign to create a new Custom Header. Enter the Key and Value and click OK.

Note: Once you have created new Custom Headers for the REST or SOAP connection, you can edit information within the Overrides section of this pop up menu to change existing connection details. 

Above: View of REST API connection with custom header information populated.

 

Support for client certificates for REST and SOAP web services (Beta)


Client certificates are a common solution to validate the identity of a calling system to ensure it is trusted to connect to a remote service. We are pleased to announce that Provar now supports sending client SSL certificates via Provar REST and SOAP web services. In version 2.0.4, Provar supports PFX client certificates for HTTPS web service requests and we plan to extend this in the near future. Please contact us if you’d like to participate in future development of this feature.

 

The following includes common scenarios for using this feature:

  • You can now choose the PFX option for a REST or SOAP service with No Authentication and Basic Authentication
  • You can pass a PFX certificate file and passphrase from the local system
  • If the correct certificate and passphrase is given, the REST or SOAP call will allow the web service to authenticate the connection using the certificate

 

Who does this impact?

  • Provar testers with test cases that involve web service requests requiring client certificates. These could not be tested using Provar prior to version 2.0.4.

 

Why is this important?

This new feature allows you to test secure web services that previously could not be tested with Provar.

 

How can I use this feature?

Step 1: To start using this new feature, you can follow the normal procedures for creating and editing a web service connection. You can refer to the Creating a web service connection help article.

Step 2: Within the Add a New Connection or Edit Connection Details screens, you will now see two radio buttons within the Certificate Type section. To enable this feature, select the PFX radio button.

Step 3: Click Browse to find and select the Certificate Path.

Step 4: Enter your Passphrase and click OK.

Above: View of Edit Connection details to enable PFX certifications for rest services.

 

SOAP web service authentication


Provar version 2.0.4 supports the authenticatication of Simple Object Access Protocol (SOAP) web services.

 

Who does this impact?

  • Lightning Experience and Salesforce Classic users
  • Provar testers with test cases that involve SOAP web services API calls

 

Why is this important?

This new feature enhances your data security.

 

How can I use this feature?

Step 1: To start using this new feature, you can follow the normal procedures for creating and editing a Simple Object Access Protocol (SOAP) API connection. You can refer to the Creating a web service connection help article.

Step 2: Within the Add a New Connection or Edit Connection Details screens, you will now see a Connection Type field. Select Basic Authentication from the drop down menu.

Step 3: Enter the User and Password information.

Step 4: Click OK.

Above: View of enabling basic authentication for a SOAP web services connection.

 

Remove unwanted values populated in the test case XML


You can now initiate an auto-clean to remove unwanted values that are populated within the test case XML that may be preventing the test case from executing correctly.

 

Who does this impact?

Provar testers that experience the following issues.

 

Why is this important?

This new feature can help you bypass issues that may prevent test cases from executing correctly.

 

Why did I receive this error message?

There are various reasons why unintended information is added to a test case file that prevents the test from executing. This may be the result of manual edits to the file’s XML, issues with version control merge or potential issues created by Provar when actions are interrupted or incomplete.

The purpose of this auto-clean feature is to detect and solve this issue when it happens.

 

When should I use this feature?

You should use this feature if you experience the following error message:

com.provar.core.model.base.api.exceptions.TestError: The updated value is not a NamedValue. ValueName: name, ValueId: 496, UpdatedValue: PrimitiveValueImpl [ value: false, valueId=1f0, createdUpdateSeq=150, updatedUpdateSeq=150]

at com.provar.core.model.base.java.NamedValueListValueImpl.refreshValue(NamedValueListValueImpl.java:539)

at com.provar.core.testexecution.common.java.ValueManagerImpl.refreshValuesAndRefenceCountChangedFlags(ValueManagerImpl.java:1394)

How can I use this feature?

If you attempt to execute a test case and experience this error message, you can use a utility file to cleanup the corrupted test cases by executing an API. If you have experienced this error message, please contact us at support@provartesting.com. Our Customer Success Team can work with you to help provide the auto-clean file and customized instructions for how to apply it.

 

Salesforce

Edit Price Book entries from the Price Book object and add Products from the Price Book object


With Provar version 2.0.4, we’ve expanded our native testing functionality for Salesforce Price Books.

You can now use Provar to test the Edit Selected Price Book page. This includes mapping all of the possible interactions and assertions on the screen including the Back, Cancel and Save buttons.

Above: View of Edit Selected Price Book Entries

 

In addition to that, you can now use Provar to add Products from the Price Book entries related list in the Price Book object. This includes mapping all of the possible interactions and assertions on the screen including the Add Products button.

Above: View of the Add Products screen

 

Who does this impact?

  • Lightning Experience and Salesforce Classic users
  • Provar users testing Salesforce Price Book Entries

 

Why is this important?

This enhancement is designed to help you easily build break-resistant tests for your Salesforce org.

 

How can I use this feature?

You can test this feature using standard mapping procedures.

 

Directly navigate to an app using the appId or appDeveloperName URL parameters


With the release of Salesforce Winter ’20, you can now directly navigate to an app using the appId or appDeveloperName URLparameters. Provar natively supports this change.

Provar will no longer open the App Launcher automatically to switch applications. This will speed up test execution, increase test robustness and reuse of tests across browsers.

 

Who does this impact?

  • This change applies to Lightning Experience in all editions
  • This change doesn’t apply to Lightning Out, Lightning communities, or the Salesforce mobile app

 

Why is this important?

This new feature offered by Salesforce is designed to simplify the process of building and managing tests by making the user interface and user experience more consistent across all browsers.

 

How can I use this feature?

This is now standard functionality available for all customers enterprise-wide. You do not need to make any adjustments within Provar.

 

Salesforce CPQ

Auto-paginate support for Salesforce CPQ tables


With Provar version 2.0.4, you can now test tables more easily within Salesforce CPQ. Previously, only the first 25 records displayed within tables could be tested using standard Provar mapping procedures.

Provar now supports auto-pagination when testing tables with 26 or more records.

 

Who does this impact?

  • Lightning Experience and Salesforce Classic users
  • Salesforce CPQ testers

 

Why is this important?

You can now create and manage more comprehensive Provar tests for Salesforce CPQ tables.

 

How can I use this feature?

You can test this feature using standard mapping procedures. Auto-pagination is enabled as the default setting within Provar when testing CPQ tables. (Please note, the autopaginate functionality will only work if the With Row steps have WHERE row locators not static numbers.)

Above: View of Auto Paginate option within the Test Builder. 

Above: View of Auto Paginate option within the Test Builder. 

 

Provar now supports version 224.x of Salesforce CPQ


Provar version 2.0.4 natively supports the testing of version 224.7 of Salesforce CPQ.

 

Who does this impact?

  • Lightning Experience and Salesforce Classic users
  • Provar users who are managing tests the testing of version 224.7 of Salesforce CPQ

 

Why is this important?

This enhancement is part of our continued investment in the testing of Salesforce CPQ via Provar.

 

How can I use this feature?

With Provar version 2.0.4, this is now standard functionality available for all customers enterprise-wide. You do not need to make any adjustments within Provar.