The Scheduling setup in Test Studio is a set of services, which allows the communication between the Test Studio components on the different machines. Depending on their role in the configuration, the machines can run different editions of the product, and can be set up in various combinations.
This article will guide you through the options of possible configurations.
Test Studio installation must be configured from a Windows Administrator account.
The Test Studio Scheduling components are the Test Studio services and these need to be installed and configured on one of the machines, which will be used in the setup as a Scheduling and Storage server. Depending on the decision which machine will host which component, you can:
- Add the Test Studio Services by changing the default standalone installation. (The services are not included by default in the Test Studio standalone installation).
- Install the default Test Studio Run-time edition. (The services are included in the default Run-time installation. If necessary, the installation can be modified to not include these.)
An Execution Server can be any physical or virtual machine with minimum installation of the Test Studio Run-time edition. Multiple Execution Servers can be connected to a single Scheduling Server to allow you execute multiple test lists simultaneously. Differences in operating systems and browsers between the machines running on the Scheduler and the Execution servers are allowed.
Each Execution Server must be running the same version of Test Studio as the Scheduling Server.
To register an Execution Server to the Scheduling service, you need to configure its Execution client to point to the running Scheduling service in the setup. The Execution client is part of each Test Studio installation - the Standalone, or Run-time.
Few things to consider when choosing an Execution Server machine:
- Ensure that the Execution Server machine has sufficient disk space to store a copy of the project you schedule test lists from.
- An active and unlocked user session is required to execute UI tests successfully. There are possible configurations and workarounds to help in setting up the Execution machines to keep the active session.
- An exception from the last requirement is executing tests in Chrome headless mode - it only requires a logged user on the Execution machine.
- If you plan to use 'Get Latest from TFS' on scheduled test runs, make sure the Test Studio Execution Server is running under an account with access to log on to the TFS repository.