Version 2.4.0 Summer ’21
The latest release of Provar version 2.4.0 is now available in the Provar Success Portal. In general, this release is designed to ensure compatibility with the Salesforce Summer ’21 release.
2.4.0 at a glance:
- This release ensures compatibility with the Salesforce Summer ’21 release to keep your tests working as expected.
- Provar compatibility updates for Summer ‘21, including guidance about any instances where your test cases may require revision.
- Added an option to export test execution reports without including any logging information.
- Chrome 90 compatibility.
Want to know more?
Please join us on May 18 for our What’s New in Summer ’21 webinar. In this webinar, we’ll share the most impactful Summer ‘21 changes that you must be acquainted with, share the latest from Provar with news from the University of Provar, a review of the Salesforce OAuth connection feature and how to get some of the brand new Provar swag. Click here to register!
Access world-class customer support at the Provar Success Portal
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.4.0, please get in touch with us and we would be happy to help. To raise a case, simply log into the Provar Success Portal and click View/Raise Case.
Salesforce Summer ’21 support
Summer ’21 general compatibility
Provar version 2.4.0 is compatible with the Salesforce Summer ’21 release. You can learn more about the release here.
The following includes a list of Summer ’21 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.4.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 90 compatibility
As part of our pre-release testing, we are happy to confirm that Chrome 90 is compatible with Provar version 2.4.0.
Who does this impact?
Provar customers who are currently using or would like to upgrade to Chrome 90.
Why is this important?
Ensuring that ChromeDriver 90 is compatible with Provar version 2.4.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 90, we recommend that you upgrade to Provar version 2.4.0 which will use ChromeDriver 90 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.4.0?
Please refer to the Browser and Driver Recommendations support article for a comprehensive guide.
Packaged ChromeDriver for 2.4.0
Provar version 2.4.0 is packaged with ChromeDriver 90.
Further Enhancements to Report Generation
As part of our continued logging framework enhancements and building upon the report generation features we introduced in the 2.3.1 release, we’ve now added an additional option to generate test execution reports with no logging included. This is via an additional selection, “No Logging” which you will see alongside the existing Basic, Detailed and Diagnostic options.
Who does this impact?
Provar users will now see the revised logging levels, with the new “No Logging” option, in the report configuration screens.
Why is this important?
This change uses our new logging and report generation framework, and introduces the capability to produce reports without including any logging information.
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.
Salesforce ICU Format
In the Winter ‘20 release, Salesforce began to roll out support for the ICU locale formats, to replace the Oracle Java 8 formats previously used. Some information is available on Supported Locales and ICU Formats and Enable ICU Locale Formats.
This change is currently optional for existing orgs but will be made mandatory in Spring ‘22. To prepare for this, we are building native support into Provar for the ICU date/time format and we plan to make this generally available in an upcoming release. Before this, if you enable ICU or experience any unexpected issues with processing ICU local format fields then please contact us at Provar Success Portal and our team will be happy to help.
REST Service Response Update
We have resolved an issue with the response data formatting with REST calls which we identified following our 2.2.0 release. The JSON-format data will now correctly provide error response details. If you had implemented a workaround for this issue, then you may need to update your response processing to function as expected. If you would like to have further detail then please contact our world class support team at Provar Success Portal.
- 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
- Guide in Salesforce CPQ Testing in Provar
- Guide in ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Provar Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- 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
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Provar CI Task
- 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 Continuous Integration
- Travis CI
- Execution Environment Security Configuration
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team foundation server
- Version control
- 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
- Performance Best Practices
- 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
- Version 2.8.0 Winter ’23
- Version 2.7.2
- Version 2.7.0 Summer ’22
- Version 2.6.3
- Version 2.6.0 Spring ’22
- Version 2.5.0 Winter ’22
- Version 2.4.1
- Version 2.4.0 Summer ’21
- Version 2.3.1
- Version 2.3.0 Spring ’21
- Version 2.2.1
- Version 2.2.0 Winter ’21
- Version 2.1.1
- Version 2.1.0 Summer ’20
- Version 2.0.5
- Version 2.0.4
- Version 2.0.3 Spring ’20
- Version 1.9.12
- Version 1.9.11