Version 2.2.1
Executive summary
The latest release of Provar version 2.2.1 is now available in the Provar Success Community.
2.2.1 at a glance:
- Refresh and reselect field locators in Test Builder
- Connection to the server deployment of Zephyr for Jira is now generally available
- Expanded browser compatibility to include Microsoft Edge (Chromium)
- Chrome 87 compatibility
- Renamed logging levels
- Changes to Oracle Java Database Connectivity (JDBC) drivers
An important note about refreshing metadata for 2.2.1
As a result of changes introduced with 2.2.1, we recommend that you refresh your metadata to ensure that tests continue to work as expected. Please refer to the Reload Org Cache support article to learn more about using the Reload All Files functionality.
macOS Big Sur users
Provar 2.2.1 is an optional release. However, if you use a Mac and want to upgrade to macOS Big Sur, you will need to upgrade to Provar version 2.2.1 to keep Provar running smoothly. Please refer to the Big Sur support article for more information.
Access world-class customer support at the Provar Success Community
If you have any questions regarding 2.2.1, please get in touch with us and we would be happy to help. To raise a case, simply log into the Provar Success Community and click View/Raise Case. Providing ongoing support is 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.
Test Builder
Refresh and reselect field locators in Test Builder
We’ve made it easier to manage field locators directly within Test Builder. Using Provar version 2.2.1 (and subsequent versions) you can refresh locators to repair a broken locator in just a few clicks. You can also change locators to a different type of locator based on your preference.
Note: This feature is designed to help you test custom Salesforce components and non-Salesforce applications. Since Provar is designed to natively adapt to Salesforce and is metadata-driven, you do not need to use this feature for standard Salesforce components/functionality.
Who does this impact?
Provar users who would like to change and/or fix a broken field locator directly within Test Builder.
Why is this important?
This feature is designed to address these challenges:
- In some instances, when existing test cases are run against a new application release a field locator may stop working due to technical changes. This is often due to changes in how the web page source is structured.
- You can also use this feature to change the locator type if you feel that Provar has not selected the preferred one by default.
How can I use this feature?
We now offer a simple click-to fix solution.
To learn more about how to use this new feature, please reference Refresh and reselect field locators in Test Builder.
Browsers
Expanded browser compatibility to include Microsoft Edge (Chromium)
We’ve expanded our list of compatible browsers to include Microsoft Edge (Chromium). This change also impacts existing tests that use the legacy version of Microsoft Edge.
Who does this impact?
Provar users who would like to test Salesforce and other web-based applications using Microsoft Edge (Chromium). This also impacts Provar users with existing tests that are configured to use the legacy version of Microsoft Edge.
Why is this important?
Earlier this year, Microsoft officially launched its new Edge Chromium browser for both Windows and macOS. We’ve configured Provar to help you take advantage of this new browser.
Another reason why we are making this change is that the legacy version of Edge is being phased out by Salesforce. Please refer to this Salesforce article about Legacy Edge browser retirement for more information.
As a result, it is on our roadmap to phase out support in a subsequent Provar release.
How does this impact existing tests?
We’ve made the switch from Edge to Edge (Chromium) automatically to make the transition seamless and reduce test maintenance. Existing test run configurations, such as Test Plans and ANT scripts, that have been configured specifically to use the Edge browser will now execute using Edge (Chromium) going forward unless modified.
If you want to execute tests using the legacy version of Edge, you will need to reconfigure your execution scripts to use Edge (Legacy).
How can I use this feature?
You will now see Edge (Chromium) added to the picklists within: Provar Desktop, the ANT dialog box, the Export as ANT dialog box, ProvarDXTM and within Provar Test Plans.
Above: View of Edge (Chromium) within the browser selection drop-down menu of Provar Desktop.
Chrome 87 compatibility
As part of our pre-release testing due diligence, we are happy to announce that Chrome 87 is compatible with Provar version 2.2.1. We have included ChromeDriver 87 in the 2.2.1 distribution.
Who does this impact?
Provar customers who are currently using or would like to upgrade to Chrome 87.
Why is this important?
Ensuring that ChromeDriver 87 is compatible with Provar version 2.2.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 87 we recommend that you upgrade to Provar version 2.2.1, which will use ChromeDriver 87 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.2.1?
Please refer to the Browser and Driver Recommendations support article for a comprehensive guide.
ChromeDriver for 2.2.1
Provar version 2.2.1 is packaged with ChromeDriver 87.
Integrations
Connection to the server deployment of Zephyr for Jira is now generally available
Provar’s integration with the server deployment of Zephyr for Jira is now generally available.
Who does this impact?
Provar customers who would like to integrate with the server deployment of Zephyr for Jira.
Why is this important?
Earlier this year, we launched Provar’s integration with the cloud deployment of Zephyr for Jira. Our integration with the server deployment of Zephyr for Jira is now generally available as well.
How can I use this feature?
You can learn more about Provar’s integration with Zephyr Cloud and Server in this support article to learn how to connect to your Zephyr Cloud and Zephyr Server instances, upload and download tests to and from Zephyr, create Test Plans to run your test against Zephyr and how to execute your Test Plan.
Provar Desktop
Renamed logging levels to Basic, Detailed and Diagnostic
We are working to enhance our logging framework to create logs that have greater clarity and additional diagnostic information. With 2.2.1, we are introducing the first phase of updates that include several UI changes to logging levels and we plan to make additional enhancements in future releases.
As part of the first phase, we’ve updated the test output log fields for the Run Under ANT, Export as ANT and the Export as Provar DXTM dialog boxes so that the logging options reflect the following:
- Show Basic logging (formerly displayed as ERROR, WARNING, INFO)
- Show Detailed logging (formerly displayed as FINE)
- Show Diagnostic logging (formerly displayed as FINER, FINEST)
Who does this impact?
This change impacts Provar customers selecting test output logging criteria.
Why is this important?
This change is part of our ongoing efforts to simplify Provar’s UI/UX.
How can I use this feature?
This change is included with 2.2.1 and you can simply select your preferred logging level from the relevant drop-down menu.
Above: View of the updated Run under ANT dialog box.
Above: View of the updated Export as ANT build file dialog box.
Above: View of the Export as ProvarDXTM dialog box.
Changes to Oracle Java Database Connectivity (JDBC) drivers
Prior to 2.2.1, we packaged Oracle Java Database Connectivity (JDBC) drivers with Provar. With 2.2.1, you will need to manually copy a file into your test project’s lib folder.
Who does this impact?
Provar customers using version 2.2.1 who are testing an Oracle connection in the test settings view, opening a browser with an Oracle connection and/or executing an Oracle CRUD test step. If Provar does not detect the appropriate Oracle JDBC driver, you will see the following dialog box that includes a link to the relevant support article.
Why is this important?
If you are using Oracle and Provar as part of your testing, you will need to install the Oracle JDBC driver in order to ensure that your tests work as expected.
How can I use this feature?
Please refer to this support article to learn more about Installing Oracle drivers.