It will be useful to have ordered tests execution option in Visual Studio plug-in - an analog of Test List in Test Studio.
At this point recording a test for React-Native applications does not automatically use elements ID
Test Studio already uses a ~ as a wildcard option within Frame properties. could this same wildcard option be extended to the Compare Mode properties. The current behavior is that you can merge the pages together by changing the page Title to match, even a partial title, however when recording another step it generate a new page in the Element Repository. The desired outcome is that with the wildcard it would recognize the page as already in the repository and add any new elements within that page. For example, if I am building a test against Amazon.com they have many pages that start with Amazon.com:..., but have much more info that is dynamic following. A wildcard could just recognize the Amazon.com portion as the same page ignoring the dynamic portion. Compare Mode: Title and Title: ~Amazon.com
Add the option to select multiple tests to open in the Used By Modal When using the Used by feature on a test or element it lists all the tests using the element or test. But one can select only one test at a time to view or make any changes. It would be really helpful to be able 1 ) to select multiple tests to open 2) to be able to add these into a test list /view This will help to quickly modify/run/debug these tests when a change is made to the UI.
From ticket 846095 Many times I forget to hit the pause button when I start navigating or clicking in a browser with the recorder on. This of course creates a test step in my test without me noticing it until I run my test and get a fail or some undesired result. Having the option to set the default record state could save me time fixing inadvertently recorded test steps.
Desktop commands (e.g. Left Click on xxx) have a Focus property which controls whether or not a Scroll To Visible happens at the beginning of the step. When you turn on Simulate Real Typing (Set Text) or Simulate Real Click (Click X) I want the ability to disable Scroll To Visible. However I can't because these steps have no Focus property on them. In addition, I would like to be able to control what the default recorded setting will be. Currently Desktop commands default to Focus being checked and I'd rather have the default to be unchecked.
Just a few notes I wrote while writing some automated tests: When viewing steps of the test, is there any way to "unselect" the item so that the attribute name (that you define above the actual method name in .cs file) appears? When you open a test by default, its unselected, but when you actually click a step it only shows the method name. Sometimes I want to see both - is there any current way to do that other than re-opening the test? Is there any way to customize keyboard shortcuts? For example, I would like to scroll through tabs similar to how I do in visual studio when many tabs are open. I can scroll forward (ctrl+tab) or backward through tabs (shift+ctrl+tab). I would like to do the same in Test Studio without having to use the mouse...Also woudl be nice to maximize and collapse all methods/regions in the .cs file - similar to the ctrl+m+ctrl+l. When in the code behind file and saving a file with changes, the cursor disappears and doesnt stay focused to the file which prevents me from continuing to type and I have to click back into the file.
It would be helpful to provide Testing Framework coded samples on Kendo UI controls wrappers documented here: http://docs.telerik.com/teststudioapi/html/N_Telerik_TestingFramework_Controls_KendoUI.htm
The ability to specify a WPF window title using the dynamic options "Start With", "Regex", and "Contains" options would be very useful. We have several different testing environments, so our windows have titles like "ProgramName - Live", "ProgramName - QA", and even "ProgramName - UAT". However, there are no options except for exact match with WPF window titles, so I have to change every instance of the window name in my element repository each time I want to change environment. The only real work around is to change our software.
It would be useful to have simple expression to exclude entire folder from a project.
In the storyboard, many test steps (such as coded steps) do not capture a screen shot. It would be useful to be able to add a custom screen shot, such as of an alert box that a coded step is handling.
When up-voting, please use the comment system to indicate the solution from which you'd like to migrate tests. Keywords: migrate, migration, import, HP, QTP, UFT, QC, IBM, RFT, SILK, MICROFOCUS
When running a test list remotely, Test Studio should give users the option to run another list remotely or go to the Results tab. Currently, Test Studio always sends users to the Results tab, which creates extra clicks for users who want to run several lists remotely. For example, 1. Select a test list & click the Run List Remotely button. 2. Select the remote computer(s) to run the test list & click the Run Test List button. 3. On the "Your tests are now running" message box, add a button that gives user the option to run another list remotely. That way users don't have to navigate back to the Test Lists tab each time to execute another test list.
Allow the ability to create a custom folder structure to organize project elements within the Element Repository. This will be helpful for cases where there are many elements on one page, or other more beneficial orgs for elements. This should be an alternative and additional view for the element repository, retaining the option to see elements organized in current view.
When dealing with tests of ~75 steps or more, it is slow to scroll from top to bottom, and it is easy to get lost in a sea of text and similar steps. Right now I have comment headers to delineate different test segments within a single test, but that also makes tests even longer. If there was a way to create a shrink/expand folder or a similar organizational system to the If/Else expand and contract, that would make longer single tests a lot more manageable. (Perhaps even making a type of comment label where it functions as an anchor tag for snapping to different sections?) NOTE: Perhaps this is my misunderstanding of best practices in Test Studio as far as test length and Test As Step nesting. If so, an explanation might solve this.