Setting Up a Connection to Provar Manager
The Provar Manager connection establishes a connection with a Provar Manager instance. It is configured by creating a Provar Manager connection via the Connection tab. The Provar Manager connection (leveraging a normal Salesforce Connection) only requires a user login via OAuth Web Flow.
Prerequisites
There are some prerequisites for setting up a connection to Provar Manager as listed below:
- A Salesforce org with Provar Manager must be already installed.
- A Salesforce user with a Provar Manager license assigned and the Provar Manager permission set assigned too.
How to set up an OAuth Web Flow connection to Provar Manager
Step 1: Create a Connected App.
Step 2: Create a Provar Manager Connection (OAuth WebFlow).
In the Test Settings, navigate to the Connections tab and click the plus (+) sign. The Add New Connection screen is displayed. Give a Connection Name and create an OAuth WebFlow Connection. In the Connection Type field, select Provar Manager then select Provar Manager Connection.
For more information, please see Salesforce OAuth (Web Flow) connection.
In the created OAuth WebFlow connection, you have to provide the details of the Consumer Key, Consumer Secret, and Callback URL that is a part of OAuth WebFlow connection.
Note: The above 3 fields are not the credentials of the user but they are the credentials of the Connected App.
Click Authorise, and it will ask for your credentials; provide your credentials, and when the authorization is successful, the Access Token and Refresh Token are populated.
Note:
- Provar Manager is only available via the Salesforce Lightning Experience.
- Only one Provar Manager connection can be set.
Above: Snapshot of creating a Provar Manager Connection.
When the Provar Manager connection is created, you can see it under the Connections tab.
Above: Screenshot of Provar Manager Connection in Provar.
Creating and linking the Test Project in Provar Manager
Once you have created the Provar Manager connection; a project is created in Provar Manager with a Test Project Name and a unique Test Project Key. For example, the project AY Test Project is created in Provar Manager which has a unique key.
If a user wants to link a Provar test project with an existing Provar Manager project then he has to provide that key (unique key) while creating the Provar Manager connection in Provar.
Note: The project was created in Provar Manager with the same name and unique key.
In Provar Manager –
Log on to the Provar Manager. Click Environments > Test Projects. You can see the AY Test Project created in Test Manager.
Above: Snapshot of the Project created in Provar Manager.
Click on the project (AY Test Project), and you can see the details of the project.
When you click on the project, you can see Test Plans inside it. When you click on Test Plans, you can see Test Suites (these are Test Plan Folders in Provar) and Test Cycles inside it.
Above: Details of the project created in Provar Manager.
Uploading screenshots
To upload screenshots, we have provided one option at the connection level. You can now select the Send Screenshots checkbox in the connection dialog box to upload screenshots.
This option is now available. If you have selected this checkbox then whatever screenshots are captured, they will all be uploaded. If it’s unchecked or de-selected, then no screenshot will be uploaded.
Note: The screenshot capture is allowed only in UI API’s. For example, in the UI Assert test case in the above test case example, you can see the options:
- screenshot before
- screenshot after
Note: In case of an error, a screenshot will always be created and uploaded. So, the maximum number of possible screenshots on a test step execution is 3 (before, after, and on-error). The screenshots can be identified as (before_ and after_).
Report Metadata Coverage
You can also enable Metadata reporting on the connection to Manager by checking the Report Metadata Coverage checkbox. After enabling this feature, Automation will start collecting what Salesforce metadata test cases interact with.
When uploading test cases to Manager, the metadata coverage present locally is also uploaded, allowing you to start running test cases from Manager based on metadata changes tracked in your DevOps pipeline.
When you enable that checkbox in the connection to Manager, it does three things:
- It calculates the metadata coverage (i.e. what Salesforce metadata each Manager-linked test case interacts with) when the connection is saved after checking the checkbox.
- Every time a Manager-linked test case is changed, the metadata coverage is recalculated.
- Every time a test case is uploaded to Manager, its metadata coverage is also uploaded.
QA teams can use this information in at least two ways:
- To report in Manager what Salesforce components they have test cases for.
- To trigger test runs based on particular metadata component changing during the development pipeline.
Removing a Provar Manager Connection
Removing or deleting a Provar Manager connection removes all the Provar Manager associations. Right-click on Provar Manager connection to delete and the Provar Manager connection is deleted, and the context menu Upload to PM won’t be visible in Provar.
For more information, check out this course on University of Provar.
- Provar Automation
- 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
- 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 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
- 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
- DevOps
- Introduction to Provar DevOps
- Introduction to Test Scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous Integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- CircleCI
- Copado
- Docker
- Flosum
- Gearset
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Version Control
- Salesforce Testing
- Recommended Practices
- Salesforce 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
- How to Use Keytool Command for Importing Certificates
- Installing Provar After Upgrading to macOS Catalina
- Browsers
- Configurations and Permissions
- Connections
- DevOps
- Error Messages
- Provar Manager 3.0 Install Error Resolution
- Provar Manager Test Case Upload Resolution
- Administrator has Blocked Access to Client
- JavascriptException: Javascript Error
- macOS Big Sur Upgrade
- 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
- Release Notes