kOoO wrote: ↑Thu Aug 29, 2019 2:11 pm
When "Tracing screenshots" setting is set to on (foreground), screenshot is silently taken for every little debug message that is logged. Why? The screenshot is not even displayed in report. It affects performance - every log message takes about 30 - 50 ms. When screenshots are off, every log message takes about 0.5 ms
Screenshots are only shown if there are failures (and you can set how many are shown using the "Ranorex.Core.Reporting.TestReport.TracingScreenshotCountLocal" setting), but we need to take the screenshots anyway, because we don't know in advance if something will fail.
kOoO wrote: ↑Fri Aug 30, 2019 8:42 am
I understand that for action steps, like clicking, keypressing ... but for loging it's rather exceedingly time consuming than useful .. nothing in the state of the system changes when I log a message, so why to take a screenshot?
The tracing screenshots are bound to logging, not to actions, i.e. if you turn off logging, you will also not have tracing screenshots.
If you do a lot of logging and want better performance, try changing the "Tracing mode" to "Background", which might result into less accurate screenshots (because done in parallel without blocking execution), but should definitely improve speed.
Regards,
Alex
Ranorex Team