orchestrator

2023.10

false

Getting started
- Introduction
- User options
- Logging in to Orchestrator
- Resetting your password
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Orchestrator Configuration Checklist
Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Folders
- Monitoring
- Access control
- Configuring automation capabilities
- Machines
- Packages
- Audit
- Credential Stores
  - Managing credential stores
  - Integrating credential stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Alerts
- Settings - Tenant Level
Resource Catalog Service
- About Resource Catalog Service
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Process Data Retention Policy
Triggers
- About triggers
  - Time triggers
  - Queue triggers
- Managing triggers
  - Creating a time trigger
  - Creating a queue trigger
- Managing Non-Working Days
- Using Cron Expressions
  - Triggering jobs on the last day of the month
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- Orchestrator Logs
Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
Queues
- About Queues and Transactions
- Bulk uploading Queue Items using a CSV file
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
  - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
- Moving Bucket Data Between Storage Providers
Test Suite - Orchestrator
- Test Automation
- Test Cases
  - Field Descriptions for the Test Cases Page
- Test Sets
  - Field Descriptions for the Test Sets Page
- Test Executions
  - Field Descriptions for the Test Executions Page
- Test Schedules
  - Field Descriptions for the Test Schedules Page
- Test Data Queues
- Testing Data Retention Policy
Other Configurations
- Increasing the Size Limit of Package Files
- Setting up Encryption Key Per Tenant
- GZIP Compression
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Configuring host authentication settings
- Managing your host license
  - Allocating Licenses to Tenants
- Configuring system email notifications
- Configuring other host settings
- Audit logs for the host portal
- Maintenance Mode
Organization administration
- About organizations
- Managing organization administrators
- Managing organization settings
- Configuring organization authentication
  - Setting up the Azure AD integration
  - Configuring the SAML integration
    - Setting up SAML SSO with Azure AD
- Configuring organization security
  - Session policy
  - Restricting access to a set of users
- About licensing
  - Activating your license
- Accounts and groups
  - Managing access
  - Managing accounts and groups
- Authorizing external applications
  - Managing external OAuth applications
  - Configuring fine-grained access for confidential apps
- Managing tags
- Overriding system email settings
  - Email setup
    - System emails are not sent - SslHandshakeException
- Audit logs
Troubleshooting
- About Troubleshooting
- Frequently Encountered Orchestrator Errors
- Browser group policies
- Cron Expressions

Orchestrator User Guide

DELIVERY:

DELIVERY:

Automation Cloud Automation Cloud Public Sector Automation Suite Standalone

Last updated Nov 11, 2024

Test Cases

Overview

In this topic, you can learn how to manage your test cases across all the projects and application versions. The test cases are part of test sets that are up for execution. For more information, see Test Sets.

Conditions

The test cases are created automatically when you publish a test package through Studio. For more information, see Application Testing.
If an existing package is revised followed by an updated version being published, the test cases for the new version are automatically created. The new test cases show up alongside existing ones for the previous version. However, if the changes to the package only apply to the patch version, then the existing test cases are updated to reflect these changes, instead of creating new ones.
When you publish a new test case version, the correspondent package is automatically updated to the latest version.
If an existing project is cloned to represent a new application version (e.g. from v1.1.1 to v.1.2.0), you must manually publish this package and create a new process.
Important:
- For the robot to run test automation jobs, make sure de default role Automation User exists and it is up to date.
- You must first deploy a process from the published test case package before you can create and execute a test set.

Create Test Set

You can group together multiple test cases into a test set.

Log in to Orchestrator.
Open your folder.
Navigate to Testing > Test Cases.
Use the checkboxes to select individual test cases. Alternatively, you can choose Select all in the column header. You can modify the test case selection later in the test set configuration step.
Click Add test set.
Enter a Name and an optional Description for your test set and then click Create to continue.
Configure the execution target. You can select the user that is assigned to that specific folder. The default is set to Any User.
Select your Studio projects.
(Optional) You can edit the project version and toggle to Include Prerelease versions.
Define custom Arguments for your test cases to override default values at the test set level.

Through the arguments, you can parameterize the test cases at runtime.

Note: To define arguments, you need to have published a package with arguments.
Click Next to continue.
Modify test case selection if needed.
Click Save. Your test set is created and available on the Test Sets page.
Tip:

Execute Test Case

You can execute individual test cases on the Test Cases page.

Log in to Orchestrator.
Open your folder.
Navigate to Testing > Test Cases.
Select a test case and click Execute.
Configure the execution target:
- User: Select the user from the dropdown list that is assigned to that specific folder. The default is set to Any User.
- Machine: Select the machine resource from the dropdown list.
Click Execute to confirm.

Delete Test Case

Open your folder in Orchestrator.
Navigate to Testing > Test Cases.
Select a test case and click Delete.
Click Ok to confirm.

On this page

Overview
Conditions
Create Test Set
Execute Test Case
Delete Test Case

Was this page helpful?

PREVIOUSTest Automation

NEXTField Descriptions for the Test Cases Page

Support and Services

Get The Help You Need

Learning RPA - Automation Courses

UiPath Community Forum

Trust and Security

© 2005-2024 UiPath. All rights reserved.