Show MongoDB service's status in the Configure Test Studio Services window in MongoDB tab. If it is running, it should indicate it in a similar way as the Storage and Scheduling services.
Currently, only when you apply the service settings, it is started and that is shown in the status bar. If I close the Configure Test Studio Services window and open it again, that information is missing again.
Group custom dynamic targets with the same source step and value.
That way you can make changes to a group of dynamic targets at once. In this regard, maybe it will be helpful to allow multiple destination steps for one custom dynamic target.
Copy a User Profile with its current state of custom dynamic targets.
The existing workaround is to copy the whole load test, but that makes the project unnecessarily large and does not cover all scenarios. It would be helpful to be able to copy existing User Profile in its current state.
Add a toggle functionality for custom dynamic targets in order to enable/disable each on or all of them.
In the current state, you have to delete your custom dynamic target in order to disable it from your User Profile. That way you lose the information there and if you need it again, you must create it from scratch.
Currently the popup window for editing user profile, choosing dynamic target and adding new dynamic target are all opened on top of each other. This prevents the user from going back to the previous windows to view steps and request details.
It would be great improvement in usability to be able to switch back to the different windows while designing your load test.
Add functionality to delete all steps that do not match your filter.
After I filter out the unnecessary domains, I delete the individual steps. The primary reason that I perform this manual deletion is to detect extra Think Time steps which may linger after the filtering.
Add functionality to change all Think Times to the same value for the entire User Profile.
This would save having to go into each Think Time step and making a manual modification. This would save time and help ensure no stray values of Think Times (say 200 instead of 20) were entered.
This should solve the problem described in the following article: http://docs.telerik.com/teststudio/troubleshooting-guide/recording-problems-tg/silverlight-unable-connect-oob It is also related to this feedback item: http://feedback.telerik.com/Project/161/Feedback/Details/166046-the-recorder-cannot-attach-to-sl-oob-customer-specific-application
When multiple users have their hands on a product and code (10+ in our case) having to consistently address conflict issues with settings files has become overwhelming. I question why the "In Development" property is maintained at the project settings instead of maintaining the at the individual test level will significantly reduce issues with maintaining what is actually in development.
Hi Team, I would like to be able to use a cloud based browser platform similar to BrowserStack, Sauce Labs, Ghostlab, Browsershots, etc. In order to avoid setting up massive VM farms to distribute browser iteration testing. Thanks!
I am logging this feature request on behalf of Eugeniy Gorbovoy. Currently the timeout setting of http requests allows only numeric input and defaults to 2000 ms when left empty. The initial plans are to implement a global project-level setting for timeout that all http requests should inherit (unless locally overwritten). (I hope we will have it delivered in some of our releases in the near future.) This should handle most cases when users want to manage the timeout from a single place instead of manually increasing it for every new http step they create. Still the idea for accepting a reference to a variable seems appealing since some users might prefer to have several "tiers" of timeout rules across the test project and manage them using variables. Any comments and shared use-cases are appreciated.
Get the response body in the API test results, when it is executed from the API command line runner. Currently, the response body is only available in the Test Studio for APIs user interface and it is not outputted in the results.
The ScrollToVisible option is not available for some of the actions that use translators. One of them is the RadSearchBox, where this property is not available.
Currently the workaround is to add an Enter text step against the <input> element. To do that, you need to use the highlighter and record any verification step. Then add the Enter text step from the step builder, enable SimulateRealTyping and change the ScrollToVisible option.
The Keyboard (KeyPress) test step is missing the option to change the ScrollToVisibleType in the properties pane. Although the step actually performs the scroll to visible action and I see the code, when I select Edit in Code.
Please add the ScrollToVisibleType option.