- Hardware and Software Requirements
- Update Studio
- Command Line Parameters
- Supported Applications and Technologies
- Enabling Gmail for Email Activities
- Opting Out of Telemetry
- Studio Executables
- About Publishing Automation Projects
- Designing Automations
- Managing Activities Packages
- Configuring Activity Project Settings
- Signing Packages
- Importing Entities
- Modern Design Experience
- Linking a Project to an Idea in Automation Hub
- Using the Data Manager
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Registering custom services
- Before and After contexts
- Application Testing
- Test Cases
- RPA Testing
- Execution Templates
- Test Case Templates
- Mock Testing
- API Test Automation
- About extensions
- About the SetupExtensions tool
- Extension for VMware Horizon
- SAP Solution Manager plugin
- Excel Add-in
- 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
- Automating applications running in AppContainer mode
- Automating applications running as administrator
- Validation of large Windows-legacy projects takes longer than expected
Data-driven testing allows you to test your RPA workflows and applications to make sure that the automations can handle multiple scenarios.
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.
Manage test data
The following table lists the actions that you can take for test cases that contain data variation.
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.