change of duration

Ask general questions here.
sravanimandadi
Posts: 4
Joined: Wed Sep 24, 2014 2:51 pm

change of duration

Post by sravanimandadi » Wed Sep 24, 2014 3:04 pm

hi, we are using evaluation version of ranorex 5.1. for a step in a test case we tried to change the duration and move time in properties to reduce the wait time taken for the step execution. but this is not reflecting when we are running the test case. can you suggest any solution so that we can reduce our execution time.

Bat
Posts: 16
Joined: Thu Jul 03, 2014 2:16 pm

Re: change of duration

Post by Bat » Wed Sep 24, 2014 4:09 pm

Make sure the timeout for it's parent folder is also set to a desirable value. It adds up the values from it's parents.

Ex.
AppFolder - 30 sec
RootedFolder - 15 sec
item - 1 sec

Total Timeout = 46 sec for item

krstcs
Posts: 2683
Joined: Tue Feb 07, 2012 4:14 pm
Location: Austin, Texas, USA

Re: change of duration

Post by krstcs » Wed Sep 24, 2014 4:18 pm

I would discourage (emphatically!!) changing the search timeouts. Remember that that timeout is the MAXIMUM time that Ranorex will take to find an item. It won't use the whole time if it finds it quickly.

However, the reverse can cause problems. Namely, if you set the timeout too low, then Ranorex will FAIL because it can't find the item in the time given.

Automation is not as much about speed as it is about consistency. The automated test will do things exactly the same way every time, where a human is likely to "fat-finger" values and mess up, which does cause delays, and is where the speed advantage is, not in just doing it faster (although it does that as well to a degree). If you are shortening the test because people are waiting on it, then maybe you need to re-examine the way you are employing the tests.
Shortcuts usually aren't...