# Data-Driven Testing

> Data-driven testing in Studio, which runs test cases across multiple data variations sourced from Excel files or Orchestrator assets.

## Overview

Data-driven testing lets you test RPA workflows and applications across various scenarios. To ensure your test cases use the prepared test data, debug and run data-driven test cases only from the Test Explorer panel. Visit [Working With Test Explorer](https://docs.uipath.com/studio/standalone/2026.10/user-guide/test-explorer#working-with-test-explorer) to read about the actions you can take within the Test Explorer panel.

## Prerequisites

A prerequisite for data-driven testing is an Orchestrator version equal to, or higher than 2022.4

## Data sources

When you configure data sources for your data variation, you can choose from the following options:

* [File](https://docs.uipath.com/studio/standalone/2026.10/user-guide/test-data-file), if you want to use Excel files.
* [Generate with Autopilot](https://docs.uipath.com/studio/standalone/2026.10/user-guide/ai-generated-test-data), for test data that you can refine using AI-powered capabilities.
* [Data Service](https://docs.uipath.com/studio/standalone/2026.10/user-guide/data-service#data-service), if you use Data Service entities (Automation Cloud only).
* Existing data for any type of data that has already been stored in your project, in the Test Data folder.
* [Test Data Queue](https://docs.uipath.com/studio/standalone/2026.10/user-guide/test-data-queues#test-data-queues) if you have configured a [JSON schema and added a test data queue in Orchestrator](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-test-data-queues-in-orchestrator).
* [Auto Generate](https://docs.uipath.com/studio/standalone/2026.10/user-guide/auto-generated-test-data), for test data that is automatically generated to cover as many paths as possible during execution.

## Manage test data

The following table lists the actions that you can take for test cases that contain data variation.

 <colgroup>
  <col/>
  <col/>
  <col/>
 </colgroup>
 
  
     Action  
     Description  
     Procedure  
  
 
 
  
    Update test data 
     Update the imported test data by choosing whether to create a new file or overwrite existing data. You can use this when you have made any changes to the Excel file. Any new columns will be added as arguments to the test case.  For Data Service entities, you can update the test case using new filter through the Query Builder .  
   
      
         Open Studio and navigate to your project. 
         In the Project panel, right-click a test case with data variations and select Update test data . 
         Select a data source from the Source dropdown list. 
      
        
           For Files (e.g., Excel), you need to browse for the file and select the Worksheet . You can select individual or all values from the file. 
           For Data Service , you need to select an entity. 
           For Test Data Queue , you need to select a test data queue. 
           (Optional) Select Update all test cases using the same test data to update all the test cases that use the test data that you are currently editing. Then, select Import to save changes. You can perform this action in Test Explorer by right-clicking a file, and then choosing Update Test Data .
        

  
  
    Remove test data 
     Remove test data from the test case.  
   
      
         Open Studio and navigate to your project. 
         In the Project panel, right-click a test case with data variations and select Remove test data . 
      
You can perform this action in Test Explorer by right-clicking a file, and then choosing Remove Test Data . 
  
  
    Modify test data JSON file 
     Update test data directly into the JSON file. The file is created after adding test data to the test case.  Important: Only for  test data files  . 
   
      
         Open Studio and navigate to your project. 
          Navigate to Project &gt; Test Data and open the JSON file with a code editor.  The JSON file name is stored as <code>ExcelName_SheetNo.json</code> .