- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Data-Driven Testing
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 to read about the actions you can take within the Test Explorer panel.
A prerequisite for data-driven testing is an Orchestrator version equal to, or higher than 2022.4
When you configure data sources for your data variation, you can choose from the following options:
- File, if you want to use Excel and CSV files.
- Auto Generate, for test data that is automatically generated to cover as many paths as possible during execution.
- 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 if you have configured a JSON schema and added a test data queue in Orchestrator.
The following table lists the actions that you can take for test cases that contain data variation.
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. |
4. (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. 5. Click Import to save changes. Note: 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. |
Note: 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.
|
|