Create a Scheduling Server

Note: As of 2013 R1, an All-in-One installation can schedule local test runs without installing the scheduling service.

 

The scheduling server keeps track of what tests to run and sends this data to the execution servers. You can also review our Telerik TV episode on Creating a Scheduling Server for a video walk-through of this process.

 

Before proceeding, there are a few things to confirm regarding the computer you will be using as the Scheduling Server:

  • The software must be run from a Windows Administrator account.
  • User Account Control (UAC: Windows Vista and 7 only) must be turned off completely (set to Never notify).
  • The Scheduling Server requires a Test Studio Runtime installation or higher.

 

 

If you do not meet the above requirements, the software will not launch or will quit immediately. 

 

2013 R2:

  1. Click Start > All Programs > Telerik > Test Execution 20XX.X > Configure as Scheduling Server.

     

    Configure

     

  2. Enter the address of the Storage Service for the Scheduling Server to use and click Connect.
     
     Scheduling window

    After you connect to the Storage Service, the Configure Scheduling Server dialog will display the URL for the Scheduling Service, which you can use to register test execution servers. You may wish to copy this URL for your records.
     
      Scheduling server settings

    Optionally, you may configure an SMTP server that your Scheduling Service can use to send notification emails.
     
     Mail settings
     

 

 

2012 R2 and Earlier:

  1. Click Start > All Programs > Telerik > Test Execution 20XX.X > Configure as Scheduling Server.

     

     

    Note: If you start the Scheduling Server Software with the Execution client already open, you receive the following error:

     

     

    If you receive this message, close the Execution client by right clicking it in the system tray (the purple square icon) and selecting Exit. If you still receive the error, you may need to completely close Test Studio (Standalone version) and/or Visual Studio (VS plugin).

     

     

  2. You will see the following screen:

     

     

  3. If this is a local only test run (within your intranet), check the box for Integrated Security.
  4. Set Server to the SQL Server name. SQL Express is used in this example and the database to be created on the server is named Telerik_Scheduling.

     

     

    Note: If you are not using Integrated Security, enter your Username and Password for the SQL server.

  5. Click Create Database. You should see a message that states The database is created. Click OK.
  6. The Import and Export buttons are typically used when upgrading from a previous version of Test Studio. If your previous installation didn't use the default installation folder, manually import the previous configuration in order to continue using it.
  7. The next page contains the settings for Service URL, email server, and machine registration:
  8.  

    Note: For the Service URL, use the Fully Qualified Domain Name and not http://localhost.

     

     

  9. Click Register the Local Machine.
  10. Edit the results data output folder if desired. This is where a captured image and DOM Tree on failure are stored. (If there is no failure during execution, no data will be added to this folder.)
  11. Edit the test execution folder if desired. This should not match the Project Source Location set when you Connect a Project to the Scheduling Server.
  12. Click the Register button.
  13. You should see a message that states The machine has been registered successfully. Click OK.

     

     

  14. Click Configure Email (SMTP) Server. Fill in the SMTP Server Settings to allow Test Studio to send emails that contain the results of your test runs.

     

     

  15. Click Save and then OK.
  16. Click Done. This machine is now registered as the Scheduling Server.
  17. This machine is also automatically registered as an Execution Server. Because of this, the Telerik Test Studio Execution Server application opens. If you do not intend to use this machine as an Execution Server, you can close this application by right-clicking on the icon in the system tray and clicking Close. Proceed to the next section to register one or more different machines as Execution Servers.
  18. If you intend to use this machine as the Scheduling Server and an Execution Server, do not close this application. It is required to be open for your tests to execute. Click the X in the upper right of the window to minimize it to the system tray.
  19.  


    Version 2012.1.528 & older

    R1 2012 SP2 & newer