Provar Automation Summer ‘26 Release
Summary
We’re excited to announce the Provar Automation Summer ‘26 Release, which includes updates to V3 (Version 3.0.7) and V2 (2.19.0). This release delivers Salesforce Summer ’26 compatibility while continuing to enhance automation reliability, scalability, and performance. The primary goal of this release is to ensure that regression suites remain fully operational with minimal maintenance, helping organizations maintain business continuity and confidently adopt the latest Salesforce updates.
We’re also pleased to announce Provar’s extended support for Microsoft Dynamics applications, reinforcing our commitment to providing reliable, scalable, and intelligent test automation across enterprise platforms. In addition, significant performance improvements have been introduced across Test Builder mapping, Studio-level Apex processing, and Set APIs for bulk data operations, resulting in faster and more efficient test execution workflows.
This release update also includes the beta launch of Provar MCP Server capabilities and numerous updates to Provar Quality Hub.
Unless otherwise noted, all changes apply to both Provar Automation V2 (2.19.0) and V3 (3.0.7).
Key Highlights
- Summer ’26 Compatibility
This release introduces Summer ’26 compatibility, ensuring your regression suites continue to run seamlessly with minimal to no maintenance, helping maintain business continuity. - Microsoft Dynamics Application Support (V3 exclusive)
Expanded support for Microsoft Dynamics applications reinforces our commitment to delivering reliable, scalable, and intelligent test automation capabilities. - AI Self-Healing (Beta – V3 exclusive):
Introducing AI Self-Healing (Beta), designed to improve test resilience by intelligently identifying and adapting to UI changes during execution. This capability helps reduce test maintenance efforts, minimize failures caused by locator changes, and improve overall automation stability.
- Government Cloud support for Agentforce Test APIs (V3 exclusive):
Agentforce Test APIs now support both Salesforce Government Cloud and standard cloud environments through a configurable Government Cloud endpoint option.
- Performance Enhancements
Significant performance improvements have been implemented across Test Builder mapping, Studio-level Apex processing, and Set APIs for bulk data operations. - Edge Browser on Linux:
Provar now supports Microsoft Edge browser execution on Linux environments, expanding the range of supported browser-platform combinations for automated testing on linux-based infrastructure, CI/CD pipelines, or containerized environments.
- Logging & Security Improvements
Introduced enhancements to logging and security capabilities, along with key bug fixes, to strengthen platform reliability, improve monitoring, and support more efficient troubleshooting. - Provar Quality Hub Release Highlights
Provar Quality Hub 3.27-3.30 introduces major enhancements across AI-powered test generation, DevOps integrations, metadata intelligence, and platform scalability. Highlights include screenshot-based AI test generation, Google Gemini support, automated metadata sync, deeper Copado and Jira integrations, ProvarLint project scoring, and expanded access for limited-access users.
- Provar MCP (Beta)
Provar MCP is now available in beta for all Provar users. This stdio MCP server comes with 40+ tools across generation, validation, execution, and inspection capabilities for test projects, plans, suites, and cases, as well as page objects, NitroX components, and project configuration & execution files.
Important: Salesforce has restricted SOAP API login using username and password authentication. Customers currently using username/password-based connections must migrate to OAuth-based authentication to use 3.0.7 and to ensure uninterrupted connectivity and continued platform compatibility. Read more from Salesforce here.
Essential Upgrade Instructions
We highly recommend upgrading to the latest release to benefit from the new capabilities, latest enhancements, optimal performance, and uninterrupted support.
To ensure a clean setup and avoid compatibility issues, follow the instructions given below:
- Remove old configuration folders from your system:
{UserHome}\Provar\.configuration\{versioned config folders}
- Delete the .chromeProfile folder
{UserHome}\Provar\.chromeProfile
- (Recommended) Import your projects into a new workspace rather than reuse your existing workspace.
Summer ‘26 Compatibility (V2 & V3)
| Change Area | Impact Summary |
| Advanced Lookup – DOM Changes Across All Objects | Summer ’26 introduces significant structural changes to Advanced Lookup components across all objects. Salesforce replaced the <record-picker-lookup-advanced> overlay tag with a standard <div> using the new class attribute <lightning-record-picker-advanced>. This affects lookup selection and interaction behavior during execution. Provar fully supports this updated structure, so standard scripts continue to work as expected. However, any custom implementations using hardcoded locators based on the older tag or attributes may need revision. |
| Service Appointment List View – Parent Record Columns Mapping Missing | With Summer ’26, Salesforce enhanced the default Service Appointment list view by adding two new columns: “Parent Record” and “Parent Record Type.” This altered the existing table structure and impacted validations and navigation steps dependent on column positioning. Provar aligns with this updated layout, and scripts should continue working without additional effort. Custom validations using fixed column references or hardcoded locators may require adjustment. |
| Aura Picklist Accessibility DOM Change – FSL Operating Hours (Time Zone) | As part of Summer ’26 accessibility improvements, Salesforce updated the Aura forceInputPicklist DOM behavior. Earlier, the selected value appeared directly inside the <a class=”select”> element, whereas it is now rendered inside a nested <span id=”…;a-value”>, with aria-labelledby referencing both label and value spans. This change caused assertion failures for the “Time Zone” field on the New Operating Hours screen. Provar handles the new structure automatically, but custom validations based on direct text node checks may need updates. |
| Product Transfer (Quantity Unit of Measure) – Dom Change | Salesforce has revised the Aura picklist rendering in Summer ’26 to improve accessibility compliance. The selected value for picklists is no longer stored as a direct text node inside the anchor tag and is now wrapped inside a nested <span>. This resulted in assertion failures for the “Quantity Unit Of Measure” field on the Product Transfer New screen. Provar supports this DOM change without requiring script updates, although custom code relying on older text node behavior may need review. |
| Convert Lead (Record Type) – DOM Changes | In Summer ’26, the “Record Type” field on the Convert Lead screen is impacted by Salesforce’s updated Aura forceInputPicklist structure. The selected value now resides inside a nested <span> rather than directly under the <a class=”select”> element, with updated aria-labelledby references for accessibility support. This led to assertion failures during execution. Provar handles the updated DOM seamlessly, while custom code using direct text validations may require modification. |
| Quick Lead Publisher (Salutation) – DOM Changes | Salesforce introduced accessibility-related DOM updates in Summer ’26 for the “Salutation” field on the Quick Lead Publisher action screen. The selected value is now wrapped inside a nested <span> instead of being directly available as anchor text. This affected automation assertions and field validations. Provar supports the new structure without requiring standard script changes, but custom locators dependent on previous attributes may need updates. |
| DOM Change – Case Publisher Update Case (Status) | Summer ’26 includes Aura picklist rendering changes for the “Status” field on the Case Publisher Update Case Quick Action. Since the selected value is now stored within a nested <span> rather than as direct anchor text, execution failures were observed in status validation steps. Provar remains compatible with this update, and existing scripts continue to work. However, manually created Page Object locators using older DOM assumptions may require revision. |
| Quote – Validation Error Message Update | Salesforce corrected the validation message for the Partner Discount field in Summer ’26. Previously, although the field accepted only 3 digits, the validation message incorrectly stated that up to 5 digits were allowed. The message has now been aligned with the actual validation rule. This impacts existing validation checks where the expected error message is asserted, and those test cases may require updates. Newly created tests will automatically reflect the corrected behavior. |
| SOAP API Login Disabled | Beginning with Summer ’26, Salesforce no longer supports SOAP API login() in the latest Salesforce API jars. As a result, username/password-based Provar connections using SOAP authentication may fail during connection setup. Users are strongly advised to migrate to OAuth-based connections to avoid interruptions. Existing environments using legacy SOAP login should be reviewed and updated proactively. |
Summer ’26 – CPQ
Provar is now compatible with the latest CPQ package version 262 introduced in the Salesforce Summer ’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.
Automation V3 Features and Enhancements
MS Dynamics Application Support
Provar now delivers Application Intelligence purpose-built for Microsoft Dynamics 365 and the Microsoft Power Platform. Rather than relying on fragile locators, Provar understands the underlying application framework, including components, metadata, structure, and runtime behavior, enabling more resilient and maintainable test automation.
With this enhancement, teams can accelerate test creation, reduce ongoing maintenance efforts, and improve confidence in business-critical releases across the Microsoft ecosystem. This support further strengthens Provar’s ability to provide scalable, enterprise-grade automation for modern business applications.
See this help document for more details.

AI Self Healing (Beta)
Provar introduces AI Self-Healing (Beta), an intelligent capability designed to improve automation resilience by automatically adapting to UI changes during test execution. Instead of depending solely on static locators, Provar leverages AI-driven analysis to identify application elements based on context, structure, and behavior, helping tests recover from common UI modifications with minimal manual intervention.
With AI Self-Healing, teams can reduce test maintenance overhead, minimize failures caused by locator changes, and improve execution reliability across evolving applications. This enhancement helps accelerate release cycles while increasing confidence in automation outcomes for enterprise-scale testing environments.
As this is a Beta feature, AI Self-Healing must be explicitly enabled in the provar.properties file located at <UserHome>/Provar/provar.properties using the following property:
com.provar.ai.healing.enabled=true
Note: AI capabilities must be enabled in order to use AI Self-Healing. This feature cannot be enabled without first enabling AI capabilities in the V3 directly.
For more information, see this detailed breakdown of how Provar’s self-healing works.
Agentforce Test API Support for Government Cloud
Agentforce Test APIs now support Salesforce Government Cloud environments in addition to standard commercial cloud environments. A new configuration checkbox has been introduced to enable Government Cloud support. When selected, API requests are automatically routed to the appropriate Government Cloud endpoint.
With this enhancement, teams can seamlessly execute Agentforce Test APIs across both Government and non-Government cloud environments using a unified configuration experience, improving flexibility and supporting broader enterprise and public sector testing requirements.
Automation V2 & V3 Features and Enhancements
Edge browser on Linux Environments
Provar now supports Microsoft Edge browser execution on Linux environments, expanding the range of supported browser-platform combinations for automated testing.
With this enhancement, teams running tests on Linux-based infrastructure, CI/CD pipelines, or containerized environments can now execute automation suites using Microsoft Edge, enabling greater flexibility, broader browser coverage, and improved cross-browser validation across enterprise applications.
Improved Logging
Provar now includes enhanced logging with timestamp information to help teams better diagnose and troubleshoot execution issues. These improvements provide more precise visibility into execution flow and event sequencing, making it easier to identify failures and analyze runtime behavior.
Note: This enhancement is currently applicable to ANT based executions only.
Security Improvements
This release includes ongoing security and compliance improvements validated through Provar’s internal and third-party review processes. These updates reinforce Provar’s commitment to delivering a secure, enterprise-grade platform aligned with modern security standards and best practices.
A JFrog Xray Scan Report has been reviewed to confirm component integrity and compliance.
Browser Compatibility Updates
Browser and Driver Combinations Recommended for Provar Automation 3.0.7 (V3) and 2.19.0 (V2)
- Chrome 148
- Chromedriver 148
- Same for Edge Chromium
For a comprehensive guide, please refer to the Browser and Driver Recommendations.
Known Issues
- LWC tables may experience inconsistencies with Test Builder Edit operations in certain scenarios.
- Performance degradation may occur in complex nested tests with large variable contexts.
- Some fields not included in the Salesforce WSDL may cause execution-related issues.
Provar Quality Hub 3.27-3.30 Release Highlights
This release summary includes updates delivered across:
- Provar Quality Hub 3.27-3.30
- DevOps Testing Plugin 0.8.0
- Provar for Agentforce 0.5.0
- Copado Plugin 0.5.0
AI-Powered Test Generation
Intelligent Test Case Generation received the largest investment across the Summer ’26 release cycle. Teams can now generate test cases from screenshots and visual context in addition to Salesforce metadata, enabling broader support for UI-driven workflows and reducing manual authoring effort. Generated results can now be exported as CSV files, and multi-select actions make it easier to manage large sets of generated assets at scale.
Google Gemini Support Added
OpenAI, giving organizations greater flexibility in aligning with internal AI strategies and compliance requirements. Teams can now configure generation quality thresholds to better control validation standards, and all AI generation capabilities have been expanded to limited-access users.
Copado Integration
Quality Hub now includes a plug-and-play component for relating multiple Test Plans directly to Copado User Stories and Promotions without custom development effort. New companion flow templates automate execution by triggering related Test Plans whenever a User Story transitions to “Ready for Testing” or a Promotion is deployed.
These enhancements reduce manual coordination between release management and QA teams while improving visibility into testing status directly within Copado-driven delivery workflows.
Metadata Component Sync
Metadata Component Sync has been significantly enhanced with automated change tracking for Salesforce metadata. Quality Hub can now identify updated and deleted metadata components directly from connected Salesforce orgs without requiring manual reconciliation.
A new Metadata Sync widget and detailed sync history view allow teams to schedule, monitor, and review sync activity directly from the associated System record, improving traceability and reducing administrative overhead.
Jira Sprint Integration
Quality Hub now supports importing and syncing Jira Sprint data directly into the platform. This allows organizations to align release timelines, sprint activity, and testing progress within a single reporting and quality management experience.
Sprint data can now be incorporated into dashboards and release management reporting to provide improved visibility across engineering and QA workflows.
Provar Test Project Scoring
A new built-in validation and scoring engine, powered by ProvarLint and more than 150 validation rules, now evaluates the overall health and maintainability of Provar test projects. Scoring is available across the project, plan, suite, and individual test case levels.
Validation results are surfaced as reportable Salesforce records and can be exported in HTML, CSV, or JSON formats for governance, auditing, and reporting purposes. AI-generated test cases are automatically validated and scored as part of the generation workflow.
Provar Grid Dynamic Concurrency
Provar Grid now retrieves concurrency limits dynamically from the Grid API at runtime across all execution surfaces, including scheduled runs, DevOps Center integrations, and Agentforce flows.
This enhancement replaces previous hardcoded defaults and ensures all executions automatically align with the correct licensed capacity available to the organization.
Expanded Access for Limited Users
A major theme across versions 3.28 through 3.30 focused on democratizing access to key platform capabilities. Limited-access users now have access to AI test generation, page object tooling, metadata synchronization, batch validation, and AI configuration settings.
To support cleaner administrative separation and least-privilege security models, a new “Manage Systems” custom permission has been introduced for System record administration.
Provar MCP (Beta)
Provar MCP is an AI-assisted quality layer built directly into the Provar DX CLI. It implements the Model Context Protocol (MCP), an open standard that lets AI assistants call tools on your behalf and exposes a rich set of Provar project operations to MCP-compatible clients such as Claude Desktop, Claude Code, Cursor, and Agentforce Vibes.
Once connected, your AI assistant can:
- Inspect your Provar Automation project and surface coverage gaps
- Generate Page Objects, NitroX Components, and test cases
- Interact with and modify Test Plans, Suites, and Projects
- Interface directly with Quality Hub using existing CLI commands for running, retrieving, and reporting on tests
- Validate every level of the test hierarchy (test cases, suites, plans, and the full project) against 170+ quality rules
- Trigger local Provar Automation test runs and Provar Quality Hub managed runs all from inside a chat session
The MCP server runs entirely on your local machine. No project files, test code, or credentials are transmitted to Provar servers.
Find out more here.
Provar Automation V2 End-of-Life Date
As we continue to drive adoption of Provar Automation V3 and incorporate more AI-native capabilities in our products, we are planning to discontinue all updates to Provar Automation V2 by December 31st, 2026. This means there will be no Salesforce Release compatibility update, security patches, bug fixes, or new features for V2 going forward from 2027. All customers will be encouraged to migrate to V3 following the V2 to V3 migration guide. Customers are not required to enable AI in V3, but are encouraged to do so. All AI Features can only be enabled by a System Administrator, and are disabled by default in V3.
Upcoming Webinars
Our upcoming Test What Matters: Summer ’26 Salesforce Release webinar on May 19, 2026 focuses on Salesforce Summer ’26 Updates and Provar Readiness. Register now on this exclusive webinar to explore the impact on your test automation strategy.
We have another upcoming webinar on May 21st, 2026, Building Confidence in AI-Powered Banking with nCino and Provar. Join Provar, with guest speakers from nCino, for a practical discussion on how financial institutions can prepare, validate, and monitor AI-enabled banking workflows.
Customer Support
We’re always here to support you. If you have questions or need assistance at any time, just log in to the Provar Success Portal and select ‘Raise a Case’, or reach out directly to your dedicated Customer Success Specialist. We’re happy to help!
Provar Community Forum
Learn from other customers, provide feedback, and get support with V3 changes and features in the forum in the V3 category. Join the Provar Community Forum!
- Home
- Provar MCP
- Get Started with V3
- System Requirements
- Automation V3: Skip Welcome Screen on Launch
- Browser and Driver Recommendations
- Installing Provar Automation V3
- Updating Provar Automation V3
- Licensing Provar Automation V3
- Automation V3: Granting Org Permissions to Provar Automation
- Automation V3: Optimizing Org and Connection Metadata Processing in Provar
- V3 Connections
- AI with Provar Automation V3
- AI Self-Healing (Beta)
- Closing the AI Quality Gap with Provar
- FAQ: Provar AI Capabilities
- Automation V3: Understanding Provar’s Use of AI Service for Test Automation
- Automation V3: Enable or Disable AI Features in Provar
- Automation V3: Provar Assistant
- Automation V3: Image Validator
- Automation V3: Intent Validator
- Automation V3: Test Data Generation
- Automation V3: Test Step Generation
- Automation V3: Utterance Generator
- Automation V3: Simplified Agentforce Agent API Testing
- Using Provar Automation V3
- Automation V3: Content Synchronization
- 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
- CBMT 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: Refactoring 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
- Provar for Microsoft Dynamics 365: Supported Capabilities
- 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
- Automation V3: Using Encrypted Password Variables in Expression Editors
- 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