When trying to open the generated .aiiresult file with Test Studio Result Viewer, I encounter deserialization error. There is also OutOfMemory exception in the Test Studio application log.

I can open the file with a text editor and it is 2 904 185 lines long, which might be causing the issue.

Another related issue is observed when the test list execution tries to generate the .aiiresult file, but it is too large. As a result the file is not created at all.

As a workaround, you can split the test list into two or more test lists to reduce the size of the result file.

Coded step is marked as passed, even though Assert verification fails inside a while or for loop. When the logic fails, the next lines of code are not executed, but there is no information in the execution log.

 

Currently only one of the attributes within an element's find expression could be data bound. 

It would be useful to be able to data bind multiple attributes at the same time. 

Currently there are no settings that allow us to configure how the element's find logic is built, when recording WPF tests. Test Studio uses XAML path in most cases, but there is AutomationId available on some of the elements and we prefer to use that as a more stable find logic.

Please add the possibility to configure and order the properties of elements for Desktop Automation, like WPF.

The Executive Dashboard gives overview of the application, by showing results from test list execution. We need to investigate the test execution and stability on the test level as well. 

It will be a great addition to the Executive Dashboard to show individual test results across different test lists from a certain time period.

I have a test list where there are few tests in it and its set to re-run failed tests. If a test fails it re-runs and passes after re-run but the entire test list is marked as failed in HTML results. 

The same test list is showing green (passed) in Test Studio and Executive Dashboard. The issue is only in the exported results.

Hi,

Is it possible to select what type of handing is set for the unexpected dialog in the Test List settings?

The current options provided are either "Do not handle", "Handle and continue" or "Handle and fail test". Whenever we choose "Handle and continue" or "Handle and fail test", can we also choose what kind of handling it is? Either to click "OK", "CANCEL", etc. just like the options to be selected in Test Step.

My AUT often checks for user inactivity and will automatically log off if there is no more screen activity performed. Sometimes the recorded test is to wait for a certain element to appear once a certain process is completed. But there are times the process takes longer time than the screen activity auto logout timeout.

However, before the logout, there will be a dialog prompted for user's confirmation, either to stay on page or directly log out if no response on the dialog for more than 1 minute.

But there is no further handling option to be set in the Test List settings, so normally the logged in user account will be directly logged off due to unable to click "OK" in the dialog prompt. This cause a lot of test cases to fail for wrong reason.

Therefore, please do kindly consider to add in the options to select what type of dialog handling in the Test List settings.

Thank you.

Error initializing recorder type omnisharp.extensions.jsonrpc.server.messages.errormessage cannot be serialized.

The error happens in Visual Studio and is a result of a conflict between different extensions. The Test Studio extension and JustMock extension in combination are causing the issue.

As workaround to continue using the Test Studio extensions in Visual Studio, you need to remove JustMock extensions.

If you have a large list of items and you want to select something from the middle of the list, the recorded "radcombobox: selecting item" step is failing.

The combo box is scrolled to the bottom of the list and if there item is not visible there, the selection is not successful.

TestStudio returns 0 for the number of tabs in a Kendo Angular TabStrip control. The behavior is reproduced on the demo page of the control - https://www.telerik.com/kendo-angular-ui/components/layout/tabstrip/tabs

Test Studio version is 2021.2.809.0

Extracted text from one element (PPSR FSID), used binding to set in another element (PPSR Search using FSID), Test failed because FSID could not be found, on closer inspection the set text had 2 different characters than the extracted text S instead of 8 and T instead of 7 (sorry snip is so wide) Have attached zipped code.

It is not possible to check if the visibility of certain element is "Hidden". Currently Test studio allows verification for "Visible" and "Collapsed", but not for "Hidden". 

Please add "Hidden" to the options.

Currently the new design of the step failure details is only available for Web tests. Please add this feature for WPF tests, as well.

When we execute a WPF test, there are no suggestions and additional details in the Test pane. We need to open the step failure details window, by clicking on the red "X" of the failed test step.

 

During a recording session with enabled Hover Over Highlighting, the context menu with recording options disappears before we can use it. This make it hard to add verification and action steps or locate the element in the DOM tree.

This only happens in one of the ComboBox dropdown controls.

Double left click desktop action is not executed in Chrome Headless browser. The step passes, but the action is not triggered as expected.

Currently it is not possible to change the image for recorded Image Verification step. In our case, the WPF application under test changes its state, when it is not on focus and it is not possible to capture the correct image.

We need to be able to change the image after the step was recorded.

WPF application closes after each test in the test list. I would like to choose whether to close it or keep it alive in its current state, after the test is completed.

Currently the Edit Test List window has fixed size, which causes usability issues when the test names are long, or when they are in a folder.

Make the window resizable and remember its previous size when I open it again.

Test Studio scheduled runs sometimes start browser in the background and it loses focus. Due to that the test steps are not executed correctly and the test fails unexpectedly.

This does not happen when running the test or test list locally.

Make it possible to choose whether or not to group the results from all iterations and provide average time, when exporting the results. 

I have 20 iterations of the same steps and it will be helpful to see the average time for each step.