- 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
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScaleCoordinates Migration Tool
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- StudioPro
- Introduction
- Application Testing
- RPA Testing
- API Test Automation
- Mock Testing
- Extensions
- Troubleshooting
Application Testing
Studio Pro supports the creation of specialized test cases for conducting automated application testing, either in VB or C#. Individual test automation projects can be created in StudioPro, used for verifying data, and included in CI/CD pipeline scenarios.
Application testing can be performed with Test Cases and Data Driven Test Cases, sequences that make use of verification activities part of the UiPath.Testing.Activities pack, together with activities from other packages.
Data Driven Test Cases use data imported as arguments into the project to verify test case execution. The entire data or only certain values may be used at execution.
.xaml
files are invoked.
With Studio Pro, workflows can be converted into test cases or imported as test cases from other projects. Later, application testing projects may be published to Orchestrator, managed and executed from the Test Cases page.
Use the Test Automation project type from Backstage view > Start to start designing a test case.
.xaml
files can be added to a project by using the New > Test Case ribbon option.
The default activities packages for this type of project are: UiPath.System.Activities, UiPath.UIAutomation.Activities, and verification activities from the UiPath.Testing.Activities.
Verification activities such as Verify Control Attribute, Verify Expression, and Verify Expression with Operator are used for testing the data used by your workflows.
Such activities behave differently when executed or debugged. If a verification activity encounters an error, the execution does not stop to throw the error, but rather logs the failed activity in the Output panel. If the activity was executed successfully, it is marked in the panel.
Application testing can require working with large data sets to verify the workflow execution and cover corner cases. Rather than creating multiple test cases for each data set, import and use your data sets inside the project with the Data-Driven Test Case file type.
In the Project panel, right-click a test case and select Add Test Data.
Go to Variation File to choose an Excel file to import, and then select a worksheet.
InArgument
types together with values from the file.
As a next step, you can use the Verify Expression with Operator activity to compare values with those from the imported Excel file, using available operators. Read more about this activity here.
Executing or debugging a Data Driven Test Case can be done in two ways, either by using all the imported data or discretionary by selecting the specific data to use.
Click the Run file with data variations or Debug file with data variations options from the ribbon. The Data variations window opens:
Select the data you would like to use for running or debugging the test case by clicking the checkbox next to each row. Click Run or Debug after the selection is made.
If the test case project uses the Verify Expression with Operator activity, the execution is performed once for each selected data set.
If changes were made to the Excel data set, remove and add the data set again in the test case project.
Existing workflows used for testing purposes can be converted to and from test cases using Studio Pro. In addition, you can create an RPA Testing project from existing processes.
To convert workflows into test cases right-click the files in the Project panel and select Convert to Test Case:
Similarly to importing data collections into API Test Automation libraries, you can import such collections into your Application Testing processes using the New Service wizard.
Please take into consideration that this is available only for libraries and Test Automation projects created with a Studio Pro license.
.xaml
files need to be set as publishable from the Project panel.
Multi-select is available, simply hold the Ctrl key while selecting each file individually, then right-click > Set as Publishable.
.nupkg
file.
Publishing test cases is performed in a similar way as for other types of projects. Use the Publish option from the Studio Pro ribbon. You can set a version of the project and use the Certificate Signing options, read more about publishing projects here.
Test cases can be published to Orchestrator, Robot defaults, or a custom path. If you wish to publish to Orchestrator, make sure your Robot or UiPath Assistant is connected to Orchestrator, follow the steps here.