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.
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.
1. Open the attached aiiresult file Expected: To load the results in the Results viewer Actual: The results viewer crashes Resources shared internally.
A specific WPF application with custom controls cannot be highlighted correctly.
Details shared internally.
While connecting to Jira Cloud (https://name.atlassian.net) with valid userid and password, its giving error message "The remote server returned an error :(401) Unauthorized".