Connect a Project to the Scheduling Server
Once you've configured your Scheduling Server and you've successfully registered at least one Execution Server to it, you're ready to configure a test project for execution.
You can also review our Telerik TV episode on Connecting a Project to a Scheduling Server for a video walk-through of this process.
From Test Studio Standalone version, load a new test project that contains at least one test and test list. Now connect the project to the Scheduling Server. Keep in mind that the Scheduling Server doesn't have to be on the same machine as the instance of Test Studio you're using.
- Click Connect in the Scheduling ribbon on the Project tab.
- The Scheduling Server Settings dialog loads.
- Under Server Details, you can connect your project to a Scheduling Server. Keep in mind that a Scheduling Server comes with the Execution Servers attached to it. When you schedule test lists from this project, you select which test list runs on which Execution Server. Your local machine can also be configured as an Execution Server.
- Enter the Server name and port of the Scheduling Server. The service URL is automatically generated. Change the URL if you previously edited the default URL when configuring the SS.
- Click Test Connection. You should see a message that states Connection established. Click OK.
- Under Schedule Configurations, you can choose where the scheduling server will find the test.
- The default setting is Schedule runs from local version. This setting also specifies the Project source location (PSL). An Execution Server assigned to this project will access this location in order to use the required test lists. By default, this is set to the current location of your test project opened in Test Studio on the local machine. If you plan on using remote Execution Servers (i.e. not located on this particular machine), change it to a network share. A network share (UNC) looks like this:
Where MachineName is the host name of the machine and TestProject7 is a shared folder accessible from your network that contains the Test Studio Project.
Note: This path or any file name within the project cannot exceed 248 characters. Placing the shared folder as close to the root of the drive as possible. Paths exceeding 248 characters result in the following error in the Scheduling Log:
Cannot create work folder! Error message: The specified path, file name, or both are too long.
The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
Test Studio does not support the Long UNC format to exceed this length limitation. For example:
Note: If the PSL differs from the local project folder, the two will not automatically be kept in sync. This must be done manually. If you upgrade Test Studio, ensure you load the project from both locations so it is properly updated as well. The second option is to Get latest version of tests automatically from your TFS. When this option is selected, you may see a message stating, "It seems you don't have a TFS configured". If so, click Connect to TFS to configure TFS settings.
Once TFS is configured, a message displays the address of the TFS server to be used.
- Click Register. Once you've successfully connected your project to a Scheduling Server, you're ready to schedule test runs.
- It's important to ensure the shared location is accessible from the Execution Servers you plan to use for the test project. Ensure you share the PSL folder and give Everyone Read/Write permissions:
- Right click the PSL folder.
- Select Properties.
- Click the Sharing tab.
- Click Share.
- Type Everyone and click Add.
- Set the Permission Level to Read/Write.
- Click Share.