Which Windows Server versions are supported for use with Docker containers? The documentation here only shows how to setup up a Docker container on a Windows machine, but not on Windows Server and other images.
Please specify which version and images are supported for testing with Run-Time in a Docker container.
We use Test Studio with Visual Studio and we are able to use the Pending Changes feature of Visual Studio to see that we have changed certain test scripts and to check them in to source control.
It would be better to show changes of tests and steps in a more human readable form. This applies for Test Studio projects that are under source control in Test Studio IDE or in Visual Studio.
Some actions in specific application with frames cannot be recorded as expected.
The last version of Test Studio when this was working fine is R3SP1 2020 (v.2020.3.1209).
Further details shared internally.
We're submitting a feature request based on Support ID 1567144.
Currently the tool does not support selection of multiple files through Open-File-dialog in WPF apps.
1 possible solution can be to multi-select files through key-press(which is present in other automation tools).
Scenario: The steps for applying a filter in WPF grid columns is tied up with the index of the column in the current view of the grid. However, the columns in WPF grid can be reordered. And after changing the columns initial order, any steps to interact with the filtering, will act based on index in the current order.
Steps to get the scenario in action:
Expected is that you can identify the specific columns filters by their name, for example.
Actual is that the interacting with the filters is based on the order of columns. Or in other words the filter for the second column will be opened, if that was recorded, no matter if it is a different column.
Feature request: Implement the option to use the column names to identify the filters to select.
Workaround: The lack of this functionality can be covered in a coded step - the sample code below is based on the structure of the grid from the Telerik WPF demo app.
// Add the cilumn name textbloxk element in the Elements Explorer so that you can use it in the code. // Ensure its find expression uses the TextContent attribute - that way the element will be consistently identified no matter where it is in the grid var lastNameTextblock = Applications.WPF_Demosexe.WPF_Controls_Examples__GridView_ChartView_ScheduleView_RichTextBox_Map_Code_Samples.LastNameTextblock; // Locate the first parent element of that textblock, which is of type grid var cell = lastNameTextblock.Parent("Grid"); // Create a find expression, which searches for element with XamlTag=filteringdropdown var expression = new XamlFindExpression("XamlTag=filteringdropdown"); // Use it to locate and click on that element. cell.Find.ByExpression(expression).User.Click();
Please consider addition this component to the Kendo components library in Test Studio.
I built a WPF single file application with dotnet 6 with the following script.
dotnet publish \ --configuration Release \ --runtime win-x64 \ --self-contained=true \ -p:PublishSingleFile=true \ -p:IncludeNativeLibrariesForSelfExtract=true \ -p:IncludeAllContentForSelfExtract=true \ --output bin/publish
When using Test Studio, it cannot record actions. The compact recording toolbar is not visible.
At some point when reconfiguring the app path, a popup showed up :
Any feedback from you would be welcome.
Change color of different steps, based on their type. This will make it easier to read and maintain the test.
For example, I would find it really useful it Comments within a test could be a different color so they stand out better.
Executive Dashboard shows projects in the dropdown, even if they do not have results. We would like to remove them from that list.
Steps to reproduce:
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.