We’re excited to announce the latest updates to Provar with the release of version 1.9.12!
In general, we are working hard to give you more flexibility in how you test.
TEST PLANS AND PROVARDX ARE IN OPEN PILOT! With this release, we are inviting customers to help us test two new features that are currently under development.
- Test Plans are designed to help users streamline the testing processes associated with supporting new software releases. With Test Plans, you build multiple Test Plans and run a repeatable collection of tests per each release cycle. You can also make global changes to the environment settings such as browser settings, build number and build server. What’s more, you can get consolidated reports of your results!
- ProvarDX is a custom Salesforce CLI plugin that lets you execute Provar test cases from the command line without requiring installation or use of ANT. ProvarDX can (optionally) be used instead of ANT as part of your CI/CD pipeline or deployment script.
Please note, we are still fine-tuning Test Plans and ProvarDX and we will publish help documentation when they are generally available later this year. In the meantime, you can contact us at [email protected] to learn more about accessing these features and participating in these pilot projects. With your feedback, we can refine these new capabilities and help improve the Provar experience for everyone. Thank you in advance!
Important ChromeDriver update
We are happy to report that Provar v1.9.12 can be used with Chrome v77. Though, we have uncovered an issue with Salesforce and Chromedriver v77. As a result, we do not recommend upgrading manually to Chromedriver v77 at this time and have disabled automatic update of Chromedriver in this release.
Updates at a glance
- Winter ‘20 Support
- Winter ‘20 Support Customization for Contact Role Related Lists
- Winter ‘20 Support Multi Line Edit Delete Icon
- Field Service Lightning
- Dispatcher Console Gantt View
- Support Service Appointment and Service Resource Pop-Up on Dispatcher Console
- Using With Row Actions in List Views and Related Lists in Any Supported Language
- Test Plan Pilot
- Testing Path Assistant in Any Supported Language
- Merge Cases Testing Available on Case View Screen
- Enhanced Related Lists Support
- Test Builder Enhancements
- Edit UI Asserts Within the Test Builder
- Edit UI With Row Test Steps
- Changes to Support Automatic Lightning Enablement
- Salesforce Mobile – Winter ‘20 Changes
- Namespace Prefix Override: Ability to Substitute Multiple Prefixes
- SMTP Path to Be Relative
- Support Sequential Embedded Visualforce Pages
- Winter ‘20 Support
Winter ‘20 support
Provar v1.9.12 has been tested thoroughly against the Salesforce Winter ‘20 release. While it is not mandatory to use Provar v1.9.12 on Winter ‘20 (v1.9.11 also works well) we strongly recommend upgrading to v1.9.12 in order to take advantage of any patch updates we provide during the sandbox preview window.
The good news!
We have continued our ongoing beta testing of Chrome versions and we are happy to report that Provar v1.9.12 can be used with Chrome v77.
The (Temporarily) not so good news
We have, however, uncovered an issue with Salesforce and Chromedriver v77 that has been reported to both Google and Salesforce to stay in accordance with W3C standards. In the meantime, Provar is using Chromedriver v76 for supporting Chrome v77. As part of Provar v1.9.12, we are distributing Chromedriver v76 which is compatible for both Chrome v76 and v77.
The net net
We do not recommend upgrading manually to Chromedriver v77 at this time and have disabled automatic update of Chromedriver in this release.
If you have already enabled the Chrome driver auto-update introduced in Provar v1.9.11, and are applying the upgrade install to v1.9.12, we recommend you disable this setting in your Provar.ini file. You can click here to learn how!
Winter ‘20 support customization for contact role related lists
As part of Salesforce’s Winter ‘20 release, administrators can now customize the columns that appear on the Contact Role related lists for Accounts, Cases and Opportunities in Lightning Experience. Provar has added support for this.
If you were previously testing Contact Role Related Lists you may find that after Winter ‘20 is applied, the columns that appear have changed and tests may fail (correctly). You will need to edit the test cases if this occurs using Provar v1.9.12.
Winter ‘20 support multi line edit delete icon
As part of Salesforce’s Winter ‘20 release, users can now delete Team Members and Opportunity Products using a new delete icon button within the Team Members and Products Add/Edit pop-up. Provar supports interaction with the new delete icon on Account, Case, Opportunity Teams and Opportunity Products.
(Featured Above: View of Add Account Team Members Screen)
(Featured Above: View of Edit Selected Products Screen)
Field Service Lightning: Dispatcher console Gantt view
Using Field Service Lightning, dispatchers can use the Gantt view to easily schedule work and assign those tasks to the right resources.
With Provar, you can now test several features within the Gantt view of open appointments. And, we made it easier to test that functionality!
- Interactions with the Gantt and Map tabs for the purpose of taking screenshots.
- Asserting values at the top of the calendar for total time, travel time, warnings and alerts.
- The total Utilization by Territory can be Asserted for a named row in the scheduler (e.g. Los Angeles or San Francisco).
- A service appointment appearing in the scheduler allows for the capture of a screenshot during a hover.
- A service appointment appearing in the scheduler can be clicked, and the actions listed can be executed as a further test steps.
To learn more about using Provar to test Field Service Lightning capabilities, you can visit our Field Service Lightning support page found here.
Field Service Lightning: Support service appointment and service resource pop-up on dispatcher console
We have expanded our support of Field Service Lightning. You can now use the Test Builder using your normal workflows to test the pop-up windows that appear within the Dispatch Console when users create or edit Service Appointments or Service Resources.
Using with row actions in list views and related lists in any supported language
Previously, With Row actions for list views and related lists could only be executed in English or the default language of the administrator access user for Provar. You can now map and execute these actions in any supported language irrespective of the admin user’s language.
To learn more about the languages supported by Provar, you can visit our Internationalization Testing of Salesforce page.
Test Plan pilot
With the release of 1.9.12, we are launching a new pilot for Test Plans. Test Plans are designed to help users streamline the testing processes associated with supporting new software releases. With Test Plans, you build multiple Test Plans and run a repeatable collection of tests per each release cycle. You also have the ability to make global changes to the environment settings such as browser settings, build number and build server. What’s more, you can get consolidated reports of your results.
How are test plans different than test cycles?
Test Cycles can help you group tests together and execute basic functions such as rerunning failed tests. Test Plans provide more advanced configuration options and are designed specifically to help support your CI/CD business objectives.
Why should I use test plans?
Test Plans are designed to help teams support an accelerated software release cycle in two primary ways.
- Test Plans help you reuse existing test cases and make it easier to find and select existing test cases and add them to your Test Plan.
- Test Plans help you make global changes to the Test Cases that are within each Test Plan – eliminating the need to open and edit each Test Case individually.
We will provide more help documentation when Test Plans are made generally available later this year.
Testing Path Assistant in any supported language
As part of our commitment to supporting customers worldwide, you can now map and execute tests involving the Path Assistant feature within the Test Builder in any supported language.
To learn more about the languages supported by Provar, you can visit our Internationalization Testing of Salesforce page online.
Merge cases testing available on case view screen
In addition to the support we added previously for the Merge Case button on the Case List View you can now test the functionality associated with the Merge Cases button from the Case Record View page and map and test all fields on the Case View screen using your normal workflows.
(Featured Above: View of Merge Case Button)
(Featured Above: View of Compare Cases Screen)
Enhanced related lists support
As part of the Salesforce Summer ‘19 release, administrators can (optionally) choose to display a Related List in the existing default mode or use the new Enhanced Related Lists display that allows you to display up to 10 columns, resize and sort your columns, perform mass actions, and wrap text.
Provar now supports the testing of this new display.
Note: Users who switch to Enhanced Related Lists will need to edit existing Provar tests to ensure they continue to function correctly.
Test builder enhancement: Edit UI asserts within the test builder
UI Assert is designed to help you assert values, messages and attributes on a screen. We updated this functionality to give you more control when building tests using the Test Builder. Instead of having to toggle to Provar Desktop, you can now edit various aspects of a UI Assert when creating or editing a test case directly within the Test Builder.
What’s new in the Test Builder?
- Checkboxes for Extract/Assert are now enabled
- Expected Values, Message and Attributes are editable
- Expected values now support Content Assist
- When present, the column checkboxes and attributes are editable
- The screenshot options are also editable
Test Builder enhancement: Edit UI with row test steps
You can also now amend the row attributes of any UI With Row test step and configure the settings associated with that test step directly within Test Builder.
(Featured Above: View of UI With Row Editing Within Test Builder)
Changes to support automated Lightning enablement
As part of the Winter ‘20 release, Salesforce is now enforcing switching users automatically on a weekly basis from Classic to Lightning if the user has been enabled for Lightning Experience.
To help you save time and simplify testing, we’ve made several changes that are designed to help you navigate testing instances of Salesforce Classic and Salesforce Lightning.
Provar now automatically detects whether you have a Classic or Lightning connection. (Note, you don’t have to make any changes to take advantage of this new feature).
Provar will also now default to lightning enabled when you add a new SF Connection or create a new Salesforce project.
When creating a new test case, or when adding a SF Connection step to an existing Test Case, you will now find that the Application is mandatory. The application is a good indicator of whether you’re testing in Lightning or Classic mode, but does not in itself force Salesforce to run in the intended mode.
To help you avoid wasting time or abandoning tests that are running in Lightning (when you actually want to test in Classic mode), you will see the test case fail at the first instance when the browser is open if we detect you’re not running in the intended mode.
We recommend that when planning tests to run in both Classic and Lightning that you now use separate Salesforce users, the Classic one should have Lightning Experience disabled. This will avoid runtime issues when Salesforce switch the user experience automatically. You can leverage Environment Overrides to switch between Classic and Lightning users without having to modify your test cases. Please see our Lightning Quick Start guide.
With these changes, you can get peace of mind that the tests you are building will work correctly in the environment you intend.
Salesforce mobile – Winter ‘20 changes
As part of their Winter ‘20 release, Salesforce made available several changes that were previously in open pilot. These include:
- The ability to customize Flexipages and set components to be visible based on the device type of Phone (not Mobile, see below) and Desktop.
- The ability to create separate Flexipages by device type of Phone, Desktop or Both. Existing pages default to Both.
- A new Salesforce Mobile experience that can be enabled for individual users. This allows a greater amount of customization, the inclusion of Lightning Components and an overall improved user experience consistent with the Lightning desktop view. This feature can be enabled on a user or profile basis.
- Enhanced offline data support for the latest Salesforce Mobile application for iOS and Android.
- The new Salesforce Mobile beta app is available via TestFlight and will be distributed on the relevant App Stores October 14, 2019.
In addition to these changes, Salesforce announced the following restrictions will be introduced in the near future:
- The new Flexipages and Component filtering for Device Types do not render when Salesforce Mobile is accessed via a web browser view. The original Salesforce Mobile experience is rendered instead.
- Accessing Salesforce via an iPad device browser will render pages in the Desktop view, not the Salesforce mobile view. The Salesforce mobile app can still be used on iPads and works with Lightning on Mobile.
- Accessing Salesforce via a desktop browser in mobile emulation will no longer render the Salesforce Mobile view.
- Accessing Salesforce via a phone browser will redirect users to the relevant app store to download the mobile application instead.
What does this mean for Provar users?
Once these changes are made, Provar, together with all other test automation tools, may no longer be able to support meaningful testing of Salesforce Mobile until Salesforce makes available a developer signed build of their mobile application. The timing of the above restrictions being enforced has not yet been communicated by Salesforce and existing Salesforce Mobile tests will continue to work in Provar until these restrictions are enforced, which we expect to be soon after October 14 2019.
We recommend you speak to your Salesforce Customer Success team if these changes may adversely affect you.
Namespace prefix override: Ability to substitute multiple prefixes
Prior to v1.9.12, we provided the ability to remove multiple namespaces and add a single namespace so that the same tests can be run across similar packages using different org or package namespaces. As part of our v1.9.12 release, you can now execute multiple individual substitutions of the namespace prefix.
- Each substitution set can be separated by |
- You can combine namespace removal/addition with namespace substitutions
- -ns1,-ns2, +ns3 will strip all ns1 prefixes and ns2 prefixes and add ns3 prefixes (as previously)
- -ns1,+ns2 | -ns3,+ns4 will replace all ns1 prefixes with ns2 prefixes and all ns3 prefixes with ns4 prefixes
- -ns1 | -ns2,+ns3 will remove all ns1 prefixes and substitute all ns2 prefixes with ns3
See provartesting.com/documentation/testing-with-provar/defining-a-namespace-prefix-on-a-connection/ for a full description of how Namespace Overrides can be used.
SMTP path to be relative
Previously the email configuration to send an email post execution stored the SMTP folder in /Provar. When using a CI server such as Jenkins, or running Provar in a Docker container, which do not have access to the root folder, this would cause the email to fail with no mechanism to amend.
With v1.9.12, the SMTP folder can be stored in a folder such as ProvarHome and the path can be passed in the ANT build.xml or ProvarDX properties without having to specify the full file specification. The scope of this change includes Docker, CI/CD Tools, ANT and ProvarDX.
Support sequential embedded Visualforce pages
You now have more flexibility when testing Visualforce pages. You can choose the index of a particular Visualforce component within a page using the Page Index setting. Prior to this change, Provar would automatically select the first Visualforce component within the page.
Note: This can only be configured through Provar Desktop and is not currently available via Test Builder.
- 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
- 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.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