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.
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.
The Check for JS errors step is not working on remote execution with the Test Studio Test Runner. I have no issues when executing locally on the machine with Test Studio.
This is causing troubles for the CI builds and scheduled execution.
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.
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.
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.
Both options to delete a cookie by domain and by cookie do not work for Chrome and Firefox. It still works for Internet Explorer though.
The ClearBrowserCache step is working as expected and clears all cookies.
A specific WPF application with custom controls cannot be highlighted correctly.
Details shared internally.
1. Create local data for a test.
2. Data bind the same test to external data source.
3. Remove the data binding to the external source.
At this point I can't use the local data for data driven test steps or find expressions.
The workaround is to right click on the test and go to Properties. Then enable both DataEnabled and DefaultToGrid.
I ran a few tests in a test list in Test Studio Mobile, and noticed, there is no report. It is just a test list which contains passed or failed test cases. Is there a reporting feature similar to the one for Web?
Also, I would like to export the results of the test list as a part of documentation, having run a set of test cases. Does the functionality exist in Test Studio Mobile? I did not find anything matching these requirements in the documentation.
How can I show a report of the tests which have run? And export them?
Please let me know
For certain control Test Studio can record elements using chained queries - include parent and child element. If one wants to create such manually or modify an existing element to use chained query, needs to use the coded approach to define elements' queries. There is no way how to adjust an element's query to be chained if using the Edit element pane in the UI.
It will be really useful to add the ability to modify the elements queries and transform these to chained queries.