When generating chained find expressions Test Studio always uses the id tribute for the parent element and it doesn't take into account the actual order of attributes.
Then, if you completely remove the id from the find logic list settings, the generated find expression uses only TagIndex for the target element and no chained find expression.
Generating this type of expressions need to be revised.
Example shared internally!
MaskedInput date field behaves inconsistently when automating the control. The type text action often types all numbers in the currently active part of the date (the year for example).
The workaround is to identify the exact sequence of actions, which allows entering the text correctly - for example, click on the input, press the Home key, press the Delete key to remove the current date, enter the desired date.
It will be great to improve the steps recorded out-of-the-box for that type of control.
Specifics shared internally.
Trying to set a variable in API test from a Json response body, but the used Json path isn't matching anything from the Json file. If testing the same in https://jsonpath.com, it returns the expected value.
Specific details shared internally!
We have a dynamic test list that includes several tests based on specific criteria. We executed this test list remotely once, but later decided to delete a few of the tests from the project.
The dynamic test list shows the correct set of tests that should be executed, but when we execute it remotely, we noticed that the previously deleted tests were still executing.
There is no way to sync the current project with the storage server and the only workaround was to drop the project, tests and test lists from the MongoDB.
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.
Verification for OuterMarkup is failing after the original recorded steps is converted to coded step. The workaround is to add a Wait for Exists step against the target element either as a recorded step or in the coded step.
Sample code for wait step:
I had been using Telerik for UI automation but never faced this type of issue earlier. So the problem is while recording the test the screen doesn't changes but while running or testing the same test case screen size changes unexpectedly which results in failed step as after the screen changes the location of the elements also changes.
PFA - Actual Image & Expected Image.
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.
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.
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 have a WPF UI that has multiple combo boxes, about a data grid. The Combo boxes are used to change what appears in the grid. When I am creating a test to verify the values of the items in the list, I am trying to get the hover menu to come up, but it quickly disappears when I try to get the menu item for a combobox item selected.
As a work around, I have been able to click Alt-Tab, and then go back to the screen, and that keeps the menu open for me to select an item, but I shouldn't have to do this.
I recently upgraded to Visual Studio 2022 and the IDE is now a 64-bit process. I am unable to assign a dataset while in VS 2022.
However, this still works within Test Studio...