Problem with speed of execution, it lasts too long

Ask general questions here.
dmu
Posts: 2
Joined: Fri Mar 25, 2016 3:32 pm

Problem with speed of execution, it lasts too long

Post by dmu » Wed Apr 27, 2016 9:02 am

Ranorex 5.4.5.19886
Desktop application - .NET

I prepared test scenario and I divided it on 3 recording modules. When I start a test case then it lasts too long. The third recording modul is very slow. It has problem with searching elements. When I start a recording modules separately one by one the problem does not exist.

Why i what should I to do with it?

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

Re: Problem with speed of execution, it lasts too long

Post by odklizec » Wed Apr 27, 2016 12:15 pm

Hi,

It's pretty hard (impossible) to suggest something sensible without seeing your test suite (at least problematic recordings), application under test (at least a Ranorex snapshot) and problematic xpaths.

You see, there is no 'magic' and always working solution for speed-of-execution-related problems. We need to see the problem, evaluate the xpaths and check the GUI structure to suggest changes in your test project.

Typically, slow element search means that the xpaths behind the repo elements are too simplified, with a lot of '?' characters or relative shortcuts. But as mentioned, it's hard to tell without seeing your test suite and at least a Ranorex snapshot (not screenshot!) of your app under test.
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

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

Re: Problem with speed of execution, it lasts too long

Post by krstcs » Wed Apr 27, 2016 2:40 pm

As Pavel said, this is most likely a path issue, but one other issue that causes this is that one of your other modules might be causing changes to your system-under-test (SUT) that are not accounted for in your last module. A button's text could change, or a field's value has been changed, and you were trying to use that changed value in the repo element's XPath.

In addition to what Pavel requested, please include the FULL TEXT of the error message you are getting. And while you are at it, check the element that it is failing on to make sure the path is correct. Then, if you can't see anything, run the first two modules again and then check the same path.

Remember, computers (and therefore the software running on them) are not smart and can't deduce like humans. You have to tell them exactly what to do, when to do it, and how to do it, and it has to be in the correct order.
Shortcuts usually aren't...

abrown
Posts: 3
Joined: Fri Apr 29, 2016 12:13 pm

Re: Problem with speed of execution, it lasts too long

Post by abrown » Fri Apr 29, 2016 12:38 pm

I have a very similar problem.

I have 3 test cases, and when they are all run at the same time, the execution speed of each test gets slower and slower the longer the whole process goes on, to the point where the tests fail due to timeout. It is not the individual tests, as if I reorder the sequence they are executed in, the same thing happens.

I have turbo mode turned on and I am executing the test without the debugger as this slows it down even further.

Do you have any further suggestions as to make the tests run, not necessary quicker, but not to the point of where they are timing out as I need to add further test cases onto the end of the process.

thanks,

Adam

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

Re: Problem with speed of execution, it lasts too long

Post by krstcs » Fri Apr 29, 2016 3:29 pm

Without more information it will be hard to help.

Please ALWAYS include:

Ranorex version
Windows version
Exact error message

If possible include:

Ranorex Snapshot of the element/application both before and after the issue pops up.
RanoreXPath of the element
Copy of the code being used, preferably the whole solution.
Shortcuts usually aren't...

abrown
Posts: 3
Joined: Fri Apr 29, 2016 12:13 pm

Re: Problem with speed of execution, it lasts too long

Post by abrown » Mon May 09, 2016 4:45 pm

Hi krstcs,

Ranorex version = 5.4.6
Windows version = Windows 10 Pro 64 bit
Exact error message = Timeout error due to system slowing down the further it gets into the test case.

As above, I don't get an error as such, you can visibly see the test case getting slower and slower the longer time goes on.

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

Re: Problem with speed of execution, it lasts too long

Post by Support Team » Thu May 12, 2016 2:20 pm

Hi abrown,

In order to analyze this issue in more detail, I would need further information about your environment and your AUT as well.
It would be great, if you could post a Ranorex Snapshot of your application. If you don't want to publish your snapshot in the forum, please send your snapshot to [email protected].

Thank you in advance.
I'm looking forward to your response.

Best regards,
Matthias
.
Image

abrown
Posts: 3
Joined: Fri Apr 29, 2016 12:13 pm

Re: Problem with speed of execution, it lasts too long

Post by abrown » Wed May 18, 2016 2:38 pm

Ok I have sent it through to you via email.