As our team has grown, we have seen Test Studio record elements that already exists but with different naming conventions and under different pages.
Although I understand that much of the element class (pages.cs) is dynamically produced, I think it would benefit the end user to be able to drag/drop organizing the elements much like you can in other solutions. This would help the end user have a better organized and less chance for duplication/mess of elements.
After using Telerik Test Studio for a couple of yeas I have found a persistent problem. I have found myself renaming some objects in the Elements Repository because the auto-generated names didn't make any sense when they are used in coded step. The Element Repository engine that is responsible for maintaining optimizing the elements often consolidates pages and elements often causes some element objects to go "missing" because it has renamed these items back to some auto-generated form in most cases. Some cases I've had them disappear altogether because of our changing page definitions. I have still been trying to find what is the best way to implement pages within our given test environments.
The Step Builder and the Element repository optimizer is great for those who are less technically inclined (e.g. BQAs). However, I would like to request a mechanism for maintaining persistent names within the Element Repository. This is mainly because the loss of named elements used in coded steps. I have found myself resorting to the use of the XPath property to reference said object in coded step so that they, at least, compile.
I have tried docking the Step Builder panel within Visual Studio various times and causes VS to crash every time.