Telerik does not support test studio assemblies in .net standard and does not have a test runner in .net core. Considering all of our Azure DevOps and container agents are running linux we will not be able to use the tool.

Please add this feature to your product.

Add functionality to delete all steps that do not match your filter. 

After I filter out the unnecessary domains, I delete the individual steps.  The primary reason that I perform this manual deletion is to detect extra Think Time steps which may linger after the filtering.

Add functionality to change all Think Times to the same value for the entire User Profile. 

This would save having to go into each Think Time step and making a manual modification.  This would save time and help ensure no stray values of Think Times (say 200 instead of 20) were entered.

Add a toggle functionality for custom dynamic targets in order to enable/disable each on or all of them.

In the current state, you have to delete your custom dynamic target in order to disable it from your User Profile. That way you lose the information there and if you need it again, you must create it from scratch.

Copy a User Profile with its current state of custom dynamic targets.

The existing workaround is to copy the whole load test, but that makes the project unnecessarily large and does not cover all scenarios. It would be helpful to be able to copy existing User Profile in its current state.

Group custom dynamic targets with the same source step and value.

That way you can make changes to a group of dynamic targets at once. In this regard, maybe it will be helpful to allow multiple destination steps for one custom dynamic target.

Currently the popup window for editing user profile, choosing dynamic target and adding new dynamic target are all opened on top of each other. This prevents the user from going back to the previous windows to view steps and request details.

It would be great improvement in usability to be able to switch back to the different windows while designing your load test.

Show MongoDB service's status in the Configure Test Studio Services window in MongoDB tab. If it is running, it should indicate it in a similar way as the Storage and Scheduling services.

Currently, only when you apply the service settings, it is started and that is shown in the status bar. If I close the Configure Test Studio Services window and open it again, that information is missing again.

When you execute a test list in CI environment with the ArtOfTest.Runner.exe, there is no option to publish the results to the storage server (if you have setup a storage server).

It will be great to have this option, so we can view the results in the Executive Dashboard.

It would be nice to have the story board capture subtest screenshots instead of the "Test Step" placeholder.  It would be fine maybe to watermark the screenshots with "Test Step," but still show the screens for reference.

The Image verification and OCR steps do not work for WPF tests.

Those steps are simply not added to the test with the latest release 2020.R2.

Telerik Test Studio has the options to Add a, Bind (to an existing), or Unbind from a data source.

However, the VS Test Studio plug-in only has Add and Unbind.

It would be nice to be able to do everything within Visual Studio.

With Find Logic for an element, sometimes the Find Logic uses Text Content on initial element recording and other times the Find Logic uses ID. 

I request for functionality in Test Studio to prioritize what logic is actually used in the Find Logic.  Generally speaking on the applications I have used Test Studio to automate testing, there are elements that has specific text content on a page.  These elements start out with their Find Logic to have TextContent since I think that is the most unique identifier about them.  But as TextContent is concerned, there is a possibility of change of text on that element.  So I would target the element with the ID of the element or the ID of a parent element and then use tagindex to be specific.

After initial recording, I put in the extra time to modify the Find Logic to fit my need.  

If an element does not have an Id, but the element has a direct parent (only 1 level above) element with an ID, use that parent element and then the additional find logic for specific element over using TextContent. 

Having this functionality of Find Logic prioritization will hopefully provide a general consistency to improve my user experience.  

When entering a value into an input field of type="password", would it be possible to have the IsPassword property automatically turned on so the the password would not be displayed while recording? Currently the password will be seen in Test Studio when recording, until the IsPassword property is turned on. When recording during demonstrations, it would sometimes be nice if the password wasn't displayed.

There are some instance (e.g. find and connect to a ClickOnce WPF application) where it's desirable or necessary to launch the WPF application outside of Test Studio's normal launch process, then, using an API call, instruct the framework to connect to and automate (i.e. run the rest of the test) the already running WPF process. This would be most useful for ClickOnce applications because the install path frequently changes. Using code it can find and launch the WPF application. If there was an API call provided, the coded step could tell Test Studio to connect to it and run the test normally from that point on.

Currently for IE recorder we can configure the highlighting options on a project level, for the color, thickness and menu hold time. We should hook up the new Chrome and Firefox recorder to use the same configuration for consistency.

Please add clear browser cache button so it can insert a test step that is clearing the cache. Currently we do have clear cookies button and if you would like to clear the browser's cache you should use coded step only.

Currently our feature to send out automated emails is too difficult to use. It's badly documented and there's no indication that it even exists in the UI unless you know exactly where to look for it. I heartily suggest:
A) We move this to the cloud and we have it always be present in the UI and useable without any special configuration
B) We remove this feature

Currently our website lists it as a big part of the product and this is far off from how difficult it is to use.

I prefer having the properties window for the selected test docked somewhere in Test Studio.