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.

Chrome Headless Failed to Select ByText when text value includes apostrophe.

The workaround is to select ByIndex or ByValue, if the value does not have an apostrophe.

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.

Test Studio does not record steps in all windows in specific WPF application. The recorder is attached, but the highlighting is not working for the main window and steps are not added. 

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.

Steps to reproduce: 

1. Record a sample test on https://demos.telerik.com/kendo-ui/textbox/index. 
2. Enter name in the KendoInput field. 
3. Add a step to verify the value of the KendoInput through the highlighting menu and execute these recorded steps. 

Expected: Successful execution.
Actual: The test fails on the verification step and reports that the value of the KendoInput is null. 
Additional note: If the verification is added for the input control (instead of using the KendoInput), it is executed as expected. 

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

1. Schedule a recurring job.
2. Rename the test list in Test Studio.
3. The recurring run entries in the Results view (the yellow coloured entries) remain with the old name of the test list. 
4. Upon first execution from the recurring runs, the generated result has the changed name of the test list as it is expected. 
5. The yellow items for the next coming runs of this recurring job remain with the old name even if Test Studio is restarted.

Expected: The upcoming recurring runs to reflect the change of the name.

Actual: The upcoming recurring runs remain with the initial name of the test list. 

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.

The translator for KendoAngularTextbox matches the textbox control in Kendo MVC and records the respective step. The execution of the test is not consistent. 

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. 

When recording a custom web application in Chrome, Firefox or Edge, no steps are added after the navigate step. There are elements listed in the DOM tree, but no steps can be added for these from the Advanced Recording tools. Highlighting is also not working. 

If recording the actions in IE these are captured and listed in the test. This recorded test can be executed against the other browsers. 

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 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.