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.
Please add the ability to create and schedule Test Studio API and Test Studio Mobile test lists.
When adding additional steps to an existing test, they will appear in the beginning or the end of the test. In web testing new steps place themselves under the step selected (often: run to here), and I would love this feature in mobile testing as well. Would save a huge amount of time that I spend finding and moving test-steps.
When Daylight Savings Time ended on November 6, our scheduled tests started running an hour earlier than scheduled. I had to "edit" each schedule (without actually changing any settings) and save in order for the time in the "TimeToRun" setting in the job details file to adjust for the time change. It would be nice if this could happen automatically. Or maybe add a right-click option to for updating the time or something.
When drilling down the results of a test list to a failing test, it would be nice to be able to go directly to the test editor for a test rather than having to go back to the Tests tab and traverse the folder structure in order to locate and edit the desired test.
There should be a way to run only selected test cases from a test list. If few test cases fail in a list, then we should be able to select those test cases and run only selected test cases.
It would be nice to be able to include an existing test list as a selection when creating/editing a different test list. This would allow for simple lists to serve as the basis for more complex lists, making list changes more manageable and simplifying the creation of larger test lists.
Now when you run the test through "Run From Here", "Run to Here" or "Run Selected" it doesn't stop at the break points.
When we generate our reports, Test Studio will only indicate to us the number of test cases that were executed. The problem here is when we use data driven testing, the number of scenarios executed can be much higher than the number of test cases. For example, if we have 10 test cases in our list, but each test case runs through 10 iterations, Test Studio will only report that 10 test cases have been run, not the 100 iterations. This makes getting an accurate report of our testing very difficult. If one iteration fails inside a test case, then the entire test case is considered a failure.
As part of the RunResults email that is sent after a scheduled test list is run, I would like to be able to include the test owner as part of the failure information. We have multiple people developing scripts and it would be nice for everyone to be able to glance at the email and see if any of their scripts are failing.