New to Telerik Test Studio? Download free 30-day trial

Scheduling Configuration in Test Studio

The Test Studio Scheduling setup allows you to configure a set of machines, connected together to execute the automated tests unattended. The results generated from the scheduled test runs are stored in a way to allow anyone in the team to review these.

From your local instance of Test Studio test lists can be scheduled on any configured machine in the network, including virtual machines. The test list runs can be fully configured - when to be executed, on which machines, in case there are multiple available, whether to generate an automatic email report, etc. If you have to run a number of tests, you can spread the workload between different machines in order to reduce the total execution time. All the results will be stored in one centralized location for you to examine later.

Which Are the Scheduling Setup Components?

Test Studio Scheduling setup consists of few services on top of the default product installation, which needs to be configured properly to allow the communication between them.

The Test Studio services, which needs to be added are as follows:

  • Scheduling Service
  • Storage Service
  • Executive Dashboard Service

Tip

The Test Studio Services are not included in the default Test Studio installation, but can be added in the installation later at any time. The Test Studio Run-time installation includes the Services in its default state.

How Many Machines Do I Need?

The Scheduling configuration can be enabled on a single machine, as well as it supports multiple execution machines.

Note

Each machine, which will act as an Execution server, requires minimum Test Studio Run-time installation.

The Scheduling configuration can be completely enabled on a single machine with the Test Studio Ultimate or Test Studio Web&Desktop installation (modified to include the services).

If there are multiple machines dedicated for test execution, you need:

  • at least one machine with the Test Studio Ultimate or Test Studio Web&Desktop installation (can use the default installation) - it will be used to create the tests for the automated testing project;
  • one machine, which hosts the Test Studio services - this can be any of the machines in the setup, so it can use either full product installation, or Run-time edition instance;
  • and at least one machine to execute test lists - this one needs minimum the Run-time installation.

Scheduling Scheme

How to Configure the Scheduling Setup?

There are few steps to follow in order to setup the Scheduling configuration:

  1. Choose a machine, which will host the Test Studio Services

    In Test Studio we call this machine the Scheduling server - it can be any of the available machines as long as it is accessible for all other machines. It can be considered the centralized component, which communicates with all other parts of the configuration.

  2. Add/Install the Test Studio Services

    Depending on which machine in the setup you have decided to host the Services - either modify the installation of the Standalone Test Studio, or install the default Run-time product.

  3. Configure the Services

    The Scheduling config wizard allows you to setup each of the Services.

  4. Connect the Execution Machines to the Scheduler

    The Execution machines are also called Execution Servers in Test Studio - these are all machines, which are dedicated to execute the tests. The minimum installation for these is the Run-time edition of Test Studio - you can even disable the Test Studio services from the installed components, if there is already a machine, which hosts these.

  5. Configure Any Project for Remote Execution

    Once the machines and components are set up, you need to connect a project to the Scheduler - that way the scheduled test list runs will go through the configured Services.

Once these prerequisites are complete - even if each of these is hosted on a single machine, the scheduled test list executions will use the Test Studio Services with all their benefits - recurring runs, test distribution on selected machines, automatic email notification, results in the Executive Dashboard, etc.

In this article
Not finding the help you need? Improve this article