Provar Automation V3 - Winter '26 Release 1
Executive Summary
We’re excited to announce the latest enhancements to the Provar product suite with our Winter ’26 Release 1. You can download and install Winter ’26 Release 1 directly from the Provar Success Portal.
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.
Winter ‘26 Compatibility
Change Area | Impact Summary |
Checkbox Rendering on Tables (Related Lists, Lists) | In Winter ’26, Salesforce introduced significant changes to checkbox rendering. The new checkboxes use a lightning-icon component, replacing the earlier DOM structure. This update changes the way checkboxes are rendered, and causes locator failures in automation scripts. Provar scripts continue to work without changes, but page objects with custom locators may require review. Note: These checkboxes are visibly look different in Winter 26 |
Entitlement Object – Entitlement Process → SLA Policy | The Entitlement Process label has been updated to SLA Policy across New and Edit screens of Entitlement Object in Winter 26. This caused dropdown filtering issues where the old label was referenced. Provar mappings have been updated to support the new label, so existing scripts work without modifications. Page objects using hardcoded labels may need updates. |
Convert Lead – Accordion Section Heading Update | Winter 26 shows that on the Convert Lead screen, accordion section headings have changed from <h3> (Sub-Subheader) to <h2> (Subheader). This affected scripts validating headers and interacting with multiple fields under them. Provar scripts remain compatible and work without any updation efforts, but page objects with hardcoded locators may require updates. |
Merge Case Screen – Label Update | In Winter ’26, the Merge Case screen shows the label Entitlement Process Start Time as SLA Policy Start Time. This change can impact row locators and conditions referencing the old label. Provar supports this change, and existing scripts continue to work without any changes. Custom locators in this area may require review and updates. |
Salutation Field – DOM Changes | Additional classes have been introduced in the DOM for the Salutation field. While the component is still rendered using Aura, these changes may affect automation scripts relying on exact class matches. Provar scripts remain unaffected, but custom locators should be reviewed. |
Edit Select Product – Header Attribute Change | The Edit Select Product screen now includes additional text in the header title attributes. This caused assertion failures in legacy automation scripts. Provar is compatible with the change and does not require manual updates. |
Picklist Fields Impact across Multiple Objects | DOM updates have introduced additional classes in picklist fields across multiple objects, including Case, Campaign, Opportunity, Quick Lead, Account Team Member, and Operating Hours. Provar scripts continue to work without changes. Page objects with hardcoded locators may require review. |
FSL Gantt View – DOM Changes | Winter ’26 introduced DOM updates in the Field Service Gantt view, causing incorrect behavior when interacting with the Notification button. Provar handles this change seamlessly, but custom locators in this area may need review and updates. |
Winter ’26 – CPQ
Provar is now compatible with the latest CPQ package version 258 introduced in the Salesforce Winter ’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
Environment Variable Support for Connections
Provar now allows all connection secrets and user variables to be stored as system environment variables. This enhancement is designed to improve security, especially in CI/CD pipelines, by ensuring sensitive information such as credentials is not exposed in configuration files.
The underlying format of each connection remains unchanged, making adoption straightforward with minimal disruption. By externalizing secrets into environment variables, teams can strengthen data protection practices while maintaining the same usability and compatibility as before.
Learn more here.

Export Test Cases to PDF
The “Export to PDF” option, previously available in V2, has now been added to the V3 interface.
With this update:
- Users can export test cases as PDF files directly from the V3 context menu.
- Exported PDFs mirror the layout and structure of V2, ensuring consistency for reporting, documentation, and reviews.
- The feature has been tested across supported operating systems (Windows and Mac).
Support for Screenflows in Vlocity Fields
We enhanced the Hybrid Model to support Salesforce Screen Flow fields in addition to Vlocity fields.
With this update:
- Page Objects are now created properly for Screen Flows.
- A new flowName attribute has been added to Page Object class annotations for Screen Flow support.
- Execution and mapping now work seamlessly with both Standard + Web Component (WC) and Page Object + WC approaches.
- Existing Vlocity field functionality remains unchanged.
Hybrid Model: Support for Page Object Operations
We enhanced the Hybrid Model to support Page Object (PO) operations, allowing users to interact with standard components and interactions directly from the PO file.
With this update:
- Users can now define and execute PO operations for fields within the PO file.
- Standard interactions can be called from the standard JSON.
- Existing functionality that worked with web elements also works seamlessly with web components.
Platform Updates
Edge Chromium as Authoring Browser
Provar now supports Microsoft Edge Chromium as an additional authoring browser, giving users more choice and flexibility when creating and managing their test cases. Until now, Chrome was the primary option for authoring, which created a dependency on a single browser. By introducing Edge support, Provar reduces this reliance and empowers teams to work in an environment that aligns with their organization’s preferred browser strategy. This also ensures better alignment with evolving enterprise IT standards, where Edge is increasingly becoming the default.
Enabling Edge as the authoring Test Builder browser is straightforward. Users simply need to Navigate to Settings>Preferences and update the Test Authoring Browser to Edge (Chromium) Once enabled, test authoring flows seamlessly in Edge, maintaining the same functionality and user experience as in Chrome. This enhancement not only improves compatibility with modern web technologies but also provides resilience in test authoring by supporting multiple browsers.

Test Authoring with Edge:

Edge (Chromium) Options
Provar now supports the ability to configure Microsoft Edge Options for automation test execution. This enhancement allows users to apply Edge-specific browser settings, making it easier to fine-tune tests for different browser options. By aligning with native Edge capabilities, this feature gives teams greater flexibility in managing test runs while maintaining compatibility with enterprise browser standards.
It’s important to note that this support is for standard Edge Options and does not extend to experimental options. Users can reference the official Microsoft Edge Options documentation for a complete list of supported configurations and best practices. This update ensures that Provar users can take advantage of modern Edge settings while keeping their automation suite consistent, reliable, and production-ready.

Chrome
Chrome 137 Extension Policy Update
With the release of Chrome 137, Google has introduced a new security policy that blocks automatic installation of browser extensions. To comply with this change, Provar now provides a one-time guided setup for the Chrome extension. When Chrome is launched via Provar and the extension is not installed, users will see a prompt directing them to install it from the Chrome Web Store.
Once installed, the extension persists across new workspaces, Provar installers, and Chrome updates, without requiring any manual configuration changes until configuration is manually deleted. All existing Authoring functionality remains unchanged, ensuring a seamless experience while meeting Chrome’s updated security standards.
Refer to this page for more details.

Browser Compatibility Updates
Chrome
As part of our pre-release testing, we have confirmed that Automation v3.0.2 is fully compatible with Chrome version 140 .
Why is this important?
Including ChromeDriver 140 in Automation v3.0.2 and ensuring compatibility with Chrome 140 helps eliminate the risk of incompatibility issues that could otherwise impact the proper functioning of test cases.
How can I use this?
If you plan to use Chrome 137, we recommend upgrading to Provar Automation v3.0.2, which includes ChromeDriver 140 by default.
Automation will automatically attempt to download the correct ChromeDriver if it detects a driver exception. If your organization’s security protocols prevent the automatic download, you can manually override the ChromeDriver.
To downgrade or use a different version of ChromeDriver, refer to this support article, which explains how to configure a ChromeDriver other than the default one provided in your Provar Automation installation.
Microsoft Edge Driver
We have updated the Microsoft Edge WebDriver to version 139 to ensure compatibility with the latest browser release and provide improved stability when running automated tests.
Browser and Driver Combinations Recommended for Provar Automation v3.0.2
For a comprehensive guide, please refer to the Browser and Driver Recommendations.
Bug Fixes
Fix for Duplicate Page Object Recognition in Test Builder
We resolved an issue where the Test Builder incorrectly recognized an existing Page Object as a new Page Object for the Home Page components. This caused failures when using “Add & Do” with the error message “Page object already exists”, particularly during field mapping.
With this update:
- Test Builder now correctly identifies and reuses existing Page Objects instead of duplicating them for the Home Page components.
- Support has been added for the Page Object with Lightning Components on Home Pages, using stable locators.
Fix for Execution Report Visibility in Outlook
We resolved an issue where PDF execution reports attached in Test Plan emails were not visible in Outlook or OWA as per the Microsoft default policy.
With this update, PDF execution reports are now attached and displayed properly across all major email clients, including Outlook.
Fix for Inconsistent Results in Bulk Test Runs
We resolved a significant issue where bulk test runs were producing inconsistent results, with multiple failures caused by stale element exceptions. These improvements ensure more reliable execution and reduce the likelihood of unexpected test failures.
Enhancements include handling Salesforce banner interruptions that previously caused instability, and adding safeguards such as null checks to prevent errors during execution. Together, these changes improve test consistency and robustness across large-scale test runs.
Safari Browser Support in SauceLabs
We fixed an issue where test cases were failing at the “On Screen” step when using the Safari browser with SauceLabs as the provider.
With this update, Safari test cases now run successfully in SauceLabs, consistent with other supported browsers.
Fix for SOQL Query Value Formatting
We resolved an issue where SOQL queries returned large decimal values in scientific notation (e.g., 2.011708732E7) instead of the expected numeric format (e.g., 20117087.32).
With this update, SOQL queries now return values in the correct numeric format, ensuring consistency in test logs and results.
Japanese Character Handling Improvements
We resolved an issue where Japanese characters became garbled when mapping a custom table using NitroX.
With this fix, Japanese characters are now displayed correctly during table mapping and record identification, ensuring smoother use of NitroX in multilingual environments.
Fix for Date Field Value Updates in Test Builder
We resolved an issue where changing a date value from the calendar control did not correctly update the value in Test Builder. Instead, a text value was displayed.
With this fix, date fields selected from the calendar now update and display correctly in Test Builder.
Fix for GUID Creation During Bulk Copy-Paste Operations
We resolved an issue where performing a large number of copy-paste operations for test cases and test plans at once did not generate GUIDs for the copied items.
With this fix, GUIDs are now created correctly for Test Cases, Test Plans, Test Folders, and Test Instances during bulk copy-paste operations.
Open Resource Shortcut
The shortcut key for opening resources in Provar has been updated from Ctrl+Shift+R to Ctrl+Shift+O. This change was introduced because Eclipse has reserved the previous shortcut, creating conflicts for users.
With the new shortcut, users can continue to access resources quickly and consistently without interference from Eclipse defaults. This update ensures smoother navigation while maintaining alignment with standard IDE practices.
Security Improvements
This release strengthens Provar’s security posture with updates across core components and dependencies. We have implemented stronger TLS protocols to ensure modern encryption standards, patched multiple third-party and platform vulnerabilities, and addressed an XML External Entity (XXE) issue in Eclipse JGit. These updates reduce potential attack surfaces, safeguard customer environments, and maintain compatibility with modern infrastructure.
For customers who track security advisories, this release includes fixes for several CVEs (including CVE-2024-47554, CVE-2025-25193, CVE-2024-12798, and CVE-2024-47535). No customer action is required—these fixes are included as part of the release.
Known Issues
- In Winter 26 orgs, we have identified that the Skill object (a referencedObject) is now returning readPermission as false in metadata. As a result, mapping and execution for this field are impacted. This appears to be an incorrect value from the Salesforce in the metadata end and is likely to be corrected in a future update. A case (#CaseNumber) has already been raised with Salesforce for resolution.
- A new field Time to Next Milestone appears on the UI but has no reference in metadata specifically on Winter 26 Orgs.
- Custom Path In Progress state is causing issues when resolution reaches 100% on Winter 26 Orgs.
- On the Opportunity Team Member screen, label assertion is impacted due to a Winter ’26 change.
- A blank screen may appear for a fraction of a second while using Studio.
Provar Manager
Test Case Generation 2.0 is now available in the Provar Test Management App. This update introduces multi-format outputs (Text, Markdown, JSON, Gherkin, XML, Apex, Java), support for generating up to 10 test cases at a time, smarter prompts for more reliable results, and issue-aware generation with auto-populated fields. New features include a scenario quality assistant with AI “Improve Scenario” suggestions, enhanced usability, and safer downloads.
The release also delivers key bug fixes, improved test data handling, and compatibility updates for Shield Encrypted Orgs. Click here for the latest Provar Manager release notes.
Education
We offer a variety of courses and articles to support you along your journey with us!
We value your input—please share your feedback via the end-of-course surveys and helpful article feature, respectively.
University of Provar
The University of Provar has created new courses on locators such as XPaths, Page Objects, and how Provar uses locators. We also have new courses providing guidance on the newest AI features available in V3.
Search our new catalog page by role, learning level, product, and more.

Documentation
V3 and V2 documentation has been split to make finding what you need even easier.
Search V3 documentation by selecting the Provar Automation V3 menu option or clicking on the product button in the middle of the page.
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 V3
- AI with Provar Automation V3
- Using Provar Automation V3
- Automation V3: Feature-by-Feature Guide
- Automation V3: Provar Automation
- Automation V3: Creating a New Test Project
- Automation V3: Import Test Project from a File
- Automation V3: Import Test Project from a Remote Repository
- Automation V3: Import Test Project from Local Repository
- Automation V3: Commit a Local Test Project to Source Control
- Automation V3: Salesforce API Testing
- Automation V3: Behavior-Driven Development
- Automation V3: Consolidating Multiple Test Execution Reports
- Automation V3: Creating Test Cases
- Custom Table Mapping in V3
- Functions in V3
- Automation V3: Using Functions
- Automation V3: Count
- Automation V3: DateAdd
- Automation V3: DateFormat
- Automation V3: DateParse
- Automation V3: GetEnvironmentVariable
- Automation V3: GetSelectedEnvironment
- Automation V3: IsSorted
- Automation V3: Not
- Automation V3: NumberFormat
- Automation V3: Round
- Automation V3: StringNormalize
- Automation V3: StringReplace
- Automation V3: StringTrim
- Automation V3: TestCaseErrors
- Automation V3: TestCaseName
- Automation V3: TestCaseOutCome
- Automation V3: TestCasePath
- Automation V3: TestCaseSuccessful
- Automation V3: TestRunErrors
- Automation V3: UniqueId
- Automation V3: Debugging Tests
- Automation V3: Creating Custom Test Steps
- Automation V3: Defining Proxy Settings
- Automation V3: Environment Management
- Automation V3: Exporting Test Projects
- Automation V3: Japanese Language Support
- Automation V3: Customize Browser Driver Location
- Automation V3: Managing Test Steps
- NitroX in V3
- Automation V3: Provar Test Builder
- ProvarDX in V3
- Automation V3: Refresh and Recompile
- Automation V3: Reintroduction of CLI license Check
- Automation V3: Reload Org Cache
- Automation V3: Reporting
- Automation V3: Running Tests
- Automation V3: Searching Provar with Find Usages
- Automation V3: Secrets Management and Encryption
- Automation V3: Setup and Teardown Test Cases
- Automation V3: Tags and Service Level Agreements (SLAs)
- Test Cycles in V3
- Automation V3: Test Plans
- Automation V3: Testing Browser – Chrome Headless
- Automation V3: Testing Browser Options
- Automation V3: Tooltip Testing
- Using Custom APIs in V3
- Callable Tests in V3
- Data-Driven Testing in V3
- Page Objects in V3
- Automation V3: Introduction to XPaths
- Automation V3: Creating an XPath
- Automation V3: JavaScript Locator Support
- Automation V3: Maintaining Page Objects
- Automation V3: Mapping Non-Salesforce Fields
- Automation V3: ProvarX™
- Automation V3: Refresh and Reselect Field Locators in Test Builder
- Automation V3: Create different page objects for different pages
- Applications Testing in V3
- Automation V3: Database Connections
- Automation V3: PDF Testing
- Automation V3: Email Testing in Automation
- Automation V3: Email Testing Examples
- Automation V3: Gmail Connection in Automation with App Password
- Automation V3: App Configuration for Microsoft Connection in MS Portal for OAuth 2.0
- Automation V3: OAuth 2.0 Microsoft Exchange Email Connection
- Automation V3: Support for Existing MS OAuth Email Connection
- Automation V3: OAuth 2.0 MS Graph Email Connection
- Automation V3: Create a Connection for Office 365 GCC High
- Automation V3: Mobile Emulation (Salesforce Mobile)
- Automation V3: Using Provar with Amazon Web Services (AWS) Device Farm
- Automation V3: Web Services
- Automation V3: Integrating with Jira
- Automation V3: Provar Feature Flags and Properties Configuration
- Automation V3: Using Java Method Annotations for Custom Objects
- Automation V3: Test Palette Introduction
- Automation V3: Apex Bulk
- Automation V3: Apex Execute
- Automation V3: Assert Test Step
- Automation V3: Assert Salesforce Layout
- Automation V3: Break Test Step
- Automation V3: Extract Salesforce Layout
- Automation V3: Fail Test Step
- Automation V3: Finally Test Step
- Automation V3: For Each Test Step
- Automation V3: Generate Test Case
- Automation V3: Group Steps Test Step
- Automation V3: If Test Step
- Automation V3: List Compare
- Automation V3: Page Object Cleaner
- Automation V3: Read Test Step
- Automation V3: Set Values Test Step
- Automation V3: Set Values
- Automation V3: Sleep Test Step
- Automation V3: String Test Steps
- Automation V3: Switch Test Step
- Automation V3: UI Action
- Automation V3: UI Assert
- Automation V3: UI Connect
- Automation V3: UI Fill
- Automation V3: UI Handle Alert
- Automation V3: UI Navigate
- Automation V3: UI On Screen
- Automation V3: UI With Row
- Automation V3: Wait For Test Step
- Automation V3: While Test Step
- Automation V3: Override Auto-Retry for Test Step
- DevOps with V3
- Automation V3: Introduction to Provar DevOps
- Automation V3: Introduction to Test Scheduling
- Automation V3: Setting Java Development Kit (JDK) Environment Variables
- Automation V3: Configuration on Jenkins
- Automation V3: Version Control and DevOps
- Automation V3: Setting up Continuous Integration
- Automation V3: Execution Environment Security Configuration
- Automation V3: Bitbucket Pipelines
- Automation V3: Perfecto Mobile
- Automation V3: ANT Task Parameters
- Automation V3: Provar Jenkins Plugin
- Automation V3: Running Automation Tests on Jenkins
- Automation V3: Configuring the Automation Secrets Password in Microsoft Azure Pipelines
- Automation V3: Parallel Execution in Microsoft Azure Pipelines using Test Plans
- Automation V3: Parallel Execution in Microsoft Azure Pipelines using Targets
- Automation V3: Parallel Execution in Microsoft Azure Pipelines using Multiple build.xml Files
- Automation V3: Parallel Execution in GitHub Actions using Test Plan
- Automation V3: Running Provar on Linux
- Automation V3: CircleCI Orbs
- Automation V3: CircleCI Common Build Errors
- Automation V3: CircleCI via Docker
- Automation V3: Copado Integration Introduction
- Automation V3: Copado Configuration
- Automation V3: Copado Architecture Overview
- Automation V3: Docker Runner
- Automation V3: Running Provar Tests on Docker using Docker File
- Automation V3: Docker Continuous Integration
- Automation V3: Setting up Continuous Integration with Jenkins for Docker
- Automation V3: Generating the build.xml File for Docker
- Automation V3: Flosum Configuration
- Automation V3: Flosum Integration Introduction
- Automation V3: Flosum Architecture Overview
- Automation V3: Parallel Execution in GitHub Actions using Multiple build.xml Files
- Automation V3: Parallel Execution in GitHub Actions using Targets
- Automation V3: Remote Trigger in GitHub Actions
- Automation V3: Parallel Execution in GitHub Actions using Job Matrix
- Automation V3: Gearset DevOps CI/CD via Jenkins
- Automation V3: GitLab Continuous Integration
- Automation V3: GitHub Desktop – Creating a Git Repository for Automation Projects
- Automation V3: Integrating GitHub Actions CI to Run Automation CI Task
- Automation V3: Provar Test Results Package
- Automation V3: Running a Provar CI Task in Azure DevOps Pipelines
- Automation V3: Amazon Web Service (AWS) & Jenkins Configuration
- Automation V3: ANT: Generating ANT Build File
- Automation V3: ANT Licensing
- Automation V3: Reading Data from Excel
- Automation V3: Configuration on other CI tools
- Automation V3: Setting Apache Ant Environment Variables
- Automation V3: BrowserStack Desktop
- Automation V3: Integrating with LambdaTest
- Automation V3: Sauce Labs Desktop
- Automation V3: AutoRABIT Salesforce DevOps in Provar Test
- Automation V3: Selenium Grid
- Automation V3: Working with Git
- Automation V3: Configuration for Sending Emails via the Automation Command Line Interface
- Automation V3: Parameterization using Environment Variables in GitHub Actions
- Automation V3: Slack Integration with Automation
- Automation V3: Zephyr Cloud and Server
- Automation V3: Adding a Salesforce Communities Connection
- Automation V3: Integrating with Sauce Labs Real Device
- Automation V3: Travis CI
- Automation V3: Salesforce DX Integration
- Automation V3: Variable Set Syntax
- Automation V3: Visualforce Testing
- Automation V3: List and Table Testing
- Automation V3: Salesforce Lightning Web Component (LWC) Locator Support
- Automation V3: Salesforce Console Testing
- Recommended Practices with V3
- Automation V3: Provar Naming Standards
- Automation V3: Object Mapping Between Provar Automation and Provar Manager
- Salesforce API Access Control Security Update – Impact on Provar Connections
- Automation V3: Salesforce Connection Best Practices
- Automation V3: Automation Planning
- Automation V3: Supported Testing Phases
- Automation V3: Best practices for the .provarCaches folder
- Automation V3: Best practices for .pageObject files
- Automation V3: Avoid Metadata performance issues
- Automation V3: The Best Ways to Change Callable Test Case Locations
- Automation V3: Improve Your Metadata Performance
- Automation V3: Abort Unused Test Sessions/Runs
- Automation V3: Create Records via API
- Automation V3: Test Case Design
- Automation V3: Increase auto-retry waits for steps using a global variable
- Troubleshooting with V3
- Automation V3: How to Use Keytool Command for Importing Certificates
- Automation V3: Resolving High Memory Usage
- Automation V3: Refresh Org Cache Manually
- Automation V3: Show Hidden Provar Files on Mac
- Automation V3: Add Permissions to Edit Provar.ini File
- Automation V3: Test Builder Does Not Launch
- Automation V3: Provar License Issue Solution
- Automation V3: How to Configure a Single Sign-On Connection
- Automation V3: Out of Memory Error During CI Execution
- Automation V3: Add Gmail Firewall Exception
- Automation V3: Add a License Firewall Exception
- Automation V3: Resolving Jenkins License Missing Error
- Automation V3: Increase System Memory for Provar
- Automation V3: Resolving Metadata Timeout Errors
- Automation V3: Java Version Mismatch Error
- Automation V3: Provar Manager 3.0 Install Error Resolution
- Automation V3: Test Case Does Not Run on IE Browser
- Automation V3: Test Builder Not Working Correctly
- Automation V3: Internationalization Support
- Automation V3: Salesforce Release Updates
- V3 Release Notes