Ranorex Forum

Hello!

Ranorex 5.0.3
Win7 64Bit

I have problem with "Global settings" option - "The factor that all timeouts of find operations are multipled with". Actually, i don't understand how it works, because when i set it to "2,00", this code just don't work:

try {
     repo.Explorer.ServerInfo.WaitForNotExists(1000);
     repo.Messages.SimpleError.SelfInfo.WaitForExists(10000);
     WarnIgnore();
} catch (Exception) {}

the test execution stuck on WaitForNotExists(1000) code, even after 1000ms timeout is over, it looks like ranorex still tries to wait-for-not-exist the "ServerInfo" item.

And the most interesting thing is that when i set "The factor that all timeouts of find operations are multipled with" back to 1,00 - everything works just fine.

I have 2 questions:
1. How the "The factor that all timeouts of find operations are multipled with" setting works for waitforexists method? What timeout "WaitForNotExists(1000)" will use, if i set this setting to "2,00"?
2. Whats wrong with my code, why the "The factor that all timeouts of find operations are multipled with" setting stucks my test execution?

I think it might be Ranorex bug. It really looks like Ranorex trying to wait for not existence of the element too long. According to multiple factor, timeout should be 2000ms, but Ranorex waiting for not existence of element much longer then 2 seconds...

Is anybody can say something about this problem?

Hi mihailo,

Sorry for the slow response.
In general if you set a “timeout factor “, all timeouts should be multiplied with this factor.
It seems that there is unfortunately a problem with the “WaitForNotExists()”-method. I already added an entry in our internal Bug-Tracking-System. The responsible department will have a look on this problem and I will get back to you as soon as we have any news for you.
Thank you for reporting this problem.

Regards,

Markus (S)

Thanks a lot for feedback!

Looking forward for any further information. This issue really prevents running my tests on slow machines...

Hi there!

Could you please tell me if there was any actions made to fix this issue? May be the last Ranorex update (5.1.1) contains fix of this issue?

mihailo wrote:Could you please tell me if there was any actions made to fix this issue?

The fix for this issue is included in the upcoming service release Ranorex 5.1.2, which will be released this week.

Regards,
Alex
Ranorex Team

Wow, thank you guys!