V2 Spring '26 Release 1 (v2.18.1)
Executive Summary
We’re excited to announce the latest enhancements with the Provar Spring ’26 Release 1(v2.18.1). This release strengthens license governance, enhances stability, and improves usability across Provar Automation. Execution License enforcement now ensures licenses are used correctly, allowing CLI-only usage while preventing UI access. V2 introduces automatic Page Object refactoring, eliminating manual updates and reducing maintenance effort.
Users can configure Test Cycles for Test Plans with Provar Quality Hub reporting while maintaining existing reporting behavior. Security is enhanced with encrypted password variable support across Expression Editors. V2 now automatically handles Edge driver mismatches, and Permission Set Group details are included in layout extraction for more complete access visibility.Overall, this release focuses on stronger control, improved reliability, better security, and simplified test maintenance. You can download and install this release from the Provar Success Portal directly.
Mandatory Installation Instructions
This release includes a major platform upgrade, moving Provar to an Eclipse 4.36-based RCP application. The new base provides significant security improvements, enhanced stability, and better long-term support while maintaining compatibility with existing workspaces.
- Although the application remains compatible with existing workspaces, we recommend creating a new workspace.
- Users must delete the UserHome/Provar/.configuration folder or rename them if a backup is needed.
- Delete UserHome/Provar/.chromeProfiles folder mandatory only if they chose Edge Browser as Test Authoring option.
Spring ‘26 Compatibility
| Change Area | Impact Summary |
| Secondary Tabs Navigation – DOM Class Change | In Spring ’26, Salesforce updated the DOM class for secondary tab navigation. The element class changed from slds-tabs–default__nav to slds-tabs_default__nav. This caused failures where the “Secondary Tab” value was not populating. Provar handles this change, and existing scripts continue to work without additional effort. Custom implementations for tab switching that rely on hardcoded DOM classes may require review and updates. |
| Checkbox Rendering on New/View/Edit/Inline Edit Screens | Spring ’26 introduced a structural change in checkbox rendering across New, View, Edit, and Inline Edit screens. The traditional tag has been replaced with lightning-primitive-input-checkbox. This resulted in execution failures for checkbox interactions. Provar support aligns with the new Lightning primitive; custom scripts or locators relying on direct tags may require updates. |
| FieldServiceSettings Query Exception | In Spring ’26 jar is introducing a new element ‘enableServiceAppointmentLifecycle’, leading to an exception: “Exception while querying FieldServiceSettings: unable to find end tag”. This is a tooling-level issue and will be resolved once the underlying jars are upgraded to API version 66. For now exception has been absorved, and hence no script-level changes are required. |
| FSL Product Request – Related Object API Name Change | In Spring ’26, the Product Request reference API name is appearing as Parent__c, whereas earlier it appeared as ProductRequestId. This has impacted navigation from Detail pages to Related Lists in Field Service Lightning. This behavior may be addressed in future Salesforce patches, otherwise, affected steps may need to be recreated using the updated API name. |
| Advanced Search – Object Mapping Issue | In Spring ’26, the Advanced Search window mapping behavior changed due to the removal of the targetApiName property from the lightning-modal DOM, which was previously used to resolve the object API name. Provar handles this change in this release, and existing scripts continue to work without disruption. |
| Global Advanced Search – Default UI Behavior Change | In Spring ’26, the Global Search default view behavior has changed. The Search Filter panel is no longer visible by default and is now available only after clicking into the search bar. This may impact automation flows where the first interaction targets the Search Filter, and test steps may need adjustment to explicitly activate the search bar before applying filters. |
Spring ’26 – CPQ
Provar is now compatible with the latest CPQ package version 260.2 introduced in the Salesforce Spring ’26 release. This compatibility ensures that existing Provar test cases will continue to run without interruption. No updates are required for the existing Provar test cases.
Provar Automation Features and Enhancements
Execution License Usage Enforcement in Provar UI
With this release we are introducing stricter controls to ensure Execution licenses are used only for CLI-based execution and not for launching or using the Provar UI. Attempting to use an Execution license in the UI will fail with a clear error message, while CLI execution continues to work as expected.
The enforcement applies to both new execution licenses and existing activated execution licenses. The Execution license will continue to work for CLI execution. Developer (floating) licenses continue to support both UI and CLI usage.
Refactored Page Object Management
Provar Automation V2 now automatically updates all references when Page Objects are renamed or moved within the project. This enhancement removes the need for manual adjustments and ensures full consistency across test cases making your test maintenance simpler, faster, and error-free.
The benefits of Page Object Refactoring include:
- Zero manual updates: Users no longer need to track or correct references after renaming or moving Page Objects.
- Error-free refactoring: No errors in test cases or execution logs due to Page Object updates.
- Backward compatibility: All existing (legacy) test cases and scenarios will continue to work without any impact.
- Improved maintainability: Refactoring is simpler, safer, and faster.
Configure Test Cycle for Test Plans using Provar Quality Hub reporting
Added support for configuring Test Cycles for Test Plans using Provar Quality Hub reporting. Users can now organize and execute tests within a defined Test Cycle while continuing to generate consolidated execution reports in Provar Quality Hub with no change to existing reporting behavior.
Encrypted Password Variables in Expression Editors
Password variables can now be securely used across all Expression Editors, including Web Services, Custom APIs, Page Operations, and Custom Test Steps. This enables encrypted credentials such as Client ID and Client Secret to be safely injected into request bodies (including JSON) for both REST and SOAP calls.
The enhancement ensures that sensitive values remain fully encrypted and are never exposed in logs, runners, or network requests, while continuing to work seamlessly with encrypted projects and environments.
Automatic Edge Driver Download for Version Mismatch Scenarios
Provar Automation V2 now comes bundled with the latest stable Edge driver and automatically downloads the correct version if a mismatch is detected i.e. during Authoring or Execution.This enhancement ensures a seamless testing experience by preventing browser–driver compatibility issues from blocking Run, Debug, or Test Builder workflows.
Add Permission Set Group Information while extracting the layout information
Added support to include Permission Set Groups in extracted layout details alongside existing Profile and Permission Set information. Users can now view a more complete layout coverage across both Record Layout and DF Layout without impacting existing functionality.
Browser Compatibility Updates
Browser and Driver Combinations Recommended for Provar Automation v2.18.1
For a comprehensive guide, please refer to Browser and Driver Recommendations.
Bug Fixes
Improved performance for loading test cases in Provar Studio during uploads to Provar Quality Hub
The issue is fixed where Provar Studio took an excessively long time to load test cases when users attempted to upload them to Provar Quality Hub.
Fix for Existing Case Test Steps Failing issue due to Locator Resolution Errors
Resolved an issue where previously working test steps failed during execution. The failure occurred on multiple Case-related fields, while newly remapped fields worked successfully. This fix restores compatibility for existing mappings and ensures smooth execution without requiring remapping of affected steps.
Fix for the UI Assert Locator Fields Auto-Updating for Page Object Mapped issue
Resolved an issue where UI Assert steps mapped via Page Objects were automatically updating to incorrect fields. Attempts to correct and save the expected field were not retained, reverting back to the previous selection. This fix ensures that locator mappings remain stable and accurately bound to the intended Page Object field, preventing unwanted automatic updates.
Fix for Keyboard Shortcut Search and Resource Navigation Not Working
Resolved an issue in the previous Provar 2.17.1 release where keyboard shortcuts such as Ctrl + H (Search) and Shift + Ctrl + R (Open Resource) were not functioning as expected. Users can now successfully trigger global search and resource navigation without requiring manual reconfiguration or workarounds.
Fix for Mac OS Not Displaying in SauceLabs Platform Selection
Resolved an issue where Mac OS was not appearing in the platform list when configuring a SauceLabs browser connection, despite users having valid access in SauceLabs. The platform dropdown now correctly displays supported Mac OS versions based on the SauceLabs account configuration, ensuring accurate platform selection.
Fix for Execution Pack Failure on Server for Hybrid Model Test Cases
Resolved an issue where execution packs failed on the server in V2 when Hybrid model test cases were included. Packs now execute successfully on V2, ensuring only Hybrid-specific failures (if any) are isolated without impacting other test cases. Required files have been added to prevent compile-time errors for V2 Page Objects.
Known Issues
- In NitroX, Test Builder may get stuck when editing a previously mapped checkbox Group field.
- When working with Hybrid mappings, users may experience repeated “Evaluating XPath…” popups while accessing Component Locator settings or toggling qualifiers, causing noticeable delays. Performance optimization is planned in an upcoming release.
University of Provar
The University of Provar has created new courses on locators such as XPaths, Page Objects, and how Provar uses locators. Search our new catalog page by role, learning level, product, and more.
Customer Support
We are committed to providing continuous support. Please contact us If you have any questions about this release; we’re happy to assist you. To get in touch, log into the Provar Success Portal and select ‘Raise a Case,’ or contact your dedicated Customer Success Specialist.
- Home
- Get Started with V2
- Using Provar
- Understanding Provar’s Use of AI Service for Test Automation
- Provar Automation
- Creating a New Test Project
- Import Test Project from a File
- Import Test Project from a Remote Repository
- Import Test Project from Local Repository
- Commit a Local Test Project to Source Control
- Salesforce API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- Creating Test Cases
- Custom Table Mapping
- Functions
- Debugging Tests
- Defining a Namespace Prefix on a Connection
- Defining Proxy Settings
- Environment Management
- Exporting Test Projects
- Exporting Test Cases into a PDF
- Japanese Language Support
- Override Auto-Retry for Test Step
- Customize Browser Driver Location
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Test Builder
- ProvarDX
- Refresh and Recompile
- Reintroduction of CLI license Check
- 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 – Chrome Headless
- 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
- Database Testing
- Document Testing
- Email Testing
- Email Testing in Automation
- Email Testing Examples
- Gmail Connection in Automation with App Password
- App Configuration for Microsoft Connection in MS Portal for OAuth 2.0
- OAuth 2.0 Microsoft Exchange Email Connection
- Support for Existing MS OAuth Email Connection
- OAuth 2.0 MS Graph Email Connection
- Create a Connection for Office 365 GCC High
- Mobile Testing
- OrchestraCMS Testing
- Salesforce CPQ Testing
- ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices Testing
- DevOps with V2
- Introduction to Provar DevOps
- Introduction to Test Scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous Integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation 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
- CircleCI
- Copado
- Docker
- Flosum
- Gearset
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation 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
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Version Control
- Salesforce Testing
- Recommended Practices
- Salesforce API Access Control Security Update – Impact on Provar Connections
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- Java 21 Upgrade
- Testing Best Practices
- Automation Planning
- Supported Testing Phases
- Provar Naming Standards
- Test Case Design
- Create records via API
- Avoid using static values
- Abort Unused Test Sessions/Runs
- Avoid Metadata performance issues
- Increase auto-retry waits for steps using a global variable
- Create different page objects for different pages
- The Best Ways to Change Callable Test Case Locations
- Working with the .testProject file and .secrets file
- Best practices for the .provarCaches folder
- Best practices for .pageObject files
- Testing Best Practices
- Troubleshooting with V2
- How to Use Keytool Command for Importing Certificates
- Browsers
- Configurations and Permissions
- Add Permissions to Edit Provar.ini File
- Configure Provar UI in High Resolution
- Enable Prompt to Choose Workspace
- Increase System Memory for Provar
- Refresh Org Cache Manually
- Show Hidden Provar Files on Mac
- Java Version Mismatch Error
- Unable to create test cases, test suites, etc… from the Test Project Navigation sidebar
- Connections
- DevOps with V2
- Error Messages
- Provar Manager 3.0 Install Error Resolution
- Provar Manager Test Case Upload Resolution
- Administrator has Blocked Access to Client
- JavascriptException: Javascript Error
- Resolving Failed to Create ChromeDriver Error
- Resolving Jenkins License Missing Error
- Resolving Metadata Timeout Errors
- Test Execution Fails – Firefox Not Installed
- Selenium 4 Upgrade
- Licensing and Installation
- Memory
- Test Builder
- V2 Release Notes