Dear Reader,
Having an existing test with several test steps recorded via the recorder while traversing a web page.
With that set of recorded steps, now saved. There is need to introduce a logic condition. The "STEP BUILDER" is used to insert a "Condition" of "if...else" via the button of "Add Step" this is successful.
The said "Add Step", "step" is added and the recorded test has the additional step, that now needs to be given the condition for the "if...else" clause. Opening up the dropdown there are a list in the dropdown of the "IF" statement, which is all the available steps in the test. Locating one of these steps is easy, what is not that simple to get done is the process of selecting that step to cause the condition to be accepted by the "IF" statement's condition. As this now requires that the opened dropdown list for the item that is desired to be selected, requires that the mouse must be clicked on in rapid succession in excess of five or sometimes seven "left mouse clicks", perhaps even more to get the click to register!!! The success of the selection is a surprise every time it happens as it seems like it is rather odd that a single or even double click does not do what should be reasonable behaviour.
I trust the above is sufficient to replicate the UX and allow a fix to be achieved.
Kind regards.
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.
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.