Thank you for contacting us!
Indeed, Test Studio records elements based on pages. If you happen to record hundreds of elements against one and the same page (I've seen such really huge applications customers automate) you are likely to get hundreds of nodes under the same page/SilverlightApp parent. Unfortunately the elements explorer does not support custom views and I suggest you vote on the feature request
The best available today is setting friendly names to the elements prior to adding manually (the first option in the recording element menu
) so that you can easy search for those later using the built in search option exposed in the Elements Explorer UI. I've seen customers manually adding all the elements they will need in order to set friendly names then using the Step Suggestions feature
to build their tests. Whether to prompt for element name prior to adding to the repository is controlled by the setting on top of the General ones as in the screenshot here