At this point it is possible to run a WPF application with arguments only as a workaround - starting a separate process in a coded step as given in this example.

It would be more useful if this feature is implemented when configure the WPF app in the test.

Multiselect control cannot be recorded against IE as expected. When selecting more than one value from it, using the Ctrl key, not all selected options are listed in the 'SelectedItems' step property.

The 'SelectedItems' step property does not display names of the selected items and it is not visible how many elements there are to be selected. 

If the desired items are manually added in the mentioned property, they will be selected correctly in run-time. 

While connecting  to Jira Cloud (https://name.atlassian.net) with valid userid and password, its giving error message "The remote server returned an error :(401) Unauthorized".

Currently any custom added dynamic target should be created separately for each next request.

For example, if there is a user session token generated in the first responses and used in the following requests (as a cookie, header, etc.), the only way to pass it to all upcoming requests is to create a new one for each request. 

It will be useful to have the ability to reuse the already created custom target and only change its destination step. 

Currently Test Studio supports Toggle calendar action and selecting date from the visible month when automating Kendo Angular datepicker. 

It will be helpful if the support is extended and setting the date directly in the KendoInput is also an option. As of now using Actions.SetText() is not triggering the necessary events and real user behavior is required to handle the scenario. 

Depending on the exact implementation, a coded step may be required to enter valid date. 

Test Studio  Run-time edition does not deploy the TestAdapter.dll with its installation.

Thus Test Studio tests cannot be executed with the VSTestConsole.exe in a Azure DevOps (VSTS) pipeline. 

Workaround: 

The TestAdapter.dll for VS 2017 and VS 2019 is being deployed to the Test Studio installation folder (for Ultimate or Dev Edition installations) along with the respective *.vsix package. Until the misbehavior is fixed, the vsix package can be copied to the agent machine and installed with double click. Then refer the dll from the respective location. 

Ability to record a test step and then change the Element with an existing Element.

Here is the workflow:
I record a step and edit the Element.  Then every time I record on the same UI object, Test Studio creates a new element.  Since it creates a new element, I have to manually edit every duplicate element to exactly match the first element in order for them to merge.  I would like the ability to change the element the step is using to an existing element.  

When you schedule and run a test list you get the following entries in the Scheduling server log:
[05/06 19:32:52,Telerik.TestStudio.ExecutionManagerService.exe(4344:12),Execution] JobBroker.ScheduleJobAsync() : Job satisfied all preconditions, id = eae7a94a-c7b8-408f-9021-3a315eeb1042
[05/06 19:32:52,Telerik.TestStudio.ExecutionManagerService.exe(4344:12),Execution] JobBroker.ScheduleJobAsync() : Job sent to scheduler, id = eae7a94a-c7b8-408f-9021-3a315eeb1042
[05/06 19:32:52,Telerik.TestStudio.ExecutionManagerService.exe(4344:12),Execution] JobsController.CreateNewJob() : Accepted new job, Id = eae7a94a-c7b8-408f-9021-3a315eeb1042
[05/06 19:33:28,Telerik.TestStudio.ExecutionManagerService.exe(4344:40),Execution] JobRunner.RunJobAsync() : TestList loaded for job ID = eae7a94a-c7b8-408f-9021-3a315eeb1042
[05/06 19:33:28,Telerik.TestStudio.ExecutionManagerService.exe(4344:40),Execution] JobRunner.RunJobAsync() : Job started, ID = eae7a94a-c7b8-408f-9021-3a315eeb1042
[05/06 19:34:10,Telerik.TestStudio.ExecutionManagerService.exe(4344:12),Execution] JobRunner.<CleanupTestRunsStatus>b__12() : TestList finished; updating dispatch group header job Id = eae7a94a-c7b8-408f-9021-3a315eeb1042
[05/06 19:34:10,Telerik.TestStudio.ExecutionManagerService.exe(4344:12),Execution] JobRunner.<CleanupTestRunsStatus>b__12() : TestList finished; sending notifications
[05/06 19:39:10,Telerik.TestStudio.ExecutionManagerService.exe(4344:28)] First trace message from pool unnamed thread (managed ID = 28, native ID = 12868).
[05/06 19:39:10,Telerik.TestStudio.ExecutionManagerService.exe(4344:28),Execution] JobRunner.<CleanupTestRunsStatus>b__12() : TestList execution status expired- removing from list job id=eae7a94a-c7b8-408f-9021-3a315eeb1042

What's missing is which execution server the test list was sent to. This can be important information in a setup that has multiple execution servers.

The size of failure information field in the verification builder is only two rows and cannot be resized. 

We should copy the text somewhere outside of Test Studio in order to see it.

Steps to reproduce:

1. Create a test with a verification step.

2. With an attached recorded right click on the verification step and choose Edit.

3.  The Sentence Verification Builder appears and if the validation fails the information field is really small and unreadable.

See the attached screen shot.

I have this idea in mind but not sure how to start with. How to add a custom option(control like a button or check box) in the UI?

From ticket 869169

In the attached screen shot is an example of an ASP.NET partial page update. It includes a URL with a dynamically changing query string. The application needs that query string echoed back in the next GET.

Currently Test Studio load tests do not parse "text/plain" responses for dynamic targets. As a result this scenario is not currently supported.

When DBMigrator is in progress all you see is "Please wait...". There's no indication how far it's gotten nor how much farther there is to go. The user can't tell if he needs to wait another 5 minutes or another 5 days, or even if anything is actually happening. Some sort of feedback needs to be shown the user indicating progress is actually being made by the migration process.

In addition, when the process is completed, it would be useful to show something like "N records migrated" to indicate success or failure of the migration process. Instead currently when the process is finished the "Please wait..." is removed. The user can only assume the process was successful and how much data was migrated.

Displayu the full test list name/Execured browser in the tooltip in the same way as it is in the calendar view on results tab.

Refer to the attachment provided internally

Currently when a test step is set to SimulateRealClick or SimulateRealTyping, the target element is unconditionally scrolled to the top of the browser window, even in cases where the element is already visible.
It would be more efficient to test if the target element is already fully visible and only scroll when needed.

Currently when Test Studio wants to scroll an element to make it visible (such as when SimulateRealClick or SimulateRealTyping is enabled) Test Studio will always, and unconditionally, scroll the element to the top. This causes problems for a few applications that have a static UI element, the target element ends up being scrolled underneath this static UI element.
It would be helpful to have a global setting which controls whether the target element is scrolled to the top or the bottom of the browser window. The parameter is available in the API, just need to expose it as a step setting, or a global setting so that customers aren't forced to convert the step to code and override the default behavior, which can be time consuming when there are lots of steps that this must be done on.

I like the new user interface of test studio and its tabbing options.  

But I do not like the static location of the Project, Elements Explorer, Properties, and Step Builders.  

Provide the ability to customize the location of the listed items to other areas.  

For instance, in test studio, the properties windows has unused space.  So I would make the window in the lower right hand side instead of the entire right side. 

Also in test studio, the element explorer takes up the whole left side.  The step builder is closely related to the element explorer and I would like it together

Web Services has become one of the key software endpoints that demand thorough testing. While load testing for web services is already avaialble, I would like to propose making testing of web services for functional requirements also available from within Test Studio. Support for REST, SOAP and OData Services should be made available.

A lot of new apps use web services (WSDL or REST based). Test Studio should provide for API testing. Fiddler already has some great components that can be reused: 
1. Composer (with header addition/modification)
2. Response Formatter (with header response etc)

All that is needed is simple validation screen based on RegEx for the response.

Looking at the test results one gets an error message only, which doesn't help much in general. Instead we should provide an easy way to take the remote execution log from the execution machine to troubleshoot the actual failure.