Installation

Prerequisites

Note: This installation of Test Manager is for a Standalone Orchestrator deployment to add the given feature.

• Check and before installation.
• Check Compatibility matrix to make sure your install the right version of Orchestrator.

• Install Test Automation feature in Orchestrator. You can enable this feature by modifying an existing Orchestrator Single Node Installation and choosing Test Automation during setup.

  
  

  

  
  
• Provide the SQL user that you provide in the Authentication Mode field from the Database Settings installation tab, with the necessary rights to create databases. During the installation of Test Manager, a new and dedicated database is created.
  Note: When you enable the Test Automation feature in the Orchestrator, it creates a dedicated database with the default name UiPathTestAutomation. This database differs from the one created during the Test Manager installation.
  • Regardless of the type of user (domain or SQL) you want to connect to SQL Server, please note that you need to assign it the dbcreator Server Role BEFORE installing Test Manager, as the database is created during this installation process.
  • If security restrictions do not allow the use of the dbcreator Server Role in the service account, create the empty database in SQL Server.

    The Windows installer connects to SQL Server to verify the existence of the database.

  • After creating the database, you need to provide the user which connects to the SQL database with the db_owner user mapping role, as in the following screenshot.
    
    

    

    
    
• Download the UiPath Test Manager installation kit.

• Configure the SQL Server instance that you want to use to install Test Manager, using the following requirements:

  • the name of the SQL Server machine;
  • the name of the instance, if it’s not the default instance;
  • the value of the TCP port, if it’s not the default port - 1433;
  • the SQL Server port is open in the firewall of the SQL Server machine;
  • the TCP Protocol in SQL Server Configuration Manager has to be enabled;
  • the SQL Server service needs to listen on a fixed port, not on a dynamically allocated one.