Provar Manager Filters
Let’s first look at the filters (the checkboxes) on the top-right of the screen. You can use these as per your requirements. Although these filters are self-explanatory, we have provided brief explanations as mentioned below:
- All Files – It will show all the files (that are in Provar).
- Missing Files – The files i.e. the test objects unavailable in Provar Manager.
- Changed Files – The files, i.e., the test objects that have been changed. (For example, renamed).
- Failures – In case some failure has occurred. Failure can only happen when you have uploaded something, and it hasn’t been uploaded, and it failed.
We have given some examples below. We have selected All Files, and it is displayed as given below:
Above: Snapshot of filtering DEV environment that is renamed to DEV-Updated.
As a user, if you want to upload Provar Test Objects to the Provar Manager, right-click on the Test Plan (i.e., test object) and click Upload to PM. Please see the screenshot given below.
Above: Snapshot of Upload to PM context menu.
An Upload to Provar Manager dialog is displayed. You will also notice a message Fetching Test Objects from Provar Manager.
Above: View of Upload to PM dialog fetching test objects from Provar Manager.
Select All files check box at the top of the dialog box, and the fetched data is displayed in the dialog. Users can select and upload the relevant files to the Provar Manager.
You can see 5 fields on the Upload to Provar Manager dialog. These are explained below.
- Provar Test Object – This field shows the test objects in Provar.
- Test Manager Object – This field shows the test objects in Provar Manager.
- Match Type –
- Inferred: It is an exact match of the Provar test object in Test Manager, but it isn’t linked. It has the same configuration in Provar Manager. You can link it. You need to explicitly link it. (There is no need to create the object, it is already created.)
- Blank: The Provar test object is not available in Provar Manager.
- Linked: The same test object is available in Provar and Provar Manager. And it is linked.
- Status –
- Missing: The missing status is shown for test objects that are missing in Provar Manager. For example, you created a Test Plan but didn’t upload it in Provar Manager yet, so it will show the Status as Missing.
- “?”: Either something has changed in the test object, or the Provar cannot comprehend the change. This is an unknown status.
For example, you renamed a test object but didn’t upload it in Provar Manager (i.e., there is a mismatch in Provar and Provar Manager). You must update it accordingly. So, when you upload it, it will also be renamed in Provar Manager.
- “-”: There is no change in the data. For example, AY Plan 1 is AY Plan 1.
- Failed – If there is an error while uploading the test object, then the Status is displayed as Failed, and on hovering over it, you can see the message.
- Actions –
- Link: Click the link to associate the Provar test object to Provar Manager.
- Unlink: Click unlink to dissociate the Provar test object from the Test. Manager (If it is linked by mistake, you linked Plan 1 to Plan 2.)
Note: If the data in Provar Test Object and Provar Manager Object field matches as one-to -then it will be displayed, otherwise it will be blank. The other columns contain additional information which is helpful to the user.
The Provar Test Object field shows the local Provar data, i.e., the test objects in Provar. The Provar Manager Object field shows the Provar Manager data, i.e., the test objects in Test Manager. If this data matches one-to-one, then Provar will show this data. Otherwise, it is blank. And, then we have some additional information (Match Type, Status, Actions) which are helpful for the user.
For example, suppose the user had earlier uploaded a plan (AY Plan1), which exists with the same name in Test Manager (AY Plan1). Then it is an exact match, and the Match Type is shown as Inferred; it is a potential match, and you can link it as displayed in the Actions column.
In the Actions field, click the link. A Test Manager Object selection dialog is displayed.
Note: It will display information depending on which test object the user clicked the link. For example, if a user clicks the link against the Test Plan (AY Plan1), he can see all the Plans only.
Above: The user clicks a link in the Actions field to link the Test Plan.
Users can see only the plans listed in the Provar Manager Object selection dialog.
Note: If the user clicked the link against the Test Plan Folder, then the Test Plan folder is Test Suite in Provar Manager; only test suite(s) would have been displayed.
Similarly, if the user had clicked the link against the test case, only test cases would have been displayed.
Note: The test objects (Test Case, Test Instance, Test Plan, Test Folder, except the Environment.) can be similarly uploaded in Provar Manager. The test object against which the user clicks the link is the only one linked; there isn’t any mismatch.
Now, create a new environment in Provar.
In the bottom section of the Provar, click Environments. Click ‘+’. An Add new Test Environment screen is displayed. Enter the Environment Name and Description. For more information, please see Provar Environment Management.
Note: Similarly, you can create environments as needed, like QA, UAT, etc.
Click Upload to Provar Manager. The Upload to Provar Manager dialog is displayed.
Select the All files checkbox. All the test objects are loaded into the environment. So, this fetches all the data. Here we have 5 types of objects – Test Case, Test Instance, Test Plan, Test Folder, and Environment. This triggers 5 different queries to the Provar Manager.
Note: Test Environments are always displayed at the top and have no hierarchy.
So, if the user wants to see the environments, it will trigger a query for the environment in Test Manager. In Test Manager, click Environments, and all the environments are displayed.
Above: Snapshot of Environments in Provar Manager.
Next, we have triggered a query on all the Test Plans, which are displayed.
Example 1: Explaining the DEV-Updated example.
If we look at the above screenshot for better understanding. Provar shows the environment as DEV – Updated. Test Manager shows the environment as DEV. So, if you see here, Match Type shows as Linked (this means that data was earlier linked in local at sometime (when it was in sync), but now it is renamed.), and Status shows “?” (and this is the reason it shows a question mark (?)).
Example 2: An example when there is no change.
Let’s see another example of AY Plan 1. It shows Match Type as Linked and Status as “- “, which means that there has been no change.
Now, you have to upload DEV-Updated. Click Upload. So, it will update it and not create it.
In Provar Manager –
Click Environments. You’ll see DEV-Updated in Provar Manager.
Above: Snapshot of Dev-Updated example in Provar Manager.
- Provar Automation
- Installing Provar Automation
- Updating Provar Automation
- Using Provar Automation
- API Testing
- Behavior-Driven Development
- Creating and Importing Projects
- Creating Test Cases
- Custom Table Mapping
- Debugging Tests
- Defining a Namespace Prefix on a Connection
- Defining Proxy Settings
- Environment Management
- Exporting Test Cases into a PDF
- Exporting Test Projects
- Override Auto-Retry for Test Step
- Managing Test Steps
- Namespace Org Testing
- Provar Automation
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI License Check
- Reload Org Cache
- 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 Plans
- Testing Browser Options
- Tooltip Testing
- Using the Test Palette
- Test Palette Introduction
- Control Test Steps
- Generate Test Case
- List Compare
- Page Object Cleaner
- Read Test Step
- String Test Steps
- UI Test Steps
- Using Custom APIs
- Callable Tests
- Data-Driven Testing
- Page Objects
- Block Locator Strategies
- Introduction to XPaths
- Creating an XPath
- Label Locator Strategies
- Maintaining Page Objects
- Mapping Non-Salesforce fields
- Page Object Operations
- Refresh and Reselect Field Locators in Test Builder
- Using Java Method Annotations for Custom Objects
- Applications Testing
- Database Testing
- Document Testing
- Email Testing
- Mobile Testing
- OrchestraCMS Testing
- Salesforce CPQ Testing
- ServiceMax Testing
- Skuid Testing
- Vlocity API Testing
- Webservices Testing
- Provar Manager
- Provar Manager Setup and User Guide
- Installing Provar Manager
- Configuring Provar Manager
- How to Use Provar Manager
- Managing Your Testing Life Cycle
- Provar Manager Test Execution
- Test Executions and Defect Management
- Provar Manager Test Coverage
- How to Integrate Provar Manager
- 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
- Provar Manager Plugins
- Uploading Existing Manual Test Cases to Provar Manager with DataLoader.Io
- Provar Grid
- 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
- Gearset DevOps CI/CD
- 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
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team Foundation Server
- Version Control
- Salesforce Testing
- Adding a Salesforce Connection
- Assert Page Error Messages on Add/Edit Product
- Internationalization Support
- List and Table Testing
- Salesforce Console Testing
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) Locator Support
- Salesforce Release Updates
- Visualforce Testing
- Best Practices
- Configurations and Permissions
- Error Messages
- Licensing, Installation and Firewalls
- Test Builder and Test Cases
- Release Notes