Spring '25 Release 2
Executive Summary
We’re excited to announce the latest enhancements to the Provar product suite with our Spring ’25 Release 2. You can download and install Spring ’25 Release 2 directly from the Provar Success Portal.
Important Notice: Java 21 Upgrade
As we have notified in our previous communications, Provar has completed our upgrade to Java 21 and it is now available. This is part of our continuous efforts to utilize the latest technology. This upgrade ensures we can release ongoing updates as part of our regular long-term support compatibility commitment.
This change will impact you, as necessary changes must be implemented to ensure seamless running of Provar Automation. To find out more, check out our Java 21 help page which contains more details. We will keep you updated as we progress with this upgrade.
Note: All the latest build tags will now point to the latest 2.15.2 Automation release, which requires Java 21 setup for CI/CD execution.
Provar Automation Features and Enhancements
Support for Querying Tooling Objects in SOQL Query Step
Our SOQL query API is now more powerful, with the ability to query tooling objects. Users will see a Use Tooling API checkbox, allowing them to seamlessly include tooling objects in their SOQL queries. This enhancement enables direct use of tooling object query results within test cases while supporting aliases used in SOQL queries at present. The result format remains unchanged, ensuring consistency. Legacy scripts and existing SOQL queries will continue to function without impact, maintaining smooth compatibility. Learn more here.
Key Changes:
- Querying Tooling Objects:
With the checkbox selected, users can now query tooling objects using SOQL. This provides access to objects that were previously inaccessible in SOQL query steps, enabling them to be used in automation test cases. - Clear Segregation of Object Types:
A clear segregation is established between regular objects and tooling objects. The query will target tooling objects when the checkbox is selected; otherwise, the standard query method will be used. - Legacy Tests Compatibility:
For legacy tests, the checkbox will be deselected by default, ensuring backward compatibility with existing queries. - Preserved SOQL Capabilities:
All SOQL capabilities (e.g., aliases) will remain fully functional, with results consistently displayed in list form, whether querying tooling or regular objects.
Addition of Permission Set Information in Layout Extraction
The Extract and Assert Layout feature has been enhanced with Permission Set support. The Extract and Assert Layout APIs now include an option to extract Permission Sets for users. By selecting the Include Permission Set checkbox, users can obtain a comprehensive view of field details influenced by both the profile and permission set, ensuring a complete and accurate representation of Record Layout and DF Layout. Learn more here.
Key Changes:
- Field Details Enhanced:
When the checkbox is enabled, the extracted layout information will include fields that are impacted by both the profile and permission set, giving users a complete view of the layout. This enhancement applies to both Record Layout and DF Layout. - Comprehensive Layout View:
The new functionality ensures that users can see a fuller representation of the Layout that includes both Profile and Permission sets information. - Legacy Compatibility:
Existing test steps and scenarios will continue to work as they did before the release. No changes to existing functionality are required for users who do not enable the “Include Permission Set” checkbox.
SLDS2 Compatibility and Support
This release focuses on ensuring compatibility with the new Salesforce Lightning Design System 2 (SLDS2 currently in beta). The goal is to ensure that existing test cases continue to work as expected without requiring modifications, while also enabling the smooth creation and execution of new test cases and implementations using SLDS2.
Key Changes:
- Seamless Functionality for Existing Test Cases:
All existing test cases will function as expected, without requiring any code changes. This ensures that the transition to SLDS2 does not disrupt previously created test cases or automation scripts. - Support for Fresh Test Case Creation:
New test cases can be created and executed successfully using SLDS2, ensuring that the updated design system works seamlessly for both new and existing implementations.
NitroX
Disabled NitroX Mapping for Generic Websites (HTML5)
To enhance clarity and streamline NitroX usage, we have removed support for generic website testing. Going forward, NitroX will be dedicated to component-based testing, with a primary focus on Salesforce components. While NitroX performs well with Lightning Web Components (LWCs), it will no longer support Experience Cloud websites and Salesforce Page Objects (PO).
Key Changes:
- Hybrid Mode Enhancement: We are reimagining the integration of NitroX and Page Objects to improve usability, ensuring seamless transitions and easy debugging when switching between the two on the same page.
- Page Objects will now be used for all generic web testing.
- Legacy Test Case Support: Execution of existing test cases for Experience Cloud and generic websites will remain unaffected, ensuring smooth test execution.
This update improves the consistency of the NitroX mapping system and ensures it is used only with supported components. If you have any questions or concerns, please reach out to our support team.
Optimized Component Overrides with Inheritance in NitroX
Previously, manually modifying or overriding a standard component copied the entire file to the workspace under the NitroxPackages folder, giving it a higher priority and blocking Provar’s latest package updates. With this new functionality, only the modified changes are applied, ensuring users receive the latest updates along with their changes.
For example, if a user adds an attribute while overriding a component from the Test Builder, only that attribute is added to the component file, with a parentID referencing the original component. This ensures that the Test Builder receives the new attribute while retaining the standard definition of the Lightning Text Input.
Editable Locator for Page Structure Nodes in NitroX
Users can now edit locators for page structure nodes, providing more flexibility in managing locators, and attributes. A new edit icon allows quick modifications, with changes reflected in the mapping file. The updated UI ensures a seamless and intuitive experience.
Integration of PO XPath Editor for NitroX
Users can now leverage the existing PO XPath editor in NitroX to create custom XPath selectors when the adaptive locator is disabled. This enhancement provides greater flexibility in selecting unique elements on the DOM by allowing manual XPath creation based on attributes not included in the standard JSON. When the adaptive locator is turned off in Test Builder, the PO XPath editor will be available for custom XPath modifications, ensuring better control over element selection.
For example, the standard component mapping file includes only four attributes for adaptive locators. However, when the adaptive locator is turned off, a broader set of attributes becomes available, allowing users to create custom XPaths beyond the standard file.
Enable “Find Usage” Context Menu for NitroX
Users can now quickly locate the usage of custom components in NitroX with the new “Find Usage” context menu option in the studio. This functionality, replicated from PO, helps identify associated test cases and components, improving efficiency and workflow.
Provar Manager
Java 21 Support for Grid Execution
Provar Manager now seamlessly handles Java 21 changes, ensuring smooth Grid execution.
Key Updates:
- Users upgrading to version 2.15.2 will automatically use Java 21 for Grid execution.
- No manual action required – Provar Manager intelligently manages the Java version for Grid execution.
- Users on older builds can continue using Java 11 without any changes, as Grid supports both Java 11 and 21.
- Starting March 20, all latest tags will default to Java 21 for Grid execution.
- For Custom ANT URL, users can choose the Java version based on their setup.
This update ensures compatibility with the latest Java versions with Provar Grid execution, while maintaining support for previous versions for flexibility.
Platform Updates
Operating System Updates
Provar now officially supports MacOS Sequoia, ensuring full compatibility and optimal performance on the latest macOS version.
Browser Compatibility Updates
As part of our pre-release testing, we have confirmed that Automation v2.15.2 is fully compatible with Chrome version 134.
Why is this important?
Including ChromeDriver 134 in Automation v2.15.2 and ensuring compatibility with Chrome 134 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 134, we recommend upgrading to Provar Automation v2.15.2, which includes ChromeDriver 134 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.
Browser and Driver Combinations Recommended for Provar Automation v2.15.2
For a comprehensive guide, please refer to the Browser and Driver Recommendations.
Education
We offer a variety of courses and articles to support you along your journey with us! The University of Provar is available for comprehensive learning and training, while Provar Documentation provides the technical details and step-by-step guidance necessary for effective use and troubleshooting of our products. We value your input—please share your feedback via the end-of-course surveys and helpful article feature, respectively.
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.
- Provar Automation V3
- Automation V3: System Requirements
- Automation V3: 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
- Using Provar Automation V3
- Automation V3: Provar Automation
- Automation V3: Commit a Local Test Project to Source Control
- Automation V3: Creating a New Test Project
- Automation V3: Creating Custom Test Steps
- Automation V3: Provar Test Builder
- Automation V3: Reintroduction of CLI license Check
- Automation V3: Creating Test Cases
- Automation V3: Debugging Tests
- Automation V3: Environment Management
- Automation V3: Managing Test Steps
- Automation V3: Reporting
- Automation V3: Import Test Project from a File
- Automation V3: Import Test Project from Local Repository
- Automation V3: Import Test Project from a Remote Repository
- Automation V3: Running Tests
- Automation V3: Testing Browser Options
- Automation V3: Testing Browser – Chrome Headless
- Automation V3: Provar Feature Flags and Properties Configuration
- Automation V3: Defining Proxy Settings
- Automation V3: Behavior-Driven Development
- Automation V3: Customize Browser Driver Location
- Automation V3: Setup and Teardown Test Cases
- Automation V3: Japanese Language Support
- Automation V3: Reload Org Cache
- Automation V3: Using Java Method Annotations for Custom Objects
- Automation V3: Salesforce API Testing
- Automation V3: Consolidating Multiple Test Execution Reports
- Automation V3: Tags and Service Level Agreements (SLAs)
- Automation V3: Test Plans
- Automation V3: Searching Provar with Find Usages
- Automation V3: Exporting Test Projects
- Automation V3: Tooltip Testing
- Automation V3: Refresh and Recompile
- Automation V3: Secrets Management and Encryption
- Custom Table Mapping in V3
- NitroX in V3
- ProvarDX in V3
- Test Cycles in V3
- Using Custom APIs in V3
- Page Objects in V3
- Automation V3: ProvarX™
- Automation V3: Creating an XPath
- Automation V3: Mapping Non-Salesforce Fields
- Automation V3: Introduction to XPaths
- Automation V3: JavaScript Locator Support
- Automation V3: Create different page objects for different pages
- Automation V3: Maintaining Page Objects
- Automation V3: Refresh and Reselect Field Locators in Test Builder
- Callable Tests in V3
- Functions in V3
- Automation V3: TestCaseErrors
- Automation V3: TestRunErrors
- Automation V3: TestCaseSuccessful
- Automation V3: TestCaseOutCome
- Automation V3: TestCasePath
- Automation V3: StringTrim
- Automation V3: TestCaseName
- Automation V3: DateFormat
- Automation V3: Not
- Automation V3: IsSorted
- Automation V3: StringReplace
- Automation V3: StringNormalize
- Automation V3: DateParse
- Automation V3: DateAdd
- Automation V3: GetEnvironmentVariable
- Automation V3: GetSelectedEnvironment
- Automation V3: NumberFormat
- Automation V3: Using Functions
- Automation V3: UniqueId
- Automation V3: Count
- Automation V3: Round
- Using the Test Palette in V3
- Automation V3: Test Palette Introduction
- Automation V3: Read Test Step
- Automation V3: String Test Steps
- Automation V3: Generate Test Case
- Automation V3: For Each Test Step
- Automation V3: Page Object Cleaner
- Automation V3: Assert Salesforce Layout
- Automation V3: Break Test Step
- Automation V3: UI On Screen
- Automation V3: UI Handle Alert
- Automation V3: UI Assert
- Automation V3: Set Values
- Automation V3: UI With Row
- Automation V3: UI Action
- Automation V3: UI Connect
- Automation V3: Fail Test Step
- Automation V3: While Test Step
- Automation V3: Apex Execute
- Automation V3: List Compare
- Automation V3: UI Navigate
- Automation V3: UI Fill
- Automation V3: If Test Step
- Automation V3: Group Steps Test Step
- Automation V3: Set Values Test Step
- Automation V3: Apex Bulk
- Automation V3: Sleep Test Step
- Automation V3: Switch Test Step
- Automation V3: Finally Test Step
- Automation V3: Wait For Test Step
- Automation V3: Extract Salesforce Layout
- Automation V3: Assert Test Step
- Applications Testing in V3
- Automation V3: Mobile Emulation (Salesforce Mobile)
- Automation V3: Using Provar with Amazon Web Services (AWS) Device Farm
- Automation V3: PDF Testing
- 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: Create a Connection for Office 365 GCC High
- Automation V3: Support for Existing MS OAuth Email Connection
- Automation V3: Gmail Connection in Automation with App Password
- Automation V3: Email Testing in Automation
- Automation V3: OAuth 2.0 MS Graph Email Connection
- Automation V3: Email Testing Examples
- Automation V3: Database Connections
- Automation V3: Web Services
- Data-Driven Testing in V3
- Provar Manager and Provar Automation V3
- Automation V3: Provar Manager – Test Execution Reporting
- Automation V3: Setting Up a Connection to Provar Manager
- Automation V3: Provar Manager Filters
- Automation V3: Importing 3rd-Party Test Projects
- Automation V3: Uploading Test Steps in Provar Manager
- Automation V3: Test Management
- Automation V3: Provar Manager Test Operations
- Automation V3: Provar Manager Test Execution
- Automation V3: Release Management
- Automation V3: Provar Manager Plugins
- Automation V3: Provar Manager Test Coverage
- Automation V3: Provar Manager Setup and User Guide
- Automation V3: Uploading 3rd-Party Test Results
- Automation V3: Uploading Existing Manual Test Cases to Provar Manager with DataLoader.Io
- Automation V3: Quality Journey, Quality Center, and Dashboards
- Automation V3: Object Mapping Between Provar Automation and Provar Manager
- Automation V3: Uploading Callable Test Cases in Provar Manager
- Automation V3: Metadata Coverage with Manager
- Provar Grid and Provar Automation V3
- DevOps with V3
- Automation V3: Setting Java Development Kit (JDK) Environment Variables
- Automation V3: Configuration on Jenkins
- Automation V3: Introduction to Provar DevOps
- Automation V3: Introduction to Test Scheduling
- 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
- Salesforce Testing with V3
- Automation V3: Adding a Salesforce OAuth (Web Flow) Connection
- Automation V3: Internationalization Support
- Automation V3: Salesforce Release Updates
- Automation V3: Adding a Salesforce Connection
- Automation V3: Adding a Log-on As Connection
- Automation V3: Salesforce Lightning Web Component (LWC) Locator Support
- Automation V3: Adding a Salesforce OAuth (JWT Flow) Connection
- Automation V3: Salesforce Console Testing
- Automation V3: Adding a Salesforce Portal Connection
- Automation V3: Visualforce Testing
- Automation V3: List and Table Testing
- Recommended Practices with V3
- Automation V3: Provar Naming Standards
- 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: 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: How to Use Keytool Command for Importing Certificates
- 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
- AI with Provar Automation V3
- Provar Automation V2
- System Requirements
- Browser and Driver Recommendations
- Installing Provar Automation
- Updating Provar Automation
- Licensing Provar
- Granting Org Permissions to Provar Automation
- Optimizing Org and Connection Metadata Processing in Provar
- Using Provar Automation
- 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 Cases into a PDF
- Exporting Test Projects
- 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 Data Generation
- 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 with V2
- Recommended Practices with V2
- 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
- Troubleshooting with V2
- How to Use Keytool Command for Importing Certificates
- Installing Provar After Upgrading to macOS Catalina
- 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 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, Installation and Firewalls
- Memory
- Test Builder and Test Cases
- Provar Manager
- How to Use Provar Manager
- Provar Manager Setup
- Provar Manager Integrations
- Release Management
- Test Management
- Test Operations
- Provar Manager and Provar Automation
- Setting Up a Connection to Provar Manager
- Object Mapping Between Automation and Manager
- How to Upload Test Plans, Test Plan Folders, Test Plan Instances, and Test Cases
- Provar Manager Filters
- Uploading Callable Test Cases in Provar Manager
- Uploading Test Steps in Provar Manager
- How to Know if a File in Automation is Linked in Test Manager
- Test Execution Reporting
- Metadata Coverage with Manager
- Provar Grid
- Release Notes