New to Telerik Test Studio? Download free 30-day trial

Desktop Tests in Test Studio

Test Studio recording feature supports various desktop applications. To initiate recording session against specific application, you need to define which in the desktop test.

This article guides you through the desktop test configuration process.


Check this video tutorial for recording an end-to-end Desktop test scenario.

Configure Desktop Test to Record Specific Application

The configuration of the desktop test requires a desktop app to be specified and, thus, used for recording and execution. Open a Desktop test in Test Studio and find the Configure button in the Test tools ribbon. Click the Configure button to open the Desktop App Config Wizard.

Configure button


If you try to initiate a recording session in a desktop test, before this is configured, the Desktop Config Wizard pops up and lets you choose the application to automate.

Choose the Desktop Application to Automate

Test Studio provides few options to define the application to automate - you can specify an executable file for this test, use a default path to the executable file set on project level, or specify an Application User Model ID.

Config Desktop app wizard

Configure Application Path in Desktop Test

Choose the Browse button to open File Explorer and browse to the folder where the executable file is and select it.

Specify path to Desktop app

The Desktop Application Path field also allows you to use environment tokens (such as %Program Files%\MyApp\App.exe). In any case the Full Path field displays the full path to the executable file.

Full application path

Use Default Desktop Application Path

The automation process requires multiple tests to be created for a single application. In such case configuring each created test will be a tedious task. Thus Test Studio allows you to set a default desktop app path on project level and use this for all desktop tests. The option is available in Project Settings -> General and once a Default Desktop App is configured each new Desktop test in the project is created directly configured to use it.

Use default path

Configure Application User Model ID

Modern desktop applications are not always started with an executable file. Example of such apps are all applications from the Windows store, UWP or Maui-based apps. To enable this type of automation Test Studio Desktop tests support configuring a test using the Application User Model ID.

Configure Application user model ID


Not sure what is the Applications ID for the tested app? Follow few simple steps to find the User Model Id and use it in the Test Studio desktop test configuration.

Finish Desktop Test Configuration

Once you choose the path to the desktop application executable file, you can confirm the configuration by pressing the OK button. Then, use the Record button to launch the specified app in Test Studio recording mode.


In any case, when you need to change the applied settings, hit the Configure button to access the wizard again.

See Also:

In this article