Reports stuck in bin/debug

Bug reports.
Posts: 47
Joined: Wed Mar 18, 2015 10:06 pm

Reports stuck in bin/debug

Post by jackrabbit » Fri Jun 19, 2015 7:27 pm

In my project, I setup the Reports as such:
- I disabled the copy/move to the Reports folder
- In the Global settings, I enabled the report in the destination sub-folder "Reports" (= bin/debug/Reports)
- In the pre-build event, I added "rmdir /S /Q Reports" so that the bin/debug/Reports only contains the last report, not the prior hundreds of test during the developpment phase.

On Ranorex 5.2.3, if I run my test from the Test Solution page, it works, the Reports folder is wiped and my new report goes to bin/debug/Reports

If my run my test from a Recording (which I do a lot during the development phase), the report is being added to the bin/debug folder instead of the bin/debug/Reports folder.

After a few hours of debugging, my bin/debug folder always contains Gigabytes of unused reports, so I have to clean it up constantly.

The report should go in the specified folder, no matter how you got the test to run.

User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA

Re: Reports stuck in bin/debug

Post by Support Team » Tue Jun 23, 2015 9:17 am

Hello jackrabbit,

First of all, I would highly recommend updating to our latest version, currently Ranorex 5.3.2.

As for your issue, the global settings are only applied if you are executing the whole test suite, but in order to avoid unused reports during the development phase I would recommend disabling the report generation. It is possible to disable the reporting for each recording individually.

Therefore, please do the following:
  • • Open the recording
    • Open the “Settings”-dialog
    • Switch to the “Current Recording”-tab
    • Untick “Generate replay reports"
Hope this helps.

You do not have the required permissions to view the files attached to this post.