- 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
- Troubleshooting
- 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
- Studio testing
- Introduction
- Creating a Test Automation project
- API Test Automation
- Execution Templates
- 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
Creating a Test Automation project
Test Automation projects are used to perform application testing. Only App Test Developer users can create and publish Test Automation projects.
This tutorial explains how to create a simple Test Automation project in Studio. The example automates a browser test that opens the built-in Google calculator and verifies if it functions correctly. While the example uses low-code activities, you can implement the same steps using coded automations and coded automation APIs.
- Open Studio.
- On the Start page, select Test Automation under the New Project section.
- In the New Blank Test Project
window, perform these steps:
- Enter a name for the new test
project.
Note: The project name cannot exceed 128 characters.
- Optionally, enter a description.
Note: The project description cannot exceed 500 characters.
- Select Show advanced
options:
- Choose the project Location.
- Set Compatibility to Windows.
- Set Language to VB.
Figure 1. New Blank Test Project window
- Enter a name for the new test
project.
- Select Create.
The new testing project is opened in Studio.
- Open the TestCase.xaml file
within the project, and follow these steps to build the test:
- Add a Use Application/Browser activity
to indicate the application that you want to automate. In this example, use
the activity to indicate a Google browser tab.
The rest of the activities that you want to use to automate the steps performed in the indicated application, must be added within the Do block of the Use Application/Browser activity.
- Inside the Do block add the following activities:
- Add a Set Text activity and
indicate the Google search bar.
Set the Text field to
"calculator"
. -
Add a Click activity and indicate the Google search icon to initiate the search.
-
Add four more Click activities to form the radical of 25 math expression.
- Add a Get Text activity to
retrieve the result offered by the built-in Google
calculator.
Indicate the calculator result displayed in the browser. Assign the result to a variable, such as
calculatorResult
. - Add a Verify Expression activity
to check if the retrieved result is correct.
In the Expression field, enter the following expression:
calculatorResult = "5"
.
- Add a Set Text activity and
indicate the Google search bar.
- Add a Use Application/Browser activity
to indicate the application that you want to automate. In this example, use
the activity to indicate a Google browser tab.
To learn how to work with test cases visit Test Cases, and Test Case Templates.