Creating automated tests

Create, publish, and link automated tests in Studio before running them as part of performance scenarios in Test Manager.

Before running performance scenarios, you must create, publish, link and assign your tests.

Prerequisites

• You can create performance scenarios only for test cases built using the latest supported packages (Testing.Activities v.25.10.2 or higher, UIAutomation.Activities v.25.10.2 or higher, WebAPI.Activities v.2.1.0 or higher). Older versions may work locally or in test sets but fail when executed at scale.
• Use Windows projects when you execute test cases on-premises, using App Testing robots (unattended robots).
• Use Cross-platform projects when you execute test cases using serverless robots. You cannot run desktop automations, such as for SAP WinGui, on Cross-platform projects.
• To run browser tests in Incognito or InPrivate mode, meet the requirements for Incognito and InPrivate mode.

Steps

1. Create tests in Studio. Configure the tests.

   • Design your automated tests as you would for any functional test case.
   Note:

   Whichever project type you use, Workflow Analyzer runs automatically as part of every dry run and checks each test case for two things: whether the package versions above are met, and whether the automation uses any activities that aren't eligible for performance testing. If a check fails, Workflow Analyzer reports what's wrong so you can fix it before spending robot minutes on a run that can't succeed.

   Unsupported activities include:

   • Computer vision activities
   • Image-based/OCR activities
   • Hardware Events input mode
   • Local file system access
   • Desktop-only interaction patterns, such as global hotkeys and window management

   

   For examples on creating various automated tests in Studio, see the following tutorials:

   • Apply for a loan with UiBank
   • Using mobile automation for mobile banking application
   Tip:

   Run your automated tests locally in Studio to validate behavior before deploying it for performance testing, as tests must be data-stable and reliable before scaling.

2. Publish your project containing the automated tests to Orchestrator. The project is published to Orchestrator under the form of a NUPKG package. For steps on publishing Studio project to Orchestrator, refer to About publishing automation projects.

3. Link tests to Test Manager.

   1. Go to Test Manager, in the same tenant where you published the project to Orchestrator.
   2. Create a test case. Refer to Create test cases for detailed steps.
   3. Open the previously created test case, and select Select automation to link the previously published NUPKG package, containing the Studio automated tests. Refer to Selecting automation for detailed steps on selecting an automation for a test case.

4. Assign tests to test sets in Test Manager. Refer to Adding test cases to a test set for detailed steps.

5. Run the test case in a test set in Test Manager to confirm successful execution. Refer to Executing automated tests for detailed steps.

Result

The automated test cases are created, published to Orchestrator, linked to Test Manager, and assigned to test sets. The tests are ready to be executed as part of performance scenarios.

Review Workflow Analyzer findings

Workflow Analyzer runs during every dry run. If a test case uses a package version or an activity that isn't eligible for performance testing, the dry run reports a finding. To resolve the findings:

1. Run a dry run of the performance scenario. For steps, refer to Executing performance scenarios.
2. Expand the Application logs panel.
3. Identify the test case and the activity referenced by each Workflow Analyzer finding.
4. In Studio, fix the issue:
   • If the activity is not eligible for performance testing, replace it with a supported one.
   • If the package version is not eligible, update it to a supported version.
5. Publish the project to Orchestrator again.
6. Rerun the dry run.

Workflow Analyzer no longer reports the findings in the Application logs panel.

For the rules that Workflow Analyzer applies to performance tests, refer to Performance test rules in Workflow Analyzer.

Requirements for Incognito and InPrivate mode

Performance testing supports browser automations that run in Chrome Incognito or Edge InPrivate mode. For the test to run in this mode, the project must meet all of the following requirements:

• The project uses UiPath.UIAutomation.Activities version 26.10.0 or later. This minimum is higher than the package versions listed earlier on this page.
• Incognito/private window is set to Yes on a modern browser activity, such as Use Application/Browser. Classic activities, such as Open Browser and Browser Scope, are not supported in performance testing.
• The browser is Chrome or Edge.
• Browser automation mode is set explicitly to Chromium Automation or Chromium Automation Headless. The default value, Browser extension, does not meet the requirement. For details about these modes, refer to Browser automation mode and the Chromium Automation section of the UI Automation Activities 26.10 release notes.

If a test doesn't meet these requirements, the dry run reports an error. For the error message and how to fix it, refer to Troubleshooting performance testing.