Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium

New issue 876 by [email protected]: rebot-generated report.html should link directly to pybot-generated log.html files
http://code.google.com/p/robotframework/issues/detail?id=876

From a thread on the user group emails about RF 2.6 alpha 1:

Me: I would REALLY LIKE and recommend that rebot NOT produce its own new log.html file. There are a number of problems caused by this, the biggest two being the size and the fact that embedded images (screenshot on failure) get the wrong URL path. What I would prefer is that rebot should generate links from the main report.html file to each of the pre-existing log.html files in each of the sub-folders generated by the separate test runs for which it is providing a consolidated report. This would shorten the time to produce the reports, since there's no need to produce a new HUGE log.html and would allow the embedded screenshot URLs to work properly.

Peke: I'm not sure do I understand this. Do you mean a situation where you have executed tests, and generated logs then, and then want to combine results with rebot? In that case you already now can use `--log NONE` to suppress log generation but the old logs aren't linked from the combined report. It might be possible to handle this situation somehow but probably not before the release. This might actually be a good solution for situations where logs have been split earlier and is worth thinking a bit more. Please submit an enhancement request about it!

Martin, did I understand your enhancement idea correctly above? We took RF 2.6a1 into use in one real project and noticed that logs generated when combining results grow too big there too. Resolving this problem like you suggest might be a really good idea.

-----------

Yes, I think you understood my enhancement idea, and to make it even clearer I've attached a file showing the reporting file/folder structure from one of our test runs with annotations to explain what happens now vs. what I'd like to happen.

Attachments:
        RF_Report_Tree.txt  22.2 KB

Reply via email to