Some customers would like the ability to us e code as the condition in Test Studios If/Else logical block. They don't want to do everything in code, only the condition because not every condition is a simple verify some property of some element. Another less elegant solution to the problem is to add the ability of a GoTo step X from code.
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.
Sometimes customers want to be able to run their test with the browser launching in a special mode (e.g. incognito mode, custom/specific user profile, etc.). If the customer could add custom command line parameters to be used when launching the browser they could accomplish this.
We have all the recorded objects inside a silverlight iframe. Now our applications have changed and we don't have Iframe anymore. But existing scripts are not working as it throws error that silverlight/contentframe is missing.
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.
A project's BaseURL appends a slash after the URL is entered into a Project's settings. This is not idea in environments where you URL's are parsed like the following: 1) Protocol: http:// 2) Environment: dev, uat or blank 3) Sub Domain: admin, shopping 4) Domain: mycompany.com So when the base URL for the dev test list is "http://dev" for example. It navigates to http://dev/shopping.mycompany.com. It would be preferable in some cases if the test would navigate to http://devshopping.mycompany.com. To achieve that, there needs to be a method to remove the appending slash from the Base URL.
TS has the built-in ability to auto detect the jQuery change event for drop down and list box because it's pretty common there. In addition to that though we also need a more general way to cover all possible jQuery events that actually can be attached to any element, for example input.
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.
Option is currently limited to only the manual test opened in Test Explorer.
I'd really like to be able to use relative paths in WPF testing as we have different workspace definitions in our project and we have the directory context start in the root directory of the test project.
It would be nice to have the story board capture subtest screenshots instead of the "Test Step" placeholder. It would be fine maybe to watermark the screenshots with "Test Step," but still show the screens for reference.
All tests under a single project in Test Studio should be in one and the same namespace. If we use different namespaces Test Studio changes the namespace to the one set in the project settings. There should be an option to use different namespaces.
Add ability to specify on which execution servers to run the test list when run through the CommandLineClient. Currently you are only able to specify the scheduling server. When the test list is executed it will run on all execution machines that are connected to the scheduling.
In the Test Studio licence, the reports menu does not provide anything other than that pictured in the Documentation site under "Test Results > Reports". I want to be able to use the data in the database and analyze the results in a different way. For example, what is the total time taken for a specific test over time. ... or total data downloaded. How many non-fatal errrors are genereated in the loading of a page. How many images are loaded? What is the size of those images.
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.
Currently, the selected browser will open automatically before the first steps are executed. If there was a way to prevent this from occurring until after a pretest script is executed that would be a HUGE plus. Much the same QTP allows you to just execute a script and doesn't require the browser even be open and later you InvokeApplication to start the web based scripting. For instance if I want to change my hosts file to point to a specific DEV box I need to execute a batch file to update my hosts. But if the browser is open first then it's going to wherever it wants really. The only way around I've found is to execute the first cycle with a blank row to skip to the next iteration of the script but at the end clear and go to next hosts.
Hey guys, I'm looking for a feature in test studio that would allow users to have multiple ramp up/down times using the load/performance testing functionality. For example, start with X users then gradually ramp up to Y users over the next N minutes. After N minutes maintain a constant load of Y users for the rest of the duration of the load test. To me, this is the one feature test studio is lacking compared to the other players in the load/performance testing industry. Please like if you agree that this would be a great feature for the test studio team to implement. Thanks all! Steve Charlton T4G Limited
Many verifications (e.g. verify visible) can be made data-driven; but not verify exists, which has to be fixed at true or false. Can you introduce a data-driven version of the exists verification please? This would be useful in order to have a testcase which, repeated for a number of different user accounts, verifies that screen elements either exist or do not exist according to the user's permissions.