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.
Test Studio should also be able to scan and test for accessibility compliance issues. See https://github.com/dequelabs/axe-core for an example scanner. This could be integrated into the main product or as a plug-in.
Create a command line option to output the results of an ArtOfTest.Runner execution of a Test Studio test or test list in MSTest .trx results format.
The method PublishManager.CreateTRX that some customers were using to convert aiiresult files to trx no longer works in the new versions on Test Studio because JSON is not supported. You can use the attached project for repro.
When a customer first sees the "Verify IsVisible" they are sort of naturally inclined to believe that Test Studio will test whether or not the target element is actually visible within the browsers window. This leads to frustration when they try to use it and it doesn't work the way they imagine it should work (see ticket 814023 for an example of this frustration). For example, if the element is not present in the DOM, the test will actually fail with "element not found" instead of passing a test step "verify is not visible" as one would naturally expect given the incorrect assumption above. Or the test may pass indicating the element is visible when it's just hidden behind another element or scrolled out of view. I'm not sure what the right answer is... do we change what IsVisible actually does? Do we change the name of the verification so it better reflects what it's actually verifying (which is the DISPLAY and VISIBILITY property of the element)? The current code/action is useful, once you correctly understand what it actually does. I'm filing this just to log it so we can start discussion on how to eliminate the ambiguity of this particular verification.
To be able to run browser as different user than the windows authenticated one. Pressing shift and right mouse click will allow the option to run the application as a different user. It would be useful if this could be automated with Telerik Test Studio.
test studio integrated code editor - commenting out/in keyboard Shortcuts Quite simply it would be nice to have a few keyboard shortcuts in the integrated test studio code editor, such as the ability to comment out/in a line of code (or blocks of code) without having to manually place the "/"'s for every line. I know we can open the projects in Visual Studio, however sometimes it is not worth the hassle when you are already in Test Studio for whatever reason to just switch out to Visual Studio. Thanks for listening! Dan
Steps to reproduce: 1. Using the project attached execute the existing test list. In the 0 test there is a test as step with enabled StopTestListOnFailure. While the feature works fine out of the box, it is not working if the test is included as test as step.