Test Automation

Overview

Test Automation in Orchestrator allows you to distribute and manage your tests. In this section, you can learn how to get started with test automation, execute, schedule and manage tests.

Note: To use the Test Automation feature in Orchestrator for large-scale testing, you require a Test Manager license.

Prerequisites

1. To create and execute test automation, you must have the Automation User, and the Robot role assigned.
2. Create a test case in Studio.
3. Publish the test case to Orchestrator.

Getting Started

To start executing your application and RPA tests, follow these steps:

Step	Action	Description
1	Create and publish test case	Create a test case in Studio and then publish it to Orchestrator. For more information, see Test Automation Prerequisites
2	Create test set	Add individual or group test cases to a test set.
3	Execute test	You can choose from the following options: Execute test case manually Set test schedule.

Navigation and Search

To quickly find your test items, use the search function and the filters. Navigate within the page using and configuring the paginator. You can filter the test items by the project and choose which column details you want to have on the page.

Uploading a test automation package to Orchestrator

You can upload a test automation package directly in the Orchestrator user interface. Navigate to the desired tenant in Orchestrator, and upload your test automation package there. For test automation packages, a corresponding process is automatically created. This process isn't necessarily created in the first folder of the tenant but in the last folder you accessed. The auto-creation of processes is a unique behavior associated with test automation packages.

If you log into Orchestrator and navigate to the third folder, any test automation package you upload at the tenant level will have a corresponding process created within that folder. Unless you access another folder in that tenant, this third folder becomes the folder which the Orchestrator UI defaults to for any process creation.

In contrast, when you publish a test automation package from Studio, the process is created in the folder where you are currently connected.