When I run my test that requires a button click event it works fine. However, when that same test is run from test list, it does not - the web page remains the same, with the visible button not being clicked.
Weird, this only seemed to happen after upgrading to 2022.1.215.0
Steps to reproduce:
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.
A specific coded steps test cause Chrome to be closed when trying to perform a partial run using Run->To Here.
The coded step before the navigate one is starting a proxy to log the traffic.
Sample project is provided internally.
The specific page and the frame, which is not identified from Test Studio, uses a Salesforce component called ForceAlohaPage and it seems there is a custom implementation for the frames in this component. These are not visible in the Windows.Frames collection, which Test Studio uses under Manager.ActiveBrowser.Frame.
Trying to open a RadComboBox with
var csBox = Window.Find.ByName<RadComboBox>(ComboBox);
csBox.EnsureClickable();
csBox.SelectItem(1);
Observing the automation shows we are waiting no time for dropdown to open and I am getting exceptions claiming there are no items in the list.
The cause is related to the fact that the public void WaitDropDownAnimation(int millis) method of Telerik.WebAii.Controls.Xaml.Wpf.RadComboBox is not working as expected.
Workaround: You can use Window.Find.ByType<RadComboBoxItem>().Wait.ForNoMotion(milliseconds); before selecting the item from the dropdown.
When used in code Wait.For() certain element's attribute state, does not respect the timeout set to wait.
Additional details shared internally.