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.

The problem we're currently having is being able to leverage Test Studio in the same capacity of distributed testing through Azure DevOps which our IT organization uses for Continuous Integration.

Although the AOR-CLI does provide some benefits, it significantly is missing distributed testing which creates a large bottleneck in the turn-around times of our tests.

A potential way to solve this, as I've seen other testing platforms, is create a Test Studio Add-on for Azure DevOps in which you can handle calling your tests in the same fashion that you can from the Test Studio platform

As our team has grown, we have seen Test Studio record elements that already exists but with different naming conventions and under different pages.

Although I understand that much of the element class (pages.cs) is dynamically produced, I think it would benefit the end user to be able to drag/drop organizing the elements much like you can in other solutions.  This would help the end user have a better organized and less chance for duplication/mess of elements.

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.

Currently the exported result contains extended details only for the failed steps. If there is a warning for a step - like the warning that the element was found only by image, this can be only seen in the Test Studio result file. 

Extending the HTML exported result to show the step warning details will be very useful for anyone who review this type of result (attached in an email after a scheduled run, for example). 

Update the predefined device config settings with the latest available common iOS and Android devices. Check if the User-Agent request header needs to be updated as well, or more options to be provided. 

When the Scheduling server is not added during installation, the Configure button in Test Studio will be greyed out (disabled). It will be helpful to add some kind of tool tip or note about this.

The solution is to modify the existing installation of Test Studio and add the Scheduling Server feature to the installation.