Test Studio Execution Server can be any machine with installed Test Studio (Run-time edition is the minimum required). Configure the machine's Execution client to point to a running Scheduling service and it is registered as an Execution server for this Scheduler.
The below article describes the configuration steps.
- Start the Execution Client
- Configure Test Studio Execution Client
- Browser Support Update
- User Session Configuration
The Test Studio Execution Client is the Run-time component of Test Studio. It gets installed with Test Studio Standalone and Run-time editions. To start the Execution Client, called also Test Runner, type in the Windows Start Menu > Start Execution Server.
The Execution client is running in the background, so if this is already started (automatically on machine startup or automatically with a test project), you might get prompted that The Test Runner is already running. In this case you can access it from the Windows Task Bar on the lower right corner - locate the Test Studio icon, right click on it and choose the Show option.
Once the Test Studio Test Runner window appears, there are multiple options you can customize as per the specifics of the particular environment.
- Execution Server Configuration
- Machine Information
- Logging Information
- Run on Startup
- Browsers Information
Status - shows the current status of the Execution Server and if it can connect to the listed Scheduling server.
Scheduling URL - shows the URL of the current Scheduling server to which the Execution server is connected. Use the three dots button next to the Scheduler name to change the address of Scheduling server to use.
Type in the Scheduling Service URI text field the Scheduling service machine with the correct port on which it's configured. Hit the Change button to connect to the listed Scheduling Server.
Temp Folder - executing tests on a remote machine includes deployment of the project files in a temporary folder on the remote machine. You can choose where this temp folder will be located on the disc - click the three dots button next to the listed folder and browse to the desired one. The Reset button will set the default temporary location on the execution machine.
You need to allow access to the newly set location for all users.
Key - the communication key is required to establish the connection and to enable the communication to the Scheduling server machine. A key is generated in the Scheduling Config wizard and if it's not matching on both the Scheduler and Execution machines, the connection between these is not possible.
The section contains details for the Execution Server machine - status, Test Studio version, machine name, OS version, machine stats.
You can access the logging of the Execution Server - enable, disable or view the generated log.
The Run on start up option allows you to decide whether the Test Runner should be started automatically on machine startup.
All available and supported browsers on the Execution Server are listed in this section. You can calibrate these or restore their default settings. If using the legacy version of Edge, you can browse here the WebDriver folder location on disc.
This section appears only if there is an update for latest browser versions and allows you to update these with a single button click.
Test Studio allows you to apply different configurations for the user session on the execution machines. That way you can make sure the machine is available and ready to execute UI tests.
With this option enabled and as long as the Test Studio Scheduling Client process is running, it prevents the machine from falling to sleep, locking or showing screen saver.
This functionality does not prevent the user to manually lock the machine or put it to sleep.
Using this functionality could be a security risk since it will prevent the machine from locking when expected by your security policy. Consider if leaving the test machine unlocked for prolonged periods is acceptable for your organization before using the feature (especially when using Test Studio on your local physical machine).
Once the option is disabled or the Test Studio Scheduling Client process is stopped, the operating system is able to get to sleep/lock normally.
When running tests on a remote virtual or physical machine, users would usually connect to that machine via Remote Desktop Connection (RDC) to start and configure the Test Studio Scheduling Client. If after that the user closes their RDC window, their user session on the virtual machine is switched to 'disconnected' state and lose access to the graphical user interface (GUI). This prevents UI tests to be executed normally, whenever an interaction to the GUI is needed (e.g. performing real mouse click or keyboard actions, dialog interaction, etc.).
When the 'Reconnect to Console on Disconnect' feature is enabled, Test Studio tries to reconnect your disconnected session to the local console session, regaining access to the GUI.
In the case when there is a physical monitor attached to the Execution machine, the reconnected console session gets displayed on it.
That means if there is another user who has physical access to the machine, they will be able to view the screen or interact with it. Therefore consider carefully if that is acceptable for your organization before using the feature.
If you keep the Remote Desktop Connection session open but minimized, the local console session isn't reconnected.
If you need to run tests in minimized RDP window you can try modifying the Terminal Server Client registry keys as suggested.
When the 'Reconnect to Console on Disconnect' feature is enabled, you have the option to change the Console session resolution - you can choose the desired resolution from the dropdown menu. This option is useful when tests are executed on remote machine and successful test run depends on particular screen resolution. When set through the Test Studio Runner, you can ensure the automated tests are executed on the specified resolution.