The Scheduling setup in Test Studio is a set of services, which allow 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 components and their specifics.
The Scheduling Service is the central part of the overall setup - it is in the middle of all operations and can be considered that it controls the process of running a test list on any remote machine. All machines, the Storage Service and the projects are all connected to the same Scheduling service.
- By default it uses port 8009, but it can be changed with any other free port in the Scheduling config wizard.
- Apart from the default set localhost, the Scheduling config wizard accepts IP address or machine name for accessing the computer, which hosts the Scheduling service.
The Storage Service, which keeps the project files and results, is the help tool for the Scheduling service. The Storage service maintains a database to store these files and the database provider, which Test Studio uses is MongoDb. The installation of the third party components is automatically triggered, when the Storage service is getting installed and if the install wizard detects there is no existing MongoDB installation.
- By default it uses port 8492, but it can be changed with any other free port in the Scheduling config wizard.
- Apart from the default set localhost, the Scheduling config wizard accepts IP address or machine name for accessing the computer, which hosts the Storage service.
- The Storage Service uses the default connection string to connect to MongoDB. If you reconfigure MongoDB, you need to apply the changes in the Scheduling config wizard as well.
- The Scheduler contacts the Storage Service for every scheduled job or results review. The Storage Service communicates internally to the database to provide the queried info.
The Executive Dashboard Service is the tool, which provides access to all results generated from scheduled test list runs for all team members - including these, who do not have Test Studio installed. This service keeps a localhost page, which visualizes the results stored in the storage database.
- By default it uses port 8085, but it can be changed with any other free port in the Scheduling config wizard.
- The Executive Dashboard service communicates with the configured Storage service. So, if you reconfigure the Storage Service, you need to change the details for the Executive Dashboard Service as well.
- The localhost page can be loaded from the Scheduling config wizard
The Execution Servers are all machines in the setup, which are connected to the Scheduling service and can execute tests. Depending on the configuration, these include the machine on which is hosted the standalone Test Studio installation (where the tests are designed) as well as the machine, which hosts the Test Studio Services.
To configure a machine as an Execution Server, you need to connect its Execution client to the Scheduling service.