Currently, when a step in the API test fails, the whole test is stopped.
Please add the continue on failure option for steps in API project.
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.
It would be nice if there was a way to avoid simulating real typing for a search box. There is no option to enable/disable it, but it is clearly using this behavior. I've tried a workaround of entering text directly in the input element, but it doesn't seem to register it when this technique is used. I don't see how a textbox can be made to work without this behavior but a search box cannot.
Simulating real typing tends to be the most fragile part of our tests, and all we really need is to enter text and then search. It also slows down the tests quite a bit vs. just setting the text directly.
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.
Tests that have Not Completed tests, shouldn't list the overall test as Pass or Fail....rather it should set the overall run as "not complete"
In addition - when loading not completed tests within test runs, they are just shown as fail with no background and white text. The run is listed as pass if there are no fails but existing "not completes".
Recommendation to add Not Complete as overall result in addition to individual tests that are no in a passed or failed state
Custom WPF application with specific control - ViewBox, causes the highlighting to be misaligned.
In case the ViewBox control is removed from the application structure, the highlighting works as expected.