- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- 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-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- 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-017 - Invalid parameter modifier
- 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
- Variables
- Arguments
- Imported Namespaces
- Coded automations
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Trigger-based Attended Automation
- Recording
- UI Elements
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- VMware Horizon Automation
- Salesforce Automation
- SAP Automation
- macOS UI Automation
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for Safari
- Extension for VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Test Suite - Studio
- Troubleshooting
- About troubleshooting
- Assembly compilation errors
- 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
- Validation of large Windows-legacy projects takes longer than expected
Studio User Guide
Auto-generated Test Data
You can use automatically generated test data to execute test cases using various sequences of data. Different data combinations can be used for both RPA and application testing.
Int32
, Bool
, String
) for an If decision tree. You use the auto-generate feature to generate values for your test cases to cover as many paths as possible during execution.
As part of symbolic execution, the workflow is interpreted and provided with values based on your arguments. The generated values will solve any conditional branch in the workflow.
- Generate values to solve workflow conditions (e.g.,
If
,Switch
). - Assign values to arguments and variables.
- Argument comparison with values or other arguments.
Decimal |
String | Array | Dictionary |
---|---|---|---|
Double |
Boolean | Of primitive values: short, int, long, float, double, byte, char, and boolean. |
For keys, you can use variables, arguments, or literal data. Primitive values are supported (short, int, long, float, double, byte, char, and boolean) You can only use one key value pair for a dictionary argument.
For example, you can use
dictionary["Name"] ==
"John" , but not dictionary["Name"]["Age"]
== 34 |
Float |
Byte | ||
Int32 |
Int64 | ||
Long |
Short |
- All boolean and numeric operations.
- For loops, a pass-at-least-once strategy is used that attempts to go through the loop at least one time.
- For strings, data is generated for the following functions:
Contains
,Equals
,StartsWith
,EndsWith
,Concat
.
- Update Testing Activities package to version 22.4.
- Create or use an existing automated workflow.
- Create arguments as parameters for auto-generated test data. See Supported argument types.
When you select Auto Generate as data source for your test data, a data table is generated with default values based on your arguments. A column is created for every argument where the first data row shows the default values.
- Right-click an existing workflow and select Create Test Case.
- Enter a name for your test case and change the default location, if required.
- (Optional) Add test case to execution template.
- In the Test Data tab, click Source and select Auto Generate from the dropdown list.
- Select the columns that you want to add.
- (Optional) Edit the data table values or delete entire rows and columns.
- (Optional) Click Add Row to generate another row of default values. You can edit the values.
-
Click OK to confirm.
The data is generated and added to the test case. You can access the data through the arguments.