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!

"Active browser is now null", caused from disposed Manager instance, fails randomly some of the tests. The behavior is not consistent and can't be reliably reproduced, where the same tests fail.

 

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.

 

When too many tests are open and the tabs bar on the top of the tests sections is overflown, a small arrow at the right corner of this bar helps us to see all the open tests. But the tests cannot be closed from here. Earlier there was a X button on each of the tests but now that button is not available. We first have to open the test and then use the X button to close it . 



I prefer to have crossmark , near each of the test. Thank you!

The installation of Test Studio Web & Desktop comes with Test Studio for APIs and places a shortcut on the desktop. With this license though, Test Studio for APIs is not available and can't be activated. So, it should not be installed or at least there should be the option to skip it during installation.

If you have opened the web test and execute a performance test list, which includes this test, the performance details will not be updated automatically in the Performance tab.

You need to reopen the web test and go to the Performance tab to view the updated details.

Are there no settings in the application to adjust font sizes? 

There are two issues with the way load tests are created.
1. Editing the newly created user profile. At the moment we rely explicitly on recording. There is no way to edit what you have recorded and make changes to the request.
   - There should be way to copy paste requests.
   - There should be way to create empty requests which you can then customize.
   - There should be a way to use external data in the requests from a data store.
   - There should be a way to reorder requests.
2. There should be an easy way to test your requests. At the moment there is no way to test how the recorded requests in the user profile perform.
The only way is to run a load test with a single user and record with fiddler. Then, in fiddler, I evaluate what was executed and then go back to the user profile editor and make changes. It should be done directly from the user profile editor.

Our team utilizes Test Studio for our product's test automation.  The company as a whole has standardized on Zephyr (on Jira Cloud) for test case tracking / metrics / etc. but I'd like to avoid double entry of data, so it'd be nice if Test Studio would sync to Zephyr via the ZAPI interface to avoid doing double work with having to log test runs manually in Zephyr and create / update test cases in both locations.  Basically, I'm lazy and I'd like an automated way to keep this information in sync.

The video recordings are generated with the test list name and timestamp and the log is generated like so - TelerikTesting_Log_timestamp. I would like to have the option to change and customize those filenames.

I have an application, where 1 click triggers 2 consecutive confirm dialogs. I handled them both and Test Studio recorded 2 handle confirm dialog steps. 

When I run the test against Internet Explorer it works as expected, but in Chrome it is stuck at the second confirm dialog.

Auto-submitting a bug from local test run works as expected, but not from a remote execution server. 

The issue comes from the different certificates that Test Studio and the remote execution server use and the fact that there were changes in Jira's API.

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.

It will be useful to improve the output data in API test results. Currently the generated results files from an API test run do not contain data for the actual sent and received requests. 

The available workaround is to use Fiddler and capture the generated traffic during the API test run.

While IE is still supported by Microsoft, it just doesn't work well in some instances and has problems with some modern web design elements. Any chance of adding the capability or a possible workaround for using an alternative browser to recapture images for the storyboard?