Spring ‘24 Release 2 (v2.12.1.2)
Executive Summary
We’re excited to announce the latest updates to the Provar product suite with our Spring ‘24 Release 2. This newest release is now available for installation via the Provar Success Portal. This release includes compatibility with the Salesforce Spring ‘24 release to keep your tests working as expected.
Notice: Selenium 4 Upgrade
In the latest Provar Spring ‘24 Release 2, the Selenium and related dependencies have been upgraded to version 4.16.1. It provides enhanced test automation features, more reliable testing capabilities, and better-quality test scripts.
This upgrade may impact users using existing PageObjects, Page Operations, Custom APIs, or SSO Java files. If so, users could need to make minor adjustments to classes and functions after installing the latest Provar release. For more guidance and instructions on how to make these changes, please visit our help page.
Provar Automation Features
Highlight Panel Component Support
We’ve introduced support for independent mapping and testing capabilities for the highlight panel. The intention is to maintain the current scripts’ functionality, the test cases’ cleanliness, and the modifications’ compatibility with Salesforce’s Dynamic Actions feature. This enables users to create tests targeting the highlight panel with complete support for various field types and buttons and compatibility with standard and flexible pages. Find more information here.
Dynamic File Selection for API-Based Records
To improve the Template Editor component and enable changeable file paths, Provar now offers flexibility in file selection during API tests. This allows users to choose different files dynamically using local and global variables. When applicable, Content Assist also works in the template editor.
Renamed Connections Reflected in Logs Using GUIDs
If a connection with a GUID is renamed, the execution works fine, but the logs are now reflected with a new name. The logs shown in the execution window are consistent with the GUID mechanism. If the connection has been renamed but the test case has not been updated, the logs will show the new connection name with an info message.
Dynamic Action Support
Provar allows users to map and perform Dynamic Actions, increasing the flexibility and efficiency of test case generation. Legacy scripts for action buttons (in the highlight panel) work properly when the action is changed to Dynamic Actions, so users do not have to recreate the scripts. Find more information here.
NitroX Editor/UI Changes
The NitroX UI has been modified to add an editor with capabilities related to page mapping/structure in Provar Automation. Users can launch the new editor in a new tab by double-clicking on the custom JSON (.po. JSON) files. The page structure is displayed in a tree-like fashion. Standard components, added to NitroX’s tree structure through the Test Builder, are shown alongside custom components, added by the ‘+’ symbol on a node.
Provar Automation Enhancements
Instrumentation License Type and Usage
To improve the deployment of instrumentation for collecting detailed data on license usage. The emphasis is on capturing license types, keys, timestamps, client information, usage times, and concurrency levels during ANT version job executions and Provar Automation logins. The purpose is to proactively identify and warn consumers about incorrect license usage as a preventative measure to ensure proper licensing. When a user logs in to Provar Automation, the license type, license key, time, date, and customer are recorded. Instrumentation will return data about which license type was used for execution and which license type is used for Provar Automation or Provar Grid.
New Context Menu
We have upgraded the context menu according to the functionality and grouped various menu items.
Callable Test Step in Test Builder
Provar users can easily add a Callable Test Case to another Test Case as a Test Step after selecting a test case from a list of possible callable test cases. This update aims to make the Test Palette more efficient, removing the switch to Provar Studio requirement.
Collapsible Option Section
In Test Builder, the Options section in the Test step editor is now collapsible by default. The users can choose to expand the section and collapse it.
Renamed Connection Log as a Warning
When there is an outdated connection name in use by a running test, Provar will highlight this in the test log as an orange warning message.
Metadata Process Improvement
The Org and Connection metadata processing has been analyzed and improved to shorten processing times and enhance Provar Automation performance. We have effectively boosted Quick Actions, Tabs Navigation, and Apps Navigation performance. These enhancements positively influence your test projects, which include up to 25% improvement in downloading metadata and loading the Org browser.
In addition, we effectively addressed Provar Automation’s longer startup time. With the most recent release, it now loads up to 60% faster than before.
Undo and Redo Functionality
Provar has added Undo and Redo capabilities, as well as shortcuts, to the Java code editor. However, a known bug in the Page Object Editor causes Undo and Redo not to work as intended. A workaround was offered for the Page Object Editor.
GUID Status Detection
A project’s GUID status is now identifiable and reported via Provar (Yes/No). The reporting system allows cross-referencing data points to determine which customers have enabled GUIDs in their projects. Reporting is triggered for all project launch mechanisms, including ANT, ProvarDX, Jenkins, and Grid.
Provar Manager Features & Enhancements
With Provar Manager version 3.1.1, the following features and enhancements are now available:
- Improved Quality Center performance.
- Improved Apex Unit Test Coverage reporting.
- Updated OpenAI models used for test case generation and RCA reporting.
New UI and Improved Apps
We have improved the UI, apps, and permission sets for Release Management, Test Management, and Test Operations.
New UI Tools to Manage Test Suites
Users can now mass-select the test suites and test cases for any test plan schedule records, removing the hassle of adding them individually. The test suites and test cases can also be searched manually.
New Provar Manager API
With Provar Manager, you can get the status of any REST API requests and retrieve test results. You can also utilize the API to execute test jobs from external systems.
Email and Slack Alerts
We have implemented an email and Slack notification system for Test Plan schedule jobs. Users can enable email notifications and enter recipient email addresses for each schedule. When a Test Plan schedule job is completed or failed, and the email notification option is enabled, an email is sent to the provided addresses to confirm the job’s status. Similarly, users can also opt to receive Slack alerts for the same, using a toggle to enable Slack Notifications.
Provar Grid Features & Enhancements
Support for Bitbucket Enterprise Server & Cloud
Customers with their own Enterprise Server or Cloud instances of Bitbucket will have their own BitBucket URL. Provar Manager now supports importing branches from these instances.
Support for Multi-environment Test Schedule Executions
By default, each branch test selected for execution in a Test Plan Schedule is assigned to a specific environment. If you would like to execute your tests against multiple or different environments, users now have the option to Override the Environment.
Users can then take their pick from the environments to run their tests against.
Selecting multiple environments will mean creating a ‘Test Plan Schedule Job’ for each environment.
This new feature allows users to configure tests against different environments, platforms, browsers, and browser versions from a single schedule.
Email and Slack Notifications for Test Plan Schedule jobs
A new ‘Alert’ feature has been added to Provar Manager for Test Plan Schedules. This also applies to Provar Grid jobs. Email notifications can be configured to be sent to a list of your chosen users on success or failure.
Alternatively, you can configure your alerts to trigger a Slack webhook, sending the job details to the chosen Slack channel.
Note: Once a user has upgraded their project to 2.12.2 or above, they cannot run tests on an older version of Provar, whether in Grid or locally, because the tests are no longer backwards compatible due to Selenium changes. To resolve this, users must remove all selenium plugins from the manifest file, beginning with org.seleniumhq. Grid users must ensure that any tests they create and run on Grid schedules must use version 2.12.1.1 or lower (not 2.12.2).
Platform Updates
Browser Compatibility Updates
As part of our pre-release testing, we have confirmed that Automation v2.12.2 is compatible with Chrome version 123.
Why is this important?
Ensuring that Automation v2.12.2 includes ChromeDriver 123 and is compatible with Chrome 123 eliminates the risk of incompatibility issues, which could prevent test cases from working as expected.
How can I use this?
If you want to start using Chrome 123, we recommend upgrading to Provar Automation v2.12.2, which will use ChromeDriver 123 out of the box.
Automation will automatically attempt to download the correct ChromeDriver if it detects a driver exception. If your organization’s security protocols block the automatic download, you can manually override the ChromeDriver.
To downgrade or revert the ChromeDriver, refer to this support article that explains how to use a ChromeDriver that differs from the one provided by default in your Provar Automation installation.
Browser and Driver Combinations Recommended for Provar Automation v2.12.2
Please refer to the Browser and Driver Recommendations support article for a comprehensive guide.
Salesforce Jars Upgrade
We updated the revised jars following the Salesforce Spring ’24 Release (version 69.0) to use them in future releases. To accomplish this, we updated the necessary jars, added the new objects to the translation files, and removed the old unused Salesforce jars.
End of Life for TEE (Team Explorer Everywhere) Plugin Support
We have discontinued the support and use of the TEE plugin for Provar Automation. If the user updates to the new version of Provar that has TEE disabled, the TEE plugin is no longer installable and has no effect if TEE is already in use.
Note: The SVN, JIRA plugin, and Legacy Editors will be removed in future.
Provar Labs
The Provar Labs team is happy to announce that Provar Assistant is now available. Provar Assistant is an AI chatbot designed to provide instant support and real-time responses to your Provar-related questions. It’s your go-to resource for rapid access to useful product information, best practices, and troubleshooting advice. Access Provar Assistant and log in with your Google or Success Portal. You may learn more about Provar Assistant here.
University of Provar
The University of Provar is excited to announce an updated Provar Manager Essentials Certification. Check it out to familiarize yourself with the new Manager updates!
Customer Support
Providing ongoing support is our promise to you. If you have any questions regarding this release, please contact us anytime; we are happy to help. To get in touch, simply log in to the Provar Success Portal and select ‘Raise a Case,’ or reach out directly to 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