Ranorex Forum

I get it now what you were pointing me at. So basically this is the expected logic for not exists method. It does not seem logical or convenient for me to use this method with RepoItemInfo without being able to specify the timeout. Yet I understand that it is as it is, so I will probably think of ot...

I am absolutely aware of the expected logic for such function. And I agree with your statements. The fact is that it should behave in two ways: 1. NotExists() confirms that element does NOT EXIST : confirms that element Not exists before timeout => reports SUCCESS message 2. NotExists() DOES NOT con...

Ranorex will always wait for the WHOLE timeout, or until it finds the item The issue I am talking about concerns the second part of your sentence. or until it finds the item As I said, NotExists() reports success message AFTER full time out. ALSO it will report same success message BEFORE full time...

Thanks for clarification, krstcs! If I map my problem on your example it would look like this: Ranorex waits for red car to disappear (NotExists()) for 1.5 min Ranorex knows that car does not exist any longer, yet it waits all the timeout time. Ranorex reports ?success after the timeout reaches. Ran...

Hi, Im using Validate.NotExists(RepoItemInfo itemInfo) method to validate that item was successfully removed. If I press shift+pause during its work and stop it waiting 1.5 min it reports this success message Element for item '<element>' does not exist (Failed to find item '<element>'. No element fo...

tvu wrote:You can use the WaitForNotExists() method.

Thanks that seems to do the job.

Hi, I am currently using NotExists() method in my test and It does not wait for element to change state. Element that I am testing waits for Push notification and is removed from list afterwards. This push notification arrives in random period of time so I have to wait for it 1-7sec. I checked NotEx...