We’re excited to announce the latest updates to Provar with the release of version 1.9.11.
NEW FEATURE! With this release, one of the most exciting new features is designed to make it easier to create tests all within one workflow. Using Provar 1.9.11, you can now edit test steps directly within the test builder.
Goed nieuws! We’ve also added several new capabilities that are designed to support the use of Provar in other languages in addition to English. And, as part of 1.9.11, we’ve also created new reporting options for Micro Focus Application Lifecycle Management (ALM) users and expanded our smart testing support for Field Service Lightning.
It’s also worth noting that starting in September, Salesforce will be enforcing all API connections to use TLS 1.2 to enhance information security. This impacts all Salesforce developers that use integrated applications like Provar. We’ve included some information about what you need to do to ensure that your systems continue to work without interruptions.
Updates at a Glance
- Editing Test Steps Within the Test Builder
- Enhanced Multi-Lingual Support
- Improved Execution Time When Testing the Activity Timeline
- Advanced Reporting Options Now Available for Micro Focus Application Lifecycle Management (ALM) Users
- New Function: GetSelectedEnvironment()
- Salesforce Update: Transport Layer Security (TLS) Requirements
- Summer ’19: Lightning Activity Timeline and Related List View
- Field Service Lightning Testing: Dispatcher Console and Appointments View
- Support for Related Lists and Record Details Added to a Custom Tab
- Chrome Driver Updates
- [New Field] Time Field Timestamp
Editing Test Steps Within the Test Builder
We understand that you need greater flexibility to quickly create and modify test cases. That’s why we updated Provar to give you more tools at your fingertips. In Provar, you can now modify various attributes associated to all action test steps on both standard and custom pages.
And, you can do that within the Test Builder itself. Previously, users were required to toggle to the main Provar desktop application to modify test steps. Now you seamlessly make necessary changes within your existing workflow – helping you save valuable time while building new test cases.
We’re also working on giving you even more flexibility. In the future, we are expanding this editing functionality to include additional test steps such as the User Interface (UI) assert and row selectors.
To help you avoid accidentally changing a test, the edit functionality is only enabled if the test case is in a paused state. This is disabled when any test step is actively executing.
Here is an example of how this now looks in Provar.
Enhanced Multi-Lingual Support
We’ve made several updates to make it easier to use Provar when testing your systems that are designed in languages other than English. When downloading your system’s metadata, Provar will now maintain that information in the supported language for the connection being used and not automatically convert it to the system administrator’s default language.
You can also now map and test weblinks in any supported language. (Previously, this defaulted to the admin user’s language.) We’ve also updated the system to support record type labels in languages other than English. And lastly, you can now also map related list quick links within the Test Builder in any language.
To take advantage of these new features, you don’t need to modify anything in Provar. These are available automatically.
PRO TIP: Provar currently supports Dutch, German, Italian, Portuguese, Spanish, French and Swedish. And, we will be supporting even more languages in the future. You can learn more about testing Salesforce in various languages at the Internationalization Support page.
Improved Execution Time When Testing the Activity Timeline
In order to improve system performance, we’ve made a few changes that are designed to help you save time and boost efficiencies. Specifically, when managing tests that involve an activity timeline in Salesforce. Provar can now execute those tests more quickly by searching your metadata more efficiently.
Advanced Reporting Options Now Available for Application Lifecycle Management (ALM) Users
You can now configure reporting options for Micro Focus ALM (formerly HP ALM) through provarSettings.xml.
By adding a new tag in the provarSetting.xml file, you can specify the reporting options that you require. After applying the following settings, your reports will be uploaded to ALM based on the reporting options specified.
How To Update provarSetting.xml
1. Open ALM in InternetExplorer.
2. Navigate to ‘Test Plan’ Section.
3. Select the Home Folder(Subject) and Download the ProvarSetting.xml(can be found form attachments Tab) in to your local machine.
4. Open the ProvarSetting.xml file in any editor (E.g. Notepad).
5. Add the “executionReportOptions” tag (See below.)
<executionReportOptions includeAllFailuresInSummary="false" includeOnlyFailures="true" includeOnlyBdd="false" includeSkipped="false" includeTestCaseDescription="false" includeScreenshots="false" includeWarningMessages="false" includeInfoMessages="false" includeDebugMessages="false" includeTestStepTime="false" includeTestStepPathHierarchy="false" includeFullScreenShot="false"/>
6. Save the .xml file and replace the same with your existing provarSetting.xml present in attachment section of ‘Test Plan’ Home folder
7. Execute your script using “Run under ALM” option to get the customized script in ALM.
It is not mandatory to add these reporting options in provarSettings.xml. If nothing is added to the xml, Provar will use your default values.
PRO TIP: To learn more about using Provar with ALM, you can also visit provartesting.com/documentation/devops/reporting/micro-focus-hp-alm/.
New Function: GetSelectedEnvironment()
A new function GetSelectedEnvironment() will be available in the list of functions. You can use this in the same way that you typically use other functions when building test cases in Provar.
The purpose of this function is to return the selected test environment in Provar. You can also learn more about using this, and other functions within Provar, on the Using Functions page found here.
Why did we create this new function? It can be helpful to solve a number of challenges when building complex tests. For example, you can use this function when you need to map your test case in different test environments (e.g. Test, Sandbox, Production, etc.). This gives you increased flexibility to reuse test cases when you expect different results for a given environment.
Salesforce Update: Transport Layer Security (TLS) 1.2 Support
Salesforce is making a change to their core platform to align with industry best practices for security and data integrity.
Starting in September, Salesforce will be enforcing all connections to use TLS 1.2 or above. Provar has been using TLS 1.2 since version 1.8.x and we’ve verified their are no issues from our side when this is enforced.
To avoid issues and continue using Provar for testing your custom applications and integrations, please check if you are using TLS 1.1 to make connections to Salesforce. If so, please upgrade to TLS 1.2. You can learn more by visiting this page on Salesforce.com.
Summer ‘19: Lightning Activity Timeline or Related List View
As part of a recent Summer ‘19 Salesforce update, system administrators can now change the behavior of the Lightning Activity Timeline. Users can now render the information as a related list, similar to how the information is displayed in Classic mode.
Provar now supports the testing of Salesforce in this new format.
Field Service Lightning Testing: Dispatcher Console and Appointments View
We are continuing to expand our support of testing Field Service Lightning (FSL). The FSL Dispatcher Console gives users the ability to easily schedule appointments across multiple resources.
As part of this latest release, you can now assert, map, highlight and execute changes associated with this module for the left hand navigation panel of the Dispatcher Console page.
- The policy dropdown
- The service appointment list view
- The match Gantt dates checkbox which can be set, unset or toggled using Provar
- A service appointment row can be selected using set, unset, or toggle
- Multiple service appointment rows can be selected using set, unset or toggle
- Column values in the service appointment list view can be asserted
- The schedule button can be clicked and the results of the action asserted
- The dispatch button can be clicked, and you can map and execute steps on the Bulk Dispatch modal form using any of the controls
- The results of the bulk dispatch can be asserted (e.g. no service appointments found).
- The optimize button can be clicked, and you can map and execute steps on the Optimize modal form. Note this is similar to the Dispatch form above.
- The unschedule button can be clicked and you can map and execute steps on the bulk unschedule modal form. Note this is identical to the dispatch form above.
- After unscheduling, the result list of the action can be asserted
Please note, we are working on delivering further enhancements for interaction with the right hand side appointment Gannt view in our next release.
Test Builder Mapping of Dispatcher Console Page
Test Builder Mapping of Field Service Appointments Type Selection
Test Builder Mapping of Field Service Appointment Selection
Test Builder Mapping of Field Service Appointment Service Territory Selection
Test Builder Mapping of Field Service Appointment Parent Record Type Selection
Provar Desktop View
Test Builder Execution
Support for Related Lists and Record Details Added to a Custom Tab
You can now map and execute the related lists and record details added to a custom tab in a Lightning page. Previously, Provar would only automatically recognise Related Lists and Detail Lightning components when in the default tabs (Details and Related) or on the main flexipage.. Provar now automatically recognises these components when they are in a custom tab regardless of the tab name.
Custom Fields Within a Lightning Page
Chrome Driver Updates
We proactively test beta releases of Google Chrome and have identified a potential issue that may impact you.
In order to make this as seamless as possible for you to use Provar 1.9.11, we have enabled a Chrome driver auto update for Chrome versions 76 and above.
What does that mean?
Fewer headaches for you! Provar can now automatically detect if a new Chrome web driver is required and attempt to download it for you.
How will I know if Provar is updating my browser?
If Provar needs to install a new web driver, you will see the following message.
I don’t want Provar to automatically install a new web driver. How can I disable this?
You can disable this auto-update by setting the following provar.ini property.
You can learn more about adding permissions to edit provar.ini files online here.
What if my computer doesn’t allow for auto-updates?
If you have restricted API calls to third-party websites, you may find the auto-update is blocked. It it is blocked, you will see the following message in Provar:
“Failed to launch chrome as could not download compatible driver, cause: Timeout while copying the files for driver with 180 seconds.”
To fix this either whitelist the Chrome Driver update URL or manually download and install the required Chrome driver when prompted to do so. For further information on manually updating Chrome drivers please see the following article.
IMPORTANT NOTE: Google Chrome (Version 76) will be released on July 30th. To ensure that you don’t experience temporary disruptions in service, please upgrade to Provar version 1.9.11 if you also upgrade to Chrome (Version 76), or if you have auto-update enabled for Google Chrome. Provar 1,9.11 also supports Chrome version 75.
You can continue to use earlier versions of Provar (such as 1.9.10) if you are using Chrome 75 (and below).
[New Field] Time Field Testing
Salesforce recently made a new feature generally available and we’ve made it easier to test that functionality in Provar.
Classic and Lightning users can now use a time field for time management, event planning, and project management. The time field type is a timestamp that is not associated with a specific date. You can use it to document things like business operating hours or staff schedules.
You can map this new field to your tests in Provar more efficiently using your normal workflows.
- 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