Long running test aborts inexplicably and report won't open

Bug reports.
dochoa
Posts: 29
Joined: Tue Jul 16, 2013 11:36 pm

Long running test aborts inexplicably and report won't open

Post by dochoa » Mon Feb 08, 2016 5:18 pm

Hello,

I am using 5.4.4

I have a test that iterates through over a hundred rows to create items in a database using the UI.

I left it running on a Friday and came back Monday to see the result.

I noticed that IE was still on a page that it would be on mid test (I close it between iterations)

It had only created 92/103 items.

Ranorex was no longer running (no run window showing the current step)

I can't view the report because trying to open it results in "Data file or transformation file is missing"

Can you point me some direction to investigate or prevent this?
(I even tried renaming the temp report file but it still does not open).

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

Re: Long running test aborts inexplicably and report won't open

Post by odklizec » Mon Feb 08, 2016 7:25 pm

Hi,

From the description of the problem it sounds as if Ranorex crashed during the test execution. I would suggest to check Windows event viewer for any entries around the time of creation of (corrupted) report file. Btw, could it be that your computer has been auto-restarted (e.g. due to windows updates)?
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

dochoa
Posts: 29
Joined: Tue Jul 16, 2013 11:36 pm

Re: Long running test aborts inexplicably and report won't open

Post by dochoa » Mon Feb 22, 2016 9:42 pm

I see nothing in the windows event logs explaining this and no restarts.

I would have also attached the DATA_TEMP file that shows that the file just stopped getting written to but it is too big to upload.

Have you seen this before?

This is how it ends:

<item
timeRelativeToTestSuiteStartTime="06:22.317"
timeRelativeToTestModuleStartTime="00:00.218"
timeWallClock="14:20:12"
time="06:22.317"
level="Info"
category="Validation">
<message>
Validating NotExists on item 'CMTCMT.AnySelectedSeatZone'.
</message>
<metainfo
type="repoitem"
path="/dom[@domain~'contwebdev']//div[#'ms-SeatZones']/div[@class='ms-selection']/ul[@class='ms-lis

dochoa
Posts: 29
Joined: Tue Jul 16, 2013 11:36 pm

Re: Long running test aborts inexplicably and report won't open

Post by dochoa » Mon May 15, 2017 5:06 pm

Hi odklizec,

Was there ever a solution for this, using 6.2 I have the same issue today with a test running 80 iterations.

Can I roll the log?

Today my test passes but the report can't open with a .rxlog.data file > 700,000KB.
Is there a size limit?

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

Re: Long running test aborts inexplicably and report won't open

Post by odklizec » Mon May 15, 2017 6:05 pm

Hi, I'm not aware of any report size limit. But honestly, 700MB report sounds quite crazy :) I don't think that such huge report could provide any useful info. If nothing else, it would take long time to just open it. You should definitely consider running your tests in smaller batches. Either by using run configurations or splitting your test to smaller chunks and run them separately.
Last edited by odklizec on Mon May 15, 2017 6:59 pm, edited 1 time in total.
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: Long running test aborts inexplicably and report won't open

Post by krstcs » Mon May 15, 2017 6:53 pm

Yeah, I have to agree with Pavel. You should be running your tests in batches or distributed among several VMs. This will make it much easier to manage.

I have 8 VMs and use Jenkins to control the actual runs (I think Pavel does about the same). This is definitely the best way to handle large test runs.
Shortcuts usually aren't...