Forum Discussion
Same machine. Nothing else running. The machines that run this are dedicated to this purpose. It is not a speed issue. The screen that should load from click neverloads.
Whay is the result if You spy the object at night?
It is different?
- vthomeschoolmom5 years agoSuper Contributor
The nighttime thing was a red herring. I observed it not working when running during the day. The issue is not reproducable when I run a single test. So I cannot tell what the spy sees. All I can tell is what the log shows me. I have entered a case with support.
- Marsha_R5 years agoModerator
Does it go weird in the same place every time?
- Wamboo5 years agoCommunity Hero
That's strange behavior.
To stop the test at night use this method:
Runner.Pause()
Check object with spy after these actions.
- vthomeschoolmom5 years agoSuper Contributor
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.
Related Content
- 2 years ago
- 8 years ago
- 8 years ago
- 7 years ago