Test Studio Test Runner in CI Builds
The Test Studio Execution Client is the Run-time component of Test Studio. It gets installed with the Test Studio Standalone and the Run-time editions. Part of its options are also applicable when running UI tests from a CI build pipeline.
This article guides you through the configuration of the Test Studio Execution Client when used in CI environment.
- Start the Execution Client
- Set Test Runner app to run on machine startup
- Use the options to control the user session
- Access Test Studio application logging on the build machine
Start the Execution Client
To start the Execution Client, called also Test Studio Test Runner, type in the Windows Start Menu > Start Execution Server.
Message 'Test Runner is already running'
The Execution client is running in the background. Thus if the runner is already started (for example automatically on machine startup; or automatically with a test project; or under another user session) and you try starting it again you get prompted with a message 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.
Note
If the Test Runner is started under another user session you need to stop its process and start it again under the current user session.
Run on Startup
The Run on start up option allows you to decide whether the Test Runner should be started automatically on machine startup.
User Session Configuration
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.
Keep Machine Awake
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.
Note!
This functionality does not prevent the user to manually lock the machine or put it to sleep.
Note!
Using this functionality is a potential risk as it prevents the machine from locking when expected by your security policies. 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.
Reconnect to Console on Disconnect
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.
Note!
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.
Note!
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.
Change Console Resolution
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.
Use Test Studio Application Log
You can access the logging of the Execution Server - enable, disable or view the generated log.
Browsers Information
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.
Browser Support Update
This section appears only if there is an update for latest browser versions and allows you to update these with a single button click.
