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