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.

On this page:
http://docs.telerik.com/teststudio/user-guide/knowledge-base/test-execution/using-baseurl.aspx

We talk about how to use BaseUrl for the NavigateTo steps and the iframe nodes. What we're missing is how to adjust the Connect to Popup steps so that they too work in multiple environments.

The screen shots on this page are very out dated:
http://docs.telerik.com/teststudio/user-guide/troubleshooting_guide/test-execution-problems/chrome/cannot-execute-in-chrome.aspx

Please add a submenu to the 'Run to Here' which allows you to select the browser to be used instead of the default specified.

The only way to select a different browser for 'Run to Here' is to go into 'Project settings -> Browsers' and remove the default browser.

If a compatible compatible database engine is not installed, no sheets are listed to select from when data binding a test. See ticket 881911 for the symptoms and solution.

Since quite new the Shadow DOM in HTML5 is not supported by Test Studio. In order to reproduce, load the website from the internal description in Chrome and try recording against the login form.

I have been using test studio for 3 years.  

I allow these constant gripes with test studio.  

As shown in this 1st screencast link, you will see that after I click Execute, Test Studio takes me to the bottom of the test instead of leaving where the test was at the time I click Execute.  

As shown in the 2nd screencast, you will see that I go to my Results.  The testlist results is not leaving me at the point when I left the Result page.  The Results constantly reloads unnecessarily even when the results were loaded the first time. It is so frustrating to wait for the results have to load over and over without reason. 

Each test studio project has a setting.aiis file as if it was a solution file from visual studio.  Allow users to open test studio projects directly from file and not needed to go through the process of launching test studio and then select the project to open. 

With the Multiple Test being opened, there is a limitation with the current build.  There appears to be only 1 Execute option when dealing with multiple test at the same time.  Each opened test should have its own option to execute and not be hinder by other opened tests. Like shown in 3rd screencast link.  

There is Base URL.  There are 3 distinct locations for baseurl.  WHY?  The Project BaseURL seems get overridden when attempting to use the BaseURL within a test's navigate step or within a test list's setting.  Drop the unnecessary BASEURL. Shown in 4th screencast.

After opening the Test Studio Project and click Test List, why does it take a while to actually load all the test lists?  The test lists are not more than query based references to specific tests in the project. I noticed that at the bottom on the page, there is a note of Extracting Element from Tests shown in 5th screencast.  Break this dependency and improve the load time of the test lists.  

In the 6th screencast, there appears to be unnecessary whitespace.  In a previous feedback item, I suggested this: http://feedback.telerik.com/Project/161/Feedback/Details/137316-customize-location-of-menu

I also have another feedback item: 
http://feedback.telerik.com/Project/161/Feedback/lo[o/137289-closing-multiple-tests

Last item on my rant is this feedback item: 
http://feedback.telerik.com/Project/161/Feedback/Details/133771-while-loop-count-for-coded-step
2 steps versus 12 steps for a while loop.

http://screencast.com/t/q8icfzpyW
http://screencast.com/t/UMgggyYgP
http://screencast.com/t/2ZwT9eM8HD
http://screencast.com/t/sWLhIvTwqiax
http://screencast.com/t/0ecaFaD0gb
http://screencast.com/t/BdnGaSnR

The selections in the Schedule Test List wizard are not being saved. Say in step 3 I select "Send test results by email" box in that wizard and all attachments, then navigate back a couple of steps, then forward again. "I'm good... no mail for me" is selected instead of what I selected and all attachment boxes are unchecked.

Some HTML applications have an overlay div at the top and/or the bottom of the browser window. This causes a problem for elements that require ScrollToVisible selected. Test Studio will unconditionally scroll the element to the top of the browser window, which ends up scrolling the element so that it's hidden behind the overlay div.

Currently the way to handle this scenario is a bit complex:
1) Add an extra step to scroll the element above the target element to the top
2) Convert the real click step to code and comment out the ScrollToVisible line of code

This is not at all intuitive or obvious. Can't we come up with a better solution to handle this scenario? See the video added to the internal feature request for a demonstration of a real customer application that demonstrates this problem

There are several requests over the years to implement a way to force stop the execution of a test in cases of a hanging processes during execution. For example to set 10 minutes timeout and if a started test does not finish in this timeframe, to force stop the execution of the test and kill active processes related to the test, so that the execution of the rest of the tests in the list is not hang because of this particular test.

A customer suggested the ability to import template definition on creating new projects. Every time they create a new Test Studio project they would love to have custom project wide settings already applied, such as:
a.	References to custom assemblies
b.	Recording settings

Please add Ctrl+f and Ctrl+h to the code behind views to be able to search and replace text.

Please add Ctrl+Tab functionality to be able to switch between open files.

It would be nice if we implement a ScrollToMiddle feature in Test Studio. The reason for this is that we have ScrollToTop and ScrollToBottom, but sometimes when we have static elements  for example static header or footer in a page the following problem is experienced:

In a test if you want to click on an element that is scrolled to visible the element in question is getting under the static header or footer on the page and cannot be clicked.

Steps to reproduce:


Start recording using Chrome or Firefox against: 

http://demos.telerik.com/kendo-ui/editor/index

No text gets recorded by Test Studio