- 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
- Workflow Analyzer
- 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
- Variables
- Arguments
- Imported Namespaces
- 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
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User
Data Service
You can use Data Service, both in Automation Cloud and Automation Suite, as a source for your data-driven testing. The data is imported from Data Service entities, exposing the fields as workflow arguments. All imported entities are stored in the Project tab, under Entities.
You can perform data-driven testing with Data Service only with version 22.4 or higher of the Testing.Activities package.
- When you configure a Data Service source, the data is fetched from the first entry in the enitity.
- To Run and Debug test cases with dynamic test data, use the Test Explorer. The data comes from the Data Service entity during runtime, and the Test Explorer populates the values at runtime.
- If you close your session and open the project again, you need to run the file with data variation again to load the test data.
- If you update the entity, you need to run the file with the data variation to load the updated test data.
- Test cases with data variations that are empty are marked as failed.
- A test case setup is created in Orchestrator, when you execute test cases containing data variations from Data Service.
If you create a data-driven test case that accepts an input argument, publish it in a test set, and attempt to define the argument value directly from the Orchestrator UI, the input argument value does not get passed to the test variations.
Workaround: To overcome this limitation, add the input argument directly to the Data Service entity.
When you add test data to your test case, you can filter the entity to retrieve only specific fields from Data Service. You can configure the filters by using the built-in Query Builder.
- Create a new test case with test data, or add test data to an existing test case.
-
Click Source and select Data Service from the dropdown list.
Note: If the option is not available, check the requirements. - Select an entity or use the search function to look for it.
- Click the Filter icon to open Query Builder.
- Use the first dropdown list to filter by a criterion (e.g.,
CreateTime). - (Optional) You can add rows and groups when you click Add and then configure the conditions.
- (Optional) You can select to filter by all or any of your criteria by choosing AND or OR.
- Enter a Name for your filter.
- (Optional) Use the Range to configure specific row intervals. This is useful if you have hundreds of fields in your entity.
-
Click OK to confirm.
The data is fetched from the entity and added to the test case as an Argument Type. Only the first entry in the entity is fetched. You can access the data through the arguments.
- Already using a CSV file for your data-driven testing? You can upload it to Data Service using batch activities.
- Update or remove test data.
