Reading Data from Excel
Data-driven testing is a helpful feature for the following scenarios:
- When business users would like to have ownership over the test data in your automated tests
- When you have multiple data permutations, and you would like to loop through data sets
- When you would like to perform various calculations on your data and use Excel as a method of deriving the fields
Provar has Read and Write test steps to read data from an Excel sheet or a database and write data to an Excel spreadsheet.
This page describes how to configure Provar to test using data from Excel. You can also refer to Write Data Into Excel for more information.
To read from the Excel sheet, first, get your Excel file ready on your local machine.
Note: It is a good practice to save the file in the templates folder in your workspace.
Next, read the Excel file into your test case using Add Parameter Value Source. You can do this from any test step, but you will often find it helpful to do it on your For Each test step if you use one. (For Each is often used within Data-Driven Testing to iterate the same action through each data row.)
To read the Excel data into your Test Case, click the Add Parameter Value Source icon (
This will add the following new section to your Test Step:

You can populate this as follows:
Step 1: If you are on a Windows machine, navigate to your Excel file and highlight the range of cells you want to read into Provar. Then select CTRL+C to copy. Navigate to Provar and select the Populate From File icon (
Step 2: If you are using a Mac, you will need to populate File, Worksheet, and Values Range manually. Use File Chooser (
Step 3: In the Name field, select the orientation of the headers.
Step 4: In the Where field, specify any filter you want to be applied to the data being imported.
Step 5: In Variable, specify your preferred object name for the results (the default is ExcelData).
Step 6: Then parameterize the Test Case.
An example Excel spreadsheet with the corresponding Parameter Value Source parameters is populated below.


Add to Test Case
Once you have read the data from the Excel sheet, you need to use it in your test case. This is typically done using a For Each or While test step to loop through multiple rows and create a test step to make the data.
Step 1: Use Content Assist to access the fields in the SourceData object.
Step 2: Specify the list Name (e.g., SourceData) and the Value Name For Each test step. (The Value Name is the name for the current iteration.)
Step 3: Use the full stop to access the column headings.

- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- 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
- Override auto-retry for Test Step
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- 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 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
- DevOps
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Provar Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Provar 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 DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Provar 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
- Team foundation server
- Version control
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Dynamic Forms
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Performance Best Practices
- Testing best practices
- Troubleshooting
- Browsers
- Configurations and permissions
- Connections
- DevOps
- Error messages
- 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
- Update to Opportunity field validation behaviour
- Licensing, installation and firewalls
- Memory
- Test Builder and test cases
- Release notes