Ranorex Time Constraint

Ask general questions here.
AppTester
Posts: 20
Joined: Thu Sep 29, 2011 12:11 am

Ranorex Time Constraint

Post by AppTester » Thu Sep 29, 2011 12:25 am

I'm surprised that I could not find this answer in the forums, Google searches, or Ranorex FAQs. I'm just wondering, is there a limit as to how long a Ranorex test case can run? In other words, will the test time out after a while and just stop?

I have a test case that is supposed to run from 5:00 pm first day to 3:30 pm second day ... so it runs 22.5 hours. During this time the test is continually clicking UI items in a loop, just repeating the same thing over and over again.

For some reason the test fails in the middle of the night, and we don't know why. We've exhausted what seems like every possibility. We've even re-written the test case code. The test just seems to stop in the middle of the night, report no failures, just success. So were thinking that Ranorex can only run for a certain amount of time. Is this true?

User avatar
Ciege
Ranorex Guru
Posts: 1335
Joined: Thu Oct 16, 2008 6:46 pm
Location: Arizona, USA

Re: Ranorex Time Constraint

Post by Ciege » Thu Sep 29, 2011 12:34 am

Nope, not true... I have tests that run at least 16 hours that make it all the way through...

You have a bug or configuration issue somewhere... Could be a network issue over night or computer going to sleep or many several different reasons...

Add lots of error handling code, exception catches etc... to find out where the test is failing.
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!

Ciege...

AppTester
Posts: 20
Joined: Thu Sep 29, 2011 12:11 am

Re: Ranorex Time Constraint

Post by AppTester » Thu Sep 29, 2011 5:34 pm

The code has try-catch blocks through out. They do not point us towards the issue. Ranorex simply just stops, giving us a success message in the morning.

The updated code ran properly without issues until we extended the test to run overnight. We have ruled out any network issues that might arise during the evening. The machine is isolated and controlled to not be interrupted, not fall asleep, or not have anything different occur from before when the tests weren't running overnight.

The only change that has occurred since the error has started is that the test is running overnight now.

So I ask again, does anyone know if there is officially a time constraint for how long a Ranorex test can run? Our test runs for 22.5 hours.

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

Re: Ranorex Time Constraint

Post by Support Team » Thu Sep 29, 2011 5:45 pm

AppTester wrote: I ask again, does anyone know if there is officially a time constraint for how long a Ranorex test can run? Our test runs for 22.5 hours.
I can officially assure you that there is no time constraint.
AppTester wrote:Ranorex simply just stops, giving us a success message in the morning.
Is it always the same action that Ranorex stops at? Or a specific time?
Does the process/test run end or does it hang, meaning the process still runs but idles?
When you say you get a success message in the morning, does this mean the test runs through or do you abort it?

It could be something simple, e.g. a large timeout for an element that cannot be found. Or someone moving the mouse in order to clean it and thereby influencing the test run :wink:

Regards,
Alex
Ranorex Team
.
Image