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.
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.
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.