petra wrote:
Seems like it is a timeproblem
Standart autowait timeout is set at 1 minutes . :catlol:
Maybe i will make a delay.
Checkpoints: In case of failor its not possible do reach any button or text.
By the way. i tested my program in midday, I dind't change anything, and it worked.
Thanks to you two
OK, first of all... AVOID hardcoded delays if at all possible... aqUtils.Delay is nice... but if the circumstances chance, you'll end up having to change code... again... that's why you should use WaitNNN methods and set the wait time sufficiently high to cover all contingencies... it avoids hardcoded delays and yet still allows your tests to work around synchronization issues.
As for your last statement, DEFINITELY a performance issue in your environment. Something slowed down your machine early on so that, now, it's working better. I'd suggest investigating that line of things as well that, if you know you're going to be running your tests during a particular time frame, make sure that nothing is going to impact performance.