Version 2.3.1

Executive summary

We’re excited to announce the latest updates to Provar with the release of version 2.3.1. The latest release of Provar version 2.3.1 is now available in the Provar Success Portal.

New Feature! With 2.3.1, we are happy to announce a new Salesforce OAuth connection feature in Provar. With this new feature, Provar users can make a Salesforce OAuth connection using a connected app rather than a username and password. So, the password is not shared and enhanced security can be implemented. And, Provar is able to create, test, and edit a Salesforce connection using a Consumer Key and Consumer Secret and a Callback URL.

For more information on this, we’ve put together a new support article, Adding a Salesforce OAuth connection, that talks about how to use a Salesforce OAuth connection in Provar.

Our 2.3.1 release ensures compatibility with the Salesforce Spring ’21 release to keep your tests working as expected.

We have enhanced our logging framework to create logs that have greater clarity and have additional diagnostic information. Provar users can now see a new logging hierarchy in the Test Runner log viewer where they can see more user-friendly logging messages.

2.3.1 at a glance:

Salesforce OAuth Connection is now available in Provar.
Additional Provar compatibility fixes for the Salesforce Spring ’21 release.
Revised report generation screen.
Chrome 89 compatibility.

Access world-class customer support at the Provar Success Portal

If you have any questions regarding 2.3.1, please get in touch with us and we would be happy to help. To raise a case, login to Provar Success Portal and click View/Raise Case. At Provar, providing ongoing support is a part of our promise to help you deliver robust, scalable and repeatable testing to achieve release agility, drive down system errors and get the maximum return on your Salesforce investment. Please contact us for more information.

Salesforce Connections

Salesforce OAuth Connection

Until now, Salesforce connections in Provar were dependent on the username and password to make a connection to a Salesforce org to create and execute automated tests, to download metadata and to make other Salesforce API calls.

With this new Salesforce OAuth Connection feature, Provar users can create a Salesforce connection using a connected app instead of username and password. Hence, the password is not shared and enhanced security can be implemented.

Who does this impact?

This new Salesforce OAuth Connection feature will be widely useful by Provar customers as this can be used with any Salesforce org configured to accept OAuth connections from connected apps.

Why is this important?

It is important that Provar customers take advantage of the key security improvements as soon as reasonably possible.

Due to the enhanced security provided by OAuth, which does not rely on username and password credentials, Provar recommends the OAuth authentication method for creating Salesforce connections from 2.3.1 onwards.

How can I use this feature?

For information on how to use this feature, we’ve put together a new support article, Adding a Salesforce OAuth connection, that talks about how to use a Salesforce OAuth connection in Provar.

Additional compatibility fixes for Salesforce Spring ‘21

Salesforce Spring ‘21 compatibility fixes for 2.3.1

Provar version 2.3.1 is compatible with the Salesforce Spring ’21 release. You can learn more about the release here.

As a Salesforce partner and the leading Salesforce test automation provider, we’ve been working closely with Salesforce’s Business Scenario Team (BST) in order to ensure that your regression tests remain stable even after new Salesforce features are added with major releases. You can click here to learn more about Provar and Salesforce pre-release Business Scenario Testing (BST) program.

During the Salesforce Spring ’21 Preview, our team identified over a dozen important changes and updated Provar to remain fully compatible with Salesforce ensuring that your tests continue to perform as expected.

Browsers

Chrome 89 compatibility

As part of our pre-release testing, we are happy to confirm that Chrome 89 is compatible with Provar version 2.3.1. We have included ChromeDriver 88 in the 2.3.1 distribution.

Who does this impact?

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

Why is this important?

Ensuring that ChromeDriver 88 is compatible with Provar version 2.3.1 eliminates the risk of incompatibility issues which can prevent Provar from working as expected.

How can I use this feature?

If you would like to upgrade to Chrome 89 we recommend that you upgrade to Provar version 2.3.1, which will use ChromeDriver 88 out of the box.

In general, Provar will automatically attempt to download the correct ChromeDriver if it detects a driver exception. If your organization’s security protocols block the automatic download, you can override the ChromeDriver manually.

To downgrade or revert the ChromeDriver you can refer to this support article that explains how to use a ChromeDriver that is different from the one provided by default in your Provar installation.

What are the browser and driver combinations that you recommend for Provar 2.3.1?

Please refer to the Browser and Driver Recommendations support article for a comprehensive guide.

Packaged ChromeDriver for 2.3.1

Provar version 2.3.1 is packaged with ChromeDriver 88.

Provar Desktop

Improved Report Generation Screen

We have revised the report generation screen as the next step in our series of logging enhancements.

The screen now takes advantage of the new logging categories:

Basic
Detailed
Diagnostic

Who does this impact?

Provar users will now see the revised logging levels in the report configuration screen.

Why is this important?

This change upgrades our report generation features to take advantage of our improved logging framework.

How can I use this feature?

This enhancement is available whenever creating an export report from a test run in Provar Desktop, also when using Run Under ANT, Export as ProvarDX and Test Plan PDF configuration.