I think that a commit comment should be required.

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.

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.

The Kendo Angular Multiselect control is not covered with the built-in translators.

It will be very useful and consistent if such translator is added in Test Studio.

BlazorTextArea records a KendoAngularTextBox step. Upon execution the step doesn't enter the text as expected. 

To workaround this, you can disable the KendoAngular controls group from the Project Settings -> Translators -> HTML and re-record the step. 

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 Test Studio load test can only use a dynamic target of type URL, if this takes its value from the response of a previous request. It will be useful to allow data driving this type of dynamic target with data from external source. 

A specific test cannot generate the output html file correctly when using the html option for CLI execution with ArtOfTest.Runner.exe.

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.

 

A picture is worth a thousand words...

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.

Allow the ArtOfTest.Runner to publish the results to the Executive Dashboard. There they can be seen by members of the team, who do not have Test Studio installed.

Make it possible for the ArtOfTest.Runner to use multiple execution machines. Distribute the test list execution to other execution servers.

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.

Currently the WaitForFrame method only takes FrameInfo object as parameter. It will be helpful to use WaitForFrame method with frame name only.

Telerik does not support test studio assemblies in .net standard and does not have a test runner in .net core. Considering all of our Azure DevOps and container agents are running linux we will not be able to use the tool.

Please add this feature to your product.

Hi Team,

 

I hope my email finds you well and safe.

I successfully managed to setup executive server. 

 

This ticket is not an issue but a suggestion from a team member of my company.

 

On the executive dashboard page it would be nice to have a description to show what this test list do. Think that the description it will be something that i will write it somewhere and show it up on the executive dashboard.

 

Thank you for your support

Kyriakos, Prevention at Sea

DisplayLabels can contain text, but because it is not a supported FrameworkElement, it is difficult to work with in code. Tests instead have to store a path to the element and use the full name - like Applications.MyApp.MyWindow.DisplayLabel1 - every time I want to refer to it. It leads to a lot of repetitious code as well as storing of unnecessary elements, especially where a Find.AllByType would otherwise be able to take advantage of the consistent structure.