Transitioning NonProduction Robot licenses to Testing Robot licenses

Testing Robots provide several advantages over NonProductions Robots, as outlined in the NonProduction and Testing Robots compared table. This section walks you through the process of moving from NonProduction to Testing, so that you can fully benefit from these advantages.

Transition in a nutshell

Orchestrator modification

Important:

This only applies to standalone Orchestrator.

If you use the Test Automation module in an Orchestrator instance installed as an Azure App Service, read through the following information:

• The Azure App Service installation page for general information

• The -testAutomationFeatureEnabled parameter description on the Publish to Orchestrator script page for details on enabling the Test Automation module

1. Run the Orchestrator installer and click Change.
   
2. Click Test Automation, and select Will be installed on local hard drive.
   
3. Fill in the SQL server authentication information:
   • the SQL server host
   • the database name
   • the authentication mode
   • the username and password
   

Robot license conversion

1. Renew or update your license.
   Note: This step only applies to standalone Orchestrator.
2. In the administration section, deallocate NonProduction licenses from your tenant. This is done from the Edit license allocation window corresponding to the desired tenant.
3. In the administration section, allocate Testing licenses to your tenant from the same Edit license allocation window. See details for cloud and on-premises environments.
4. In Orchestrator, make the switch between NonProduction and Testing in all relevant places:
   • Tenant > Machines > Edit Machine - deallocate all NonProduction runtimes from existing machines, and allocate Testing runtimes instead.
   • Folder > Automations > Triggers - edit existing triggers to change all NonProduction runtime types to Testing.
   • Folder > Automations > Jobs - edit existing jobs to change all NonProduction runtime types to Testing.
   This is what you can expect the runtimes section of the machine page to look like after following the previous steps:

   

New product installation

Install Test Manager.

Note: This step is recommended, but not mandatory for Test Robots to work properly.

NonProduction and Testing Robots compared

NonProduction Robots	Testing Robots
Used for running unattended automations for development purposes only.	Used for running unattended automations for development and testing purposes, which include workflows, activities, and applications.
Run the same automations as a Production Robot, including test cases.	Run test cases with robust verification and testing options, which can be reused across projects.
Reporting must be manually configured.	Allow for granular reporting of test case results to third party tools.
Allow full workflow testing only (black box).	Allow activity-level unit testing (white box).
Allow for single points of verification.	Allow for multiple points of verification.
Opening Studio with Unattended Robot or NonProduction Robot license is primarily used for troubleshooting, with editing allowed. You can also use it to debug projects from the development machine, with Remote debugging.	Opening Studio with Attended Robot or Testing Robot license is permitted for debugging without any editing capabilities.

Testing Robots and Orchestrator compatibility

The functionality of Testing Robots is largely dependent on the standalone Orchestrator version, as outlined in this table.

Testing Robot/Orchestrator version compatibility	Orchestrator 2019.10.x	Orchestrator 2020.4.x and 2021.4.x	Orchestrator 2021.10.x	Orchestrator 2022.4.x and newer
Testing Robots can execute processes.	No	No	Yes	Yes
Testing Robots can perform white box and black box testing.	No	Yes	Yes	Yes
Testing Robots can execute test automations.	No	Yes	Yes	Yes
Testing Robots support Orchestrator queue triggers.	No	No	Yes	Yes
Testing Robots can execute process automations from UiPath® Apps.	No	No	No	Yes