Duration seconds

Ask general questions here.
BeardMJ
Posts: 27
Joined: Wed May 31, 2017 8:39 am

Duration seconds

Post by BeardMJ » Thu Jun 15, 2017 9:54 am

Hi

I've created some recording modules with the standard duration timer of 100ms but sometimes Ranorex adds it's own seconds without no user input, why is this?

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

Re: Duration seconds

Post by Support Team » Thu Jun 15, 2017 8:48 pm

Hello BeardMJ,

Delays don't start until after the object is found, which may take some time depending on numerous factors. Each repository object has a timeout setting built in which may be causing longer delays than what you expect. This timeout is the maximum time Ranorex spends looking for the object. If it is not found within this timeout, your test will fail.

With more information, I may be able to better assist you. What specific setting did you change and where in your test are you seeing an increased time?

Kind Regards,
Ned
.
Image

BeardMJ
Posts: 27
Joined: Wed May 31, 2017 8:39 am

Re: Duration seconds

Post by BeardMJ » Fri Jun 16, 2017 1:06 pm

Hi Ned

I have "MOUSE" click action that opens a popup, the popup comes up in mil seconds but Ranorex changes it to 3.67s.

The duration timer was 100ms, just seems odd.

Regards

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

Re: Duration seconds

Post by Support Team » Mon Jun 19, 2017 9:04 pm

BeardMJ wrote:the popup comes up in mil seconds but Ranorex changes it to 3.67s.
I am sorry, but I don't fully understand the behavior you are describing. You state Ranorex makes the popup come up 3.67 seconds later instead of 'mil seconds'? Screenshots of your module and playback report may better explain the issue.

If the duration is set to 100ms, the click action should occur as soon as the object is found, wait 100ms, then move onto looking for the next object/performing the next action.

Cheers,
-Ned
.
Image

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 3921
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Duration seconds

Post by odklizec » Tue Jun 20, 2017 7:35 am

My guess is that it takes too long to find an element? It does not matter that the popup appears instantly. What matter is the xpath behind the searched element. If the xpath is too general, Ranorex may have a problem to find the element and so it may take few secs to find it?

Please post a Ranorex snapshot (not screenshot) of the popup and xpath behind the searched element, so we can review both and suggest improvements.
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration

Hondo
Posts: 43
Joined: Thu Nov 03, 2016 12:03 am

Re: Duration seconds

Post by Hondo » Wed Sep 06, 2017 10:45 pm

I think the OP may be referring to the affects of cumulative Search Timeout Parameter values in the XPath Tree.

Assuming he's encountered a scenario where he knows the object isn't there and wants/needs Ranorex to STOP SEARCHING ALREADY!
but Ranorex continues searching/waiting for ## seconds because the UI Map has a nice XPath Tree.
Each element of the XPath Tree has a Search Timeout parameter set.. and they are being summed.

Totally configurable to taste and needs.