That's strange behavior.
To stop the test at night use this method:
Runner.Pause()
Check object with spy after these actions.
I just talked to the developer. Holy Oy Vay. So. Here is what we THINK is happening. That button I am trying to click? It moves. When the page is written server side, it is in one place, then is moved to another lower in the DOM. Ok that stinks. But I am aiming at the correct button. BUT I am speculating that the event handler for that button is not ready yet. This is the same behavior for many, many, many (like many more manies) buttons within the app. I increased the delay between events to absurdly high to wait for the code to futz around client side to see if this does anything. I will give more info when I can.
I have the strong sense that this is the problem since all debug actions are not presenting the symptom. It is likely working locally because the local machines we use are rocket ship fast compared to the production where the tests are getting executed.
I have many manies questions. :)
Are you clicking button by coordinates or by name?
When the button moves, is it ending up off the visible part of the page?
Why is the button being moved?
Hi,
> I have the strong sense that this is the problem
Sounds very reasonable. What technology tested client application is based on? (Guessing Angular or something like that.)
