I think I am having this problem in chrome. I am running telerik test studio version 2013.1.806.0, and chrome Version 28.0.1500.95 m.
In our web application, selecting a value from a filter drop-down list automatically refreshes a table of data below. In my test the click is happening correctly and the screen is correctly refreshing itself, but the next step (a coded step which verifies the refreshed state of the table) is failing because it doesn't wait for the refresh; and if I force it to wait, it is still reading the old state of the DOM, from before the refresh.
I have tried the following workarounds, mainly without success:
This does not work; the test does not wait at all, but carries on before the refresh has completed.
This does not work either; again, the test does not wait at all but continues to the next step before the screen has refreshed.
This is a suggested solution from a previous thread
; does not work either; again, the test continues to the next step without waiting for the refresh to complete.
This does not work, in quite an interesting way. It does wait for ten seconds, by which time the screen has completed refreshing. But the coded step fails because it is getting the data from the old DOM tree, from before the refresh.
This is the only solution I have found which does work:
After I have called the RefreshDomTree method, the coded step succeeds because it is now seeing the correct refreshed data.
The problem does not occur at all when I run the test on IE10 or Firefox 23 - the coded step automatically waits for the screen to refresh, automatically uses the refreshed DOM tree, and the coded waits, delays and refreshes are not needed. I only get this problem when running the test on Chrome.
P.S. The web application is built in asp.net, and the control's html calls __DoPostBack like this: