Version 2.6.0 Spring ’22
We’re happy to announce the latest updates to Provar with the release of version 2.6.0. The latest release of Provar version 2.6.0 is now available in the Provar Success Community. This release ensures compatibility with the Salesforce Spring ’22 release to keep your tests working correctly with all the latest Salesforce updates.
2.6.0 at a glance:
- Provar compatibility updates for Spring ‘22, including guidance about any instances where your test cases may require revision.
- Chrome 96 and 97 compatibility, keeping you up-to-date with the latest versions for Chrome for test authoring and execution.
- Assert Step UI condition is redesigned
Access world-class customer support at the Provar Success Community
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. If you have any questions regarding 2.6.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 ’22 support
Spring ’22 general compatibility
Provar version 2.6.0 is compatible with the Spring ‘22 Release. You can learn more about the release here.
The following includes a list of Spring ’22 updates that Salesforce introduced that we have addressed. Your existing Provar tests that use standard components will continue to perform as expected.
Salesforce Release Updates
Salesforce Release Updates for 2.6.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.
Chrome 96 and 97 compatibility
As part of our pre-release testing, we are happy to confirm that Chrome 96 and 97 are compatible with Provar version 2.6.0.
Who does this impact?
Provar customers who are currently using or would like to upgrade to Chrome 96 and 97.
Why is this important?
Ensuring that ChromeDriver 96 is compatible with Provar version 2.6.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 96 or 97 we recommend that you upgrade to Provar version 2.6.0, which will use ChromeDriver 96 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.6.0?
Please refer to the Browser and Driver Recommendations support article for a comprehensive guide.
Packaged ChromeDriver for 2.6.0
Provar version 2.6.0 is packaged with ChromeDriver 96.
Assert Test Step Condition UI is redesigned
We’ve redesigned the UI for the Assert test step condition to improve your experience. The field labels and the sequence of fields are changed. Test Builder is also updated in the same way as the UI change in the Provar Desktop.
Who does this impact?
All Provar users who currently use or will use the Assert test step in their test cases.
Why is this important?
This is a UI design change in the Assert test step and Test Builder is also updated in the same way to match the Provar Desktop. Please note that existing Provar tests will not be impacted by this change.
How can I use this feature?
The UI redesign in the Assert test step is as given below:
- Result: this is the execution result of the test step, such as a value you read from Salesforce in a test step.
- Target: this is the predetermined target value against which the result is checked against using the operator.
- Operator: this is used to compare the Result to the Target. The operation reads in the order in which it is presented on screen. As an example, if the Target is 5 and the Operator is >, then for the test step to pass, the Result must be > than 5. A Result of 8 would pass the step; a result of 4 would fail the step.
Above: View of UI redesign in the Assert test step.
Testing compatibility with Einstein Search
We have made an update so that when you enable Einstein Search, any existing tests that cover the Salesforce search capability will continue to work correctly with Einstein Search going forwards, without any need to modify your existing tests.
Page error assertion change on legacy test cases for the Opportunity object
Salesforce has changed the page validation message on the Opportunity object. You may notice this change when you will create a New Opportunity in Salesforce. If you have tests doing a UI Assert on the New Opportunity validation message, you may need to edit the existing test cases with the new validation messages to keep your test working as expected. For more information on how to edit your test cases, please see Update on Opportunity field validation
- 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
- 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
- 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
- Test Palette introduction
- Control test steps
- List compare
- Read test step
- String test steps
- UI Test Steps
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Salesforce CPQ testing
- ServiceMax testing
- Skuid testing
- Vlocity testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for sending emails via the Provar Command Line Interface (CLI)
- Continuous integration
- 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
- 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
- Travis CI
- Execution Environment Security Configuration
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- 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
- Configurations and permissions
- Error messages
- Administrator has blocked access to client
- macOS Big Sur upgrade issue
- Resolving failed to create ChromeDriver error
- Resolving Jenkins license missing error
- Resolving metadata timeout errors
- Test execution fails – Firefox not installed
- Update to Opportunity field validation behaviour
- Licensing, installation and firewalls
- Test Builder and test cases
- Release notes