Importing 3rd-Party Test Projects
Provar Manager is built on the Salesforce platform, meaning any tool used to perform ETL (extract, transform, load) tasks on Salesforce can also be used for Provar Manager.
Data Import Tools
Here are some of the most popular ETL tools for Salesforce:
- Salesforce Data Loader is a free client application for the bulk import/export data. Can be used to insert, update, delete, or export Salesforce records.
- Dataloader.io is a popular cloud data loader for Salesforce that lets you quickly and securely import, export, and delete unlimited amounts of data.
- Jitterbit Salesforce Data Loader is a cloud data loader that quickly and easily automates the import and export of Salesforce data.
- Dataimporter.io is a cloud data loading tool that lets you connect, clean, and import data into Salesforce.
Importing Test Cases
When migrating from a test management application to Provar Manager, it is important to know how to import your existing test cases with their test steps.
In this section we use Salesforce Data Loader, but you may want to use a different tool.
Step 1: Store your test cases in a CSV file
The CSV file should only contain test cases, not test steps. Depending on the information you have about your test cases, you may want to add more or less headers to the CSV file, but the following are required:
- Test Case Name (80 characters max)
- Test Type (must be one of the available ones in Provar Manager)
- Status (must be one of the available ones in Provar Manager)
- Test Project ID (not strictly required but highly recommended)
Step 2: Import the test cases
Once the CSV is ready, follow these steps to import it into Provar Manager:
- Open Salesforce Data Loader.
- Click the Insert option.
- Log into the Salesforce org where Provar Manager is located.
- Search for and select the Test Case (provar__Test_Case__c) Salesforce object.
- Choose the CSV file and click Next.
- Ignore the next screen and click Next.
- Click on Create or Edit a Map.
- Search for the test case fields and map them to your CSV file headers by dragging and dropping them.
- Click OK when you are done.
- Click Next.
- Select a folder to store the results. You will need the results file afterward.
- Click Finish and select Yes in the final prompt.
- Review the results and click OK.
Step 3: Import the test steps
Now that the test cases have been imported, it’s time to import their test steps by following the same approach as before but choosing the Test Step (provar__Test_Step__c) Salesforce object instead.
The following headers are required:
- Test Case Id can be found in CSV’s results when importing test cases.
- Action (Short) is limited to 80 characters. We recommend entering the full test step action in the Action (Long) field and entering the truncated version in Action (Short).
- Sequence No defines the order in which test steps should be executed (e.g., 1, 2, 3, etc…)
Importing Test Suites
Test Suites are a great way of grouping and categorizing test cases. In Provar Manager, a test suite can have many test cases, and a test case can be part of many test suites.
Follow these steps to import your test suites and then relate test cases to them.
Step 1: Store your test cases in a CSV file
The CSV file should only contain test suites, not test cases. The following headers are required:
- Test Suite Name (80 characters max)
- Test Project ID (not strictly required but highly recommended)
Step 2: Import the test suites
Once the CSV is ready, follow these steps to import it into Provar Manager:
- Open Salesforce Data Loader.
- Click the Insert option.
- Log into the Salesforce org where Provar Manager is located.
- Search for and select the Test Suite (provar__Test_Suite__c) Salesforce object.
- Choose the CSV file and click Next.
- Ignore the next screen and click Next.
- Click on Create or Edit a Map.
- Search for the test case fields and map them to your CSV file headers by dragging and dropping them.
- Click OK when you are done.
- Click Next.
- Select a folder to store the results. You will need the results file afterward.
- Click Finish and select Yes in the final prompt.
- Review the results and click OK.
Step 3: Relate test cases to their test suites
Now that the test suites have been imported, it’s time to relate the existing test cases to their test suites following the same approach as before, but choosing the Test Suite Case (provar__Test_Suite_Case__c) Salesforce object instead.
These are the required headers in the CSV file:
- Test Case Id. You can use Dataloader to export existing test cases with their IDs.
- Test Suite Id. You can find this ID in the results CSV created when importing test suites.
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 – 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
- 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
- Provar AI Assistant Popup Test