Last Updated: 16 Jun 2021 09:59 by ADMIN

Make it possible to choose whether or not to group the results from all iterations and provide average time, when exporting the results. 

I have 20 iterations of the same steps and it will be helpful to see the average time for each step.

Pending Review
Last Updated: 09 Jun 2021 15:41 by Mark

Currently the exported result contains extended details only for the failed steps. If there is a warning for a step - like the warning that the element was found only by image, this can be only seen in the Test Studio result file. 

Extending the HTML exported result to show the step warning details will be very useful for anyone who review this type of result (attached in an email after a scheduled run, for example). 

Pending Review
Last Updated: 07 Jun 2021 15:57 by Aditya
Update the predefined device config settings with the latest available common iOS and Android devices. Check if the User-Agent request header needs to be updated as well, or more options to be provided. 
Pending Review
Last Updated: 07 Jun 2021 06:46 by ADMIN

We have a large PDF (60+ pages) and try to verify certain content on specific pages. During the recording process some elements are captured with TagName and TextContent and others with TagIndex. In this scenario TagIndex is not reliably, because the document is large and the elements change dynamicaly.

One solution is to update the element's find logic manually on all elements that use TagIndex, but this is very time consuming. 

Another option is to use coded step to find the target element by TextContent and verify it.

Pending Review
Last Updated: 07 Jun 2021 06:45 by ADMIN

When the Scheduling server is not added during installation, the Configure button in Test Studio will be greyed out (disabled). It will be helpful to add some kind of tool tip or note about this.

The solution is to modify the existing installation of Test Studio and add the Scheduling Server feature to the installation.

Pending Review
Last Updated: 07 Jun 2021 06:45 by ADMIN
Created by: Kristina
Comments: 0
Type: Feature Request

Allow users to add custom arguments when executing tests against any of the supported browsers.

This includes the Chrome Headless execution, which always defaults to en-EN language argument for example and you can't change it.

Last Updated: 07 Jun 2021 06:44 by ADMIN



We are unable to use TestStudio for WPF, when closing the window during recording we get an excpetion.

I tried and created simple wpf app in VS 2019 and get same results.

I attached a C# project as solution was to big.



Simple app is based on VS 2019 telerik for WPF project, created as blank.

Only code changed is adding a DispatcherUnhandledException on App class.


private void OnDispatcherUnhandledException(object sender, DispatcherUnhandledExceptionEventArgs e)
            if (e.Handled || e.Exception == null)
            e.Handled = true;



1) Create new project

2) Create new test for WPF 

3) Configure to the WPF app exe file

4) Click record

5) After test studio is connected close the window.


Expected results:

Window get closed without any problems.


Actual results:

While closing the window exception is being thrown that we.


Pending Review
Last Updated: 04 Jun 2021 11:09 by Mark

When generating videos for the test runs from a test list, the output video files uses the name of the test only. There is no indication which is the test list from which this test was executed and when having multiple runs and videos it is difficult to relate these with the generated results. 

It will be useful to generate the names of the videos from a test list in a way to correspond to the test list name and particular run. 

Last Updated: 17 May 2021 11:45 by ADMIN

Add the option to start quick execution of tests in Headless mode from Visual Studio.

Currently it is available from the Select Execution Browser window, but if you have selected a preferred browser this window is skipped.

Last Updated: 17 May 2021 11:43 by ADMIN

Navigate to the application under test and click a link that opens in a new tab. Then, click within the new tab to redirect it to a new URL and close the tab. 

The result is that the Close pop-up window step is successful, but the tab is not closed. This results in issues with the following steps in the test scenario.

Under Review
Last Updated: 29 Apr 2021 15:07 by ADMIN

Nested data driven tests generates quite large results, even when there is no data in the bound data table (built-in or external). The result is almost twice the size of the same tests, if these are not using the data tables. The tests may be using InheritParentDataSource, but the behavior is similar if these are not using it as well. 

For real user scenarios, the large results may exceed the limitation of the file size (16MB), which can be transferred through the storage service. 

Investigate if it is possible to optimize the data driven test results, at least for the case, when the data source is empty.

Pending Review
Last Updated: 28 Apr 2021 06:34 by ADMIN
Created by: Alexandru
Comments: 0
Type: Feature Request

We need to be able to verify the text in dialogs in different browsers.

The current solution is in code, but is not stable due to browser structure changes -> https://docs.telerik.com/teststudio/advanced-topics/coded-samples/html/verify-dialog-text-chrome


Last Updated: 26 Apr 2021 08:37 by ADMIN

The TextFromImage verification step extracts the wrong text in some scenarios.

One example is that the number "8" can be recognized as "3", when it is at the beginning of the element (text). Other times, the word "learn" is not extracted correctly from a sentence. 


Last Updated: 25 Apr 2021 20:05 by ADMIN

When you edit the "Wait for ExistsNot" step as coded step, the generated code does not reference the target element from the Pages. Instead, it creates a fixed find logic from the current state of the element in the Elements Explorer.

The issue is that when the find expression for that target element changes, the coded step fill not be updated.

Last Updated: 22 Apr 2021 13:20 by ADMIN
I'm following the ArtOfTest.Runner.exe doc in User's Guide syntax and getting an error I can't understand.  Screenshots
in attached file below.

If you need additional information let me know.

Pending Review
Last Updated: 22 Apr 2021 07:55 by Mark

It will be helpful to have an element, which is defined based on another element. This is similar to chained find expression, but instead of defining the parent element with its find expression, add the ability to reference an already recorded element in the project as a parent one. Then add find expression for the child element.

Last Updated: 21 Apr 2021 07:55 by ADMIN

Currently we have an Angular select control and we are experiencing troubles with the automation. The value is visibly selected but it is not used further in the application. It appears that the "OnInput" event is not triggered during the selection.

We have found a workaround, which is to trigger that event in a coded step:

// This is necessary to trigger event listener
Last Updated: 19 Apr 2021 14:14 by ADMIN

Not able to install Telerik Test Studio


=== Verbose logging started: 4/16/2021  10:47:39  Build type: SHIP UNICODE 5.00.10011.00  Calling process: Local\Temp\7zSCA0634CB\ProgressWebInstaller.exe === MSI (c) (94:58)

Need More Info
Last Updated: 16 Apr 2021 10:46 by ADMIN
DisplayLabels can contain text, but because it is not a supported FrameworkElement, it is difficult to work with in code. Tests instead have to store a path to the element and use the full name - like Applications.MyApp.MyWindow.DisplayLabel1 - every time I want to refer to it. It leads to a lot of repetitious code as well as storing of unnecessary elements, especially where a Find.AllByType would otherwise be able to take advantage of the consistent structure.
Last Updated: 12 Apr 2021 07:00 by ADMIN

When you add a "Wait for Exists" step from the Step Builder, against existing element in the Elements Explore, it will keep the image that was captured during the recording of that element.

That image is used as a backup logic to try and find the target element for the "Wait for Exists" step, but it should not be used. 

The workaround is to delete the image in the target element only for the "Wait for Exists" step.

1 2 3 4 5 6