Automation V3: 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.
- Home
- 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
- AI with Provar Automation V3
- Using Provar Automation V3
- Automation V3: Feature-by-Feature Guide
- Automation V3: Provar Automation
- Automation V3: Creating a New Test Project
- Automation V3: Import Test Project from a File
- Automation V3: Import Test Project from a Remote Repository
- Automation V3: Import Test Project from Local Repository
- Automation V3: Commit a Local Test Project to Source Control
- Automation V3: Salesforce API Testing
- Automation V3: Behavior-Driven Development
- Automation V3: Consolidating Multiple Test Execution Reports
- Automation V3: Creating Test Cases
- Custom Table Mapping in V3
- Functions in V3
- Automation V3: Using Functions
- Automation V3: Count
- Automation V3: DateAdd
- Automation V3: DateFormat
- Automation V3: DateParse
- Automation V3: GetEnvironmentVariable
- Automation V3: GetSelectedEnvironment
- Automation V3: IsSorted
- Automation V3: Not
- Automation V3: NumberFormat
- Automation V3: Round
- Automation V3: StringNormalize
- Automation V3: StringReplace
- Automation V3: StringTrim
- Automation V3: TestCaseErrors
- Automation V3: TestCaseName
- Automation V3: TestCaseOutCome
- Automation V3: TestCasePath
- Automation V3: TestCaseSuccessful
- Automation V3: TestRunErrors
- Automation V3: UniqueId
- Automation V3: Debugging Tests
- Automation V3: Creating Custom Test Steps
- Automation V3: Defining Proxy Settings
- Automation V3: Environment Management
- Automation V3: Exporting Test Projects
- Automation V3: Japanese Language Support
- Automation V3: Customize Browser Driver Location
- Automation V3: Managing Test Steps
- NitroX in V3
- Automation V3: Provar Test Builder
- ProvarDX in V3
- Automation V3: Refresh and Recompile
- Automation V3: Reintroduction of CLI license Check
- Automation V3: Reload Org Cache
- Automation V3: Reporting
- Automation V3: Running Tests
- Automation V3: Searching Provar with Find Usages
- Automation V3: Secrets Management and Encryption
- Automation V3: Setup and Teardown Test Cases
- Automation V3: Tags and Service Level Agreements (SLAs)
- Test Cycles in V3
- Automation V3: Test Plans
- Automation V3: Testing Browser – Chrome Headless
- Automation V3: Testing Browser Options
- Automation V3: Tooltip Testing
- Using Custom APIs in V3
- Callable Tests in V3
- Data-Driven Testing in V3
- Page Objects in V3
- Automation V3: Introduction to XPaths
- Automation V3: Creating an XPath
- Automation V3: JavaScript Locator Support
- Automation V3: Maintaining Page Objects
- Automation V3: Mapping Non-Salesforce Fields
- Automation V3: ProvarX™
- Automation V3: Refresh and Reselect Field Locators in Test Builder
- Automation V3: Create different page objects for different pages
- Applications Testing in V3
- Automation V3: Database Connections
- Automation V3: PDF Testing
- Automation V3: Email Testing in Automation
- Automation V3: Email Testing Examples
- Automation V3: Gmail Connection in Automation with App Password
- 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: Support for Existing MS OAuth Email Connection
- Automation V3: OAuth 2.0 MS Graph Email Connection
- Automation V3: Create a Connection for Office 365 GCC High
- Automation V3: Mobile Emulation (Salesforce Mobile)
- Automation V3: Using Provar with Amazon Web Services (AWS) Device Farm
- Automation V3: Web Services
- Automation V3: Integrating with Jira
- Automation V3: Provar Feature Flags and Properties Configuration
- Automation V3: Using Java Method Annotations for Custom Objects
- 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: Override Auto-Retry for Test Step
- Automation V3: Assert Test Step
- Automation V3: Extract Salesforce Layout
- Automation V3: Wait For Test Step
- Automation V3: Finally Test Step
- Automation V3: Switch Test Step
- Automation V3: Sleep Test Step
- Automation V3: Apex Bulk
- Automation V3: Set Values Test Step
- Automation V3: Group Steps Test Step
- Automation V3: If Test Step
- Automation V3: UI Fill
- Automation V3: UI Navigate
- Automation V3: List Compare
- Automation V3: Apex Execute
- Automation V3: While Test Step
- Automation V3: Fail Test Step
- Automation V3: UI Connect
- Automation V3: UI Action
- Automation V3: UI With Row
- Automation V3: Set Values
- Automation V3: UI Assert
- Automation V3: UI Handle Alert
- Automation V3: UI On Screen
- Automation V3: Test Palette Introduction
- DevOps with V3
- Automation V3: Introduction to Provar DevOps
- Automation V3: Introduction to Test Scheduling
- Automation V3: Setting Java Development Kit (JDK) Environment Variables
- Automation V3: Configuration on Jenkins
- 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
- 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: How to Use Keytool Command for Importing Certificates
- 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: 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
- Automation V3: Setting Up a Connection to Provar Manager
- Automation V3: Provar Manager – Test Execution Reporting
- 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
- Automation V3: Test Plan Scheduling
- Automation V3: Provar Manager Version Control Setup
- Automation V3: Setting Up Provar Grid