Ranorex Forum

Hi,

I don't catch occurring Ranorex.ElementNotFoundExceptions immediately
but with a general surrounding catch (Exception e).
So during a long test run there are hundreds of such exceptions.

Problem: After some time Ranorex doesn't recognize anything anymore.
Questions:
Could there be a problem with Ranorex when there are too many of these ElementNotFoundExceptions?
Is there a better way to circumvent these Exceptions programatically?

My test setup:
Using my own .Net Testrunner GUI I coded several keyword based testfunctions:
e.g. Save_Program which uses several Ranorex.Button = <xpath> of the test object.
Some of the test object's GUI elements might not be visible all the time which is ok so far.
If one GUI element is not available I just take another visible one.

Best regards
Dirk

Hi,

Sorry for the late response. We are currently trying to reproduce your behavior and we will inform you about the outcome.

Regards,
Peter
Ranorex Support Team

Hi,

Sorry, but we were not able to reproduce the problem. Would it be possible to send us a short sample application with a Ranorex Project where this error occurs. Or can you describe us the steps to reproduce in more detail (a step by step description would be nice ).

Thanks in advance.
Regards,
Peter
Ranorex Support Team

Hi Peter,

unfortunately this behaviour is hard to reproduce.
It takes hours to show up the failure.
My post was intended to just ask a question about the proper implementation for these try-catches and to give a hint if there might be a long-time problem with these exception.

If I can find a simple setup to reproduce this failure I certainly will inform you.

Meantime please feel free to invest your time somewhere else
Regards
Dirk