Validation should have Timeout property.
I see in Ranorex Studio it has Duration property but it is not the same as Timeout.
Validate with a Duration set to 30 seconds will consume 30 seconds even when validation condition is met after, say 100ms which is simple waste of time.
Use WaitForExists (WaitForNotExists) to simulate Validate with Timeout forces to have unmaintainable number of items in the repository.
For those who code much there is a workaround: wrap Validate in a loop with timeout (or maybe create own Validation class).
But the workaround is not the solution.
If Validate can have Timeout property it would resolve also problem described in "Create function for wait for visible and wait for not visible".
Thank you for your input.
Since we have improved the Ranorex runtime performance with Ranorex 9.2, we faced issues in our internal testing that also made it necessary to have some kind of “grace period” on validation actions. We are currently implementing a solution that should solve this issue.
Thomas from the Ranorex Product Management Team