Version 2.3.0 Spring ’21
Executive summary
The latest release of Provar version 2.3.0 is now available in the Provar Success Community. In general, this release is designed to ensure compatibility with the Salesforce Spring ’21 release.
2.3.0 at a glance:
- This release ensures compatibility with the Salesforce Spring ’21 release to keep your tests working as expected
- We’ve made it easier to use BrowserStack with Provar
- Support for Dynamic Forms in Provar Test Builder and Provar Desktop
- Testing recommendations for Salesforce Release Updates
- Chrome 88 compatibility
Learn more about the Spring ’21 Salesforce release
Please join us January 14 for our What’s New in Spring ’21 webinar. We’ll provide information about Provar enhancements with version 2.3.0, new Salesforce features, our latest recommendations for testing Salesforce Release Updates and information about the University of Provar. Click here to register!
Access world-class customer support at the Provar Success Community
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. If you have any questions regarding 2.3.0, 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.
Salesforce Spring ’21 support
Spring ’21 general compatibility
Provar version 2.3.0 is compatible with the Salesforce Spring ’21 release. You can learn more about the release here.
As a Salesforce first 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 the Provar and Salesforce prerelease Business Scenario Testing (BST) program.
The following includes a list of Spring ’21 updates that Salesforce introduced that we have addressed. Your existing Provar tests that use standard components will continue to perform as expected.
Note: If you have created custom page objects related to items impacted by these updates, you may need to update existing Provar tests.
Salesforce Release Updates
Salesforce Release Updates for 2.3.0
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 Release 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.
BrowserStack
Local testing with BrowserStack
If you use BrowserStack to expedite release cycles and deploy websites and mobile applications, you can now integrate Provar with BrowserStack further to simplify testing for web and mobile applications only accessible within your network. With Provar version 2.3.0 and onward, you can set BrowserStack capabilities for local testing using the browserstack.localIdentifier capability as an environment variable or command line argument.
Who does this impact?
Provar users leveraging BrowserStack.
Why is this important?
This feature helps to enable testing of local web and mobile applications currently under development or only accessible within your corporate network.
How can I use this feature?
To find step-by-step instructions for enabling this feature and additional information about using Provar with BrowserStack, please refer to the BrowserStack Desktop support article.
Overriding BrowserStack credentials
Using Provar version 2.3.0 and onward, you can override BrowserStack browser provider credentials as an environment variable or a command line argument. This is helpful when executing tests as part of your CI/CD build pipeline using ANT. Overriding the username and access key in Provar eliminates the need to store the Provar .secrets file on the execution server when executing Provar via ANT.
Who does this impact?
Provar users leveraging BrowserStack.
Why is this important?
This feature helps to simplify and streamline testing by reducing manual test maintenance and configuration while maintaining data integrity.
How can I use this feature?
To find step-by-step instructions for enabling this feature and additional information about using Provar with BrowserStack, please refer to the BrowserStack Desktop support article.
Note: This feature is not supported by ProvarDXTM at the time of this release.
Dynamic Forms
Dynamic Forms support using Test Builder and Provar Desktop
In 2020, Salesforce launched Dynamic Forms to create user-friendly page layouts. To avoid overwhelming users with information, you can add visibility rules to make fields and components appear and disappear based on the criteria you specify.
Using Provar version 2.3.0 and onward, you can use Provar Test Builder and Provar Desktop to test fields within pages that are configured using Dynamic Forms.
Who does this impact?
Salesforce Lightning users who have enabled Dynamic Forms.
Why is this important?
Using Provar version 2.3.0 and onward, you can map, interact and assert fields that are part of Dynamic Forms.
How can I use this feature?
You can create and maintain Provar tests that include Dynamic Form components as you would normally. You can follow standard Provar testing procedures.
Dynamic Forms support for legacy tests
With Provar version 2.3.0 and onward, test cases created prior to enabling Dynamic Forms will continue to work, which eliminates the hassle of updating your existing library of regression tests. Existing tests that interact and assert properties that are now present within dynamic forms will continue to work as expected.
When executing legacy test cases with Provar version 2.3.0, you may see that some test cases are displayed in an unsaved state even if you haven’t made any changes to the test. Provar will display a dialog box prompting you to either save the changes or ignore the changes. To keep your tests running as expected, we recommend that you simply click Save Changes. Note: This only impacts tests for Field Service Lightning (FSL).
Browsers
Chrome 88 compatibility
As part of our pre-release testing due diligence, Chrome 88 is compatible with Provar version 2.3.0. We have included ChromeDriver 87 in the 2.3.0 distribution.
Who does this impact?
Provar customers who are currently using or would like to upgrade to Chrome 88.
Why is this important?
Ensuring that ChromeDriver 88 is compatible with Provar version 2.3.0 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 88 we recommend that you upgrade to Provar version 2.3.0, 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.3.0?
Please refer to the Browser and Driver Recommendations support article for a comprehensive guide.
Packaged ChromeDriver for 2.3.0
Provar version 2.3.0 is packaged with ChromeDriver 87.
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- Functions
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reload Org Cache
- Reporting
- Running tests
- Searching Provar with find usages
- Secrets management and encryption
- Setup and teardown test cases
- Tags and Service Level Agreements (SLAs)
- Test cycles
- Test plans
- Testing browser options
- Tooltip testing
- Using the Test Palette
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript locator support
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- ProvarX™
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- DevOps
- Introduction to test scheduling
- Apache Ant
- Configuration for sending emails via the Provar Command Line Interface (CLI)
- Continuous integration
- AutoRABIT
- Azure DevOps
- Running a Provar CI task in Azure DevOps
- Configuring the Provar secrets password in Microsoft Azure Pipelines
- Parallel execution in Microsoft Azure Pipelines using multiple build.xml files
- Parallel execution in Microsoft Azure Pipelines using targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- Circle CI
- Copado
- Docker
- Flosum
- Gearset
- GitHub Actions
- Running a Provar CI task in GitHub Actions
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using multiple build.xml files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab CI
- Jenkins
- Travis CI
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team foundation server
- Version control
- Zephyr Cloud and Server
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Dynamic Forms
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Testing best practices
- Troubleshooting
- Release notes