Validate.NotExists timeout too long

Bug reports.
eyalg
Posts: 4
Joined: Wed Jul 28, 2010 1:32 pm

Validate.NotExists timeout too long

Post by eyalg » Wed Jul 28, 2010 1:56 pm

I'm trying to shorten the timeout when looking for non existing windows from 10 seconds to 2 seconds.
I set SearchTimeout of 'winNewDSTInfo' to be 2000ms, and used the following code:
Validate.NotExists(repo.fldAddEditDST.winNewDSTInfo.Path,repo.fldAddEditDST.winNewDSTInfo.SearchTimeout,"DTS window should be closed",false);
I expected the search to take 2 seconds, but it actually still takes 10 seconds.
Any ideas what I need to be doing differently?

Thanks,
Eyal

User avatar
sdaly
Posts: 238
Joined: Mon May 10, 2010 11:04 am
Location: Dundee, Scotland

Re: Validate.NotExists timeout too long

Post by sdaly » Wed Jul 28, 2010 2:14 pm

This works for me....

validate.NotExists(path,200)

eyalg
Posts: 4
Joined: Wed Jul 28, 2010 1:32 pm

Re: Validate.NotExists timeout too long

Post by eyalg » Wed Jul 28, 2010 2:28 pm

sdaly wrote:This works for me....

validate.NotExists(path,200)

Thanks.
I tried that and the behaviour is the same. The timeout is still 10 seconds, eventhough the output is:
Element for path '/form[...]' does not exist (No element found for path '/form[...']' within 200ms.).

User avatar
sdaly
Posts: 238
Joined: Mon May 10, 2010 11:04 am
Location: Dundee, Scotland

Re: Validate.NotExists timeout too long

Post by sdaly » Wed Jul 28, 2010 2:41 pm

What about?

Validate.NotExists(repo.fldAddEditDST.winNewDSTInfo.AbsolutePath,200);

eyalg
Posts: 4
Joined: Wed Jul 28, 2010 1:32 pm

Re: Validate.NotExists timeout too long

Post by eyalg » Wed Jul 28, 2010 2:45 pm

sdaly wrote:What about? Validate.NotExists(repo.fldAddEditDST.winNewDSTInfo.AbsolutePath,200);
No, still no change.

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Validate.NotExists timeout too long

Post by Support Team » Wed Jul 28, 2010 3:44 pm

Hi,

I've tried it with Ranorex 2.3.3 and it works as expected. Which version of Ranorex you use?
Please can you also post the exact error message you get and the full path of your element.

Thanks and Regards,
Peter
Ranorex Support Team
.
Image

eyalg
Posts: 4
Joined: Wed Jul 28, 2010 1:32 pm

Re: Validate.NotExists timeout too long

Post by eyalg » Thu Jul 29, 2010 7:37 am

Hi Peter,

[edited]
I'm sorry for the confusion.
I found there was another function call that caused the 10 second delay.
Validate.NotExists() indeed works as expected.

Thanks,
Eyal