Version 2.1.1
Executive summary
The latest release of Provar version 2.1.1 is now available in the Provar Success Community.
With 2.1.1, we are excited to announce the launch of ProvarX™, a new feature within Provar that is designed to make it easier to test web components where traditional XPath locators stop short. (Related to that, we’ve put together a new support article, Salesforce Lightning Web Component (LWC) locator support, that talks about your options for testing web components using Provar.)
In addition, we’re also sharing more information about how you can use ProvarDX™, a feature designed to help you radically simplify the process of executing Provar tests in conjunction with Salesforce DX, an integrated, end-to-end development ecosystem designed for high-performance agile software development.
2.1.1 at a glance:
- ProvarX™ is now generally available
- ProvarDX™ is now generally available
- Zephyr Cloud and Server integration [Beta]
- JavaScript locator support is now generally available
- Edit Page object locators in Test Builder
- HTML editor enhancements
- Chrome 84 compatibility information
- Salesforce critical updates and 2.1.1 compatibility
Runtime environment and backwards compatibility for 2.1.0 and 2.1.1
We provided the following information in the 2.1.0 release notes, but it’s worth mentioning again if you are taking the 2.1.1 release and skipped 2.1.0.
With 2.1.0, we introduced several enhancements designed to improve data security and encryption. As a result of these changes, we recommend that you backup Provar projects (created prior 2.1.0) and upgrade all environments where you execute Provar projects to ensure that your tests continue to work correctly. Existing tests will continue to work with 2.1.0, though projects edited with 2.1.0 will require a 2.1.0 runtime environment to guarantee compatibility with project files and new features.
Upgrading from 2.1.0 to 2.1.1
If you upgrade from 2.1.0 to 2.1.1, test cases are backwards compatible. This means that tests created with 2.1.0 will continue to work using Provar version 2.1.1. Tests created using Provar version 2.1.1 require a 2.1.0 or 2.1.1 runtime environment.
Potential backwards compatibility issue with the new HTML editor enhancement
With Provar version 2.1.1, the new HTML editor enhancements may cause backwards compatibility issues for some customers. If you are impacted, you can learn more about how to disable this feature in the release notes below.
For further information about anything contained in these release notes, please contact us at [email protected].
Salesforce Critical Updates
Salesforce Critical Updates for 2.1.1
Salesforce periodically releases updates that improve the performance, logic, and usability of Salesforce, but these can affect your existing customizations.
To help keep you informed, we have created a list of Salesforce critical updates that also includes our recommendations for testing those within your sandbox environments prior to enabling those features in order to minimize risk. Based on our internal analysis, we have assigned each update with a testing priority of high, medium or low.
We will update this support article prior to each major Salesforce release.
Status of testing with Provar version 2.1.1
In addition to that, we have also tested two high priority updates. Based on our internal analysis, the following can successfully be enabled with no impact on Provar tests.
Integrations
Zephyr Cloud and Server integration (Beta)
We are continuing to refine our Zephyr Cloud and Zephyr Server integration that is available as a beta feature for Provar customers.
Who does this impact?
Zephyr Cloud and Zephyr Server users.
Why is this important?
Integrating Provar with Zephyr Cloud and Zephyr Server can help simplify and accelerate testing and release management.
How can I use this feature?
We’ve put together information that walks you through Provar’s integration with Zephyr Cloud and Zephyr Server 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
- Execute your Test Plan
Please refer to our Zephyr Cloud and Zephyr Server (Beta) support article to learn more about using this beta feature.
ProvarDX™
ProvarDX™ is designed to help customers radically simplify the process of executing Provar tests in conjunction with Salesforce DX, an integrated, end-to-end development ecosystem designed for high-performance agile software development. Salesforce DX offers source-driven development, rapid testing and deployment and team collaboration with governance.
Who does this impact?
Teams using Salesforce CLI and especially scratch orgs to manage their changes between environments or those customers wishing to use an alternative to ANT for Provar server execution.
Why is this important?
Using ProvarDX and Salesforce DX together, Salesforce teams can test releases in scratch orgs prior to them being deployed as part of their continuous integration and continuous delivery (CI/CD) pipelines. By design, ProvarDX addresses the many challenges associated with testing multiple orgs that are temporary in nature throughout the entire release lifecycle. ProvarDX includes both a Salesforce CLI plugin for ease of installation and maintenance, and a VS code extension to guide users quickly through the available command options.
How can I use this feature?
Please refer to our Salesforce DX integration support article to learn more.
Lightning Web Components
ProvarX™
ProvarX™ is an enhanced feature within Provar that is designed to make it easier to test custom and standard web components within a web app where traditional locators like XPath and CSS (used by other test automation frameworks) are unable to find elements within a web component without using a JavaScript locator.
Who does this impact?
Teams testing web components within a web app and find that traditional XPath and CSS locators are not able to locate an element.
Why is this important?
In some instances, you may attempt to test web components within a web app and find that traditional XPath and CSS locators are not able to locate an element. This is because web components are encapsulated by the Shadow DOM. Within the Shadow DOM, the elements within a web component are private which means that XPath and CSS locators are unable to access their elements.
How can I use this feature?
Provar will automatically suggest ProvarX as the recommended locator when needed. As always you can override this with an alternate locator. Please refer to our ProvarX support article to learn more information about this new feature.
Limitations
There is a limitation in using the ProvarX locator on generic web pages (non-salesforce pages) on the following browsers when interacting with web components using the native Shadow DOM: IE 11.
JavaScript locator support is now generally available
With Provar version 2.1.0, we introduced JavaScript locator support in beta – this new feature is now generally available. Using Provar Test Builder and Provar Desktop, you can set up relatively simple locators using JavaScript to find elements on a web page using ordinary JavaScript code to locate an element. This is particularly useful when locating elements within a Shadow DOM which cannot be accessed by standard XPath and CSS locators.
With Provar version 2.1.1, we have enhanced the JavaScript locator so that the default locator for Salesforce web components identifies the shadow DOM from the polyfill used by Salesforce to provide cross browser consistency. As a result, {provarContext} is now appended to the beginning of each JavaScript path when locating elements within a Shadow DOM. This allows ProvarX page object locators to be reused for different occurrences of the same component, based on the enclosing component (which is defined by the enclosing On Screen step). This increases locator reuse across different pages and page sections.
Who does this impact?
This change applies to Lightning Experience users.
Why is this important?
This feature offers additional flexibility for Provar users in how tests can be created and managed. It also provides a mechanism for switching from other testing frameworks already using JavaScript locators so they can be reused in Provar.
How can I use this feature?
You can reference this support article to learn more about using JavaScript locators.
Limitations
There is a limitation in using the By Javascript locator on generic web pages (non-salesforce pages) on the following browsers when interacting with web components using the native Shadow DOM: IE 11.
Test Builder
Edit page object locators in Test Builder
We have made it easier to edit locators using the Test Builder when mapping and testing field details in Salesforce.
In some instances when the Test Builder is not able to select a working or optimal locator by default, you may need to manually select the locator type and parameters to get a unique match. If new locators fail to work as expected, you may need to edit the locator information.
Using the Test Builder, you can see on-screen (and in real-time) the highlighted effect of the configured locator, showing directly whether it matches the target element accurately or not.
Who does this impact?
These changes apply to Lightning Experience and Salesforce Classic users.
Why is this important?
This update simplifies the process of updating field locators by enabling updates directly within the Test Builder.
How can I use this feature?
Pause your test step, right-click the test step within the Test Builder and select Edit Test Step.
Note: The Edit Test Step option will be available for the paused test step and the test step immediately prior. When mapping an existing field, the Edit button will be enabled, though the Edit button will not be enabled for a new field.
Above the Field Details section, click Edit. you will now see the Cancel Edit button. To update information, simply click Edit to modify the information.
Provar Desktop
Secrets file optimization
Prior to 2.1.1, when a connection was deleted the corresponding secrets file entries could be retained in some circumstances but orphaned. We have identified all scenarios where this could occur and improved the functionality of Provar so that these orphaned files are no longer retained.
HTML editor enhancement
We’ve introduced simplified formatting capabilities to help you modify the appearance of test case summaries and remarks. With Provar version 2.1.1, you can use the Atlassian editor (which is familiar to users of Jira) to allow you more real estate to type or paste your notes. We’ve also added a pop-up mode for editing large amounts of contents in the Summary and Remarks in both test cases and Test Plans.
Who does this impact?
All Provar users who optionally elect to leverage this new feature.
Why is this important?
Simplified formatting capabilities enable you to modify text as needed using more screen real estate and an easier interface for editing.
How can I use this feature?
This feature is automatically enabled with 2.1.1 by default. Though there are some backwards compatibility issues. If you encounter an Unsupported Content error message (show below), you can optionally revert back to the prior HTML editor version by adding the following entry into the Provar.ini file:
-Dcom.provar.eclipse.ui.useLegacyContentEditor=true
Above: View of the legacy HTML editor.
Above: View of the new HTML editor.
Above: View of error message if you encounter backwards compatibility issues.
Please reference the Add Permissions to edit Provar.ini file for more information.
General
Chrome 84 compatibility
As part of our pre-release testing due diligence, we are happy to announce that Chrome 84 is compatible with Provar version 2.1.1.
Who does this impact?
Provar customers who are currently using or would like to upgrade to Chrome 84.
Why is this important?
Ensuring that ChromeDriver 84 is compatible with Provar version 2.1.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 84 and use Provar version 2.1.1, you will need to use ChromeDriver 83 or ChromeDriver 84.
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 learn how, 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 using Provar 2.1.1?
Please refer to the Browser and Driver Recommendations support article for a comprehensive guide.
ChromeDriver for 2.1.1
Provar version 2.1.1 is packaged with ChromeDriver v83. We are in the process of testing the ChromeDriver Beta v85 and if any updates are required, we will notify customers in due course by August 25th when Chrome v85 is generally available.
Upcoming feature retirements
Please contact us urgently if you rely on any of the following features.
Messaging connection
When adding a connection, one of the connection types is Messaging. We will soon be retiring the Messaging connection feature within the UI of Provar. This will no longer be visible when creating new connections at some point after Provar version 2.2.0 (Winter ’21). We will still support existing Messaging connections for at least six months afterwards.
In addition, the Test Palette options for Publish Message and Receive Message, which rely on the current Messaging Connection, will also be retired soon after Provar 2.2.0. These will be superseded in a future release with new functionality for testing Salesforce Platform Events and related technology.
ConfigureDX
ConfigureDX was launched in 2017 as a solution to help customers run Provar tests against Salesforce scratch orgs under ANT.
With the general release of ProvarDX, we feel ConfigureDX is no longer an appropriate solution for running Provar projects on scratch orgs and recommend you switch to ProvarDX if you have not already done so.
We plan to start retiring ConfigureDX and remove documentation for it after our 2.2.0 release for Salesforce Winter ’21. It will remain available for use up until our 2.3.0 (Spring ’21) release in January 2021, depending on customer feedback.
Advance notice
License server migration
In response to customer demand, we are planning a migration from our current product license provider to move this facility to be in-house. This migration will:
- Improve license server availability, performance and issue resolution
- Increase flexibility for automatic and temporary license provisioning
- Eliminate the need for a third-party service provider to capture and store license usage information
Currently we are in the planning phase. In the future, we will provide the information you need to whitelist the new Provar licensing server. In this upcoming notice, we will outline all of all of the data that is being captured (unchanged from today). Rest assured, no personal identifiable Information is captured today – nor in future.