log pictures eat my disk space
longtime test runs generate large logs with lots of Pictures.
In my case, a 15h-run generates >2GB of data, most of it consisting of screenshots.
I do Need the screenshots to prove what was going on, but: do they Need to consume that much disk space?
For me, it would be sufficient to have the Event Pictures automatically generated by TC in a lower Quality. Less Color, less Resolution would not be a Problem.
Events logging control Actions such as button click or window getting focus could be logged with a Picture just showing a sector around the control, e. g. 5*5 cm instead of the full Dialog or screen. This would also reduce size.
My own logged Pictures (via script) shall have the full Quality.
What about a new Event type to intercept Picture logging? With the logged control as context and the ability to Clip a part of the Picture around the red Frame and the ability to reduce Quality and storage space?
What do You mean?
I have the visualiser switched off as well.
There are a few areas in my scripts where screen caps are occasionally useful. So I have my own code in there and a toggle to enable/disable caps during a run.
But then, I also use my own custom log file with WAY more descriptive text in it. That allows me to isolate problems down to a single test step (user driven keyword + data driven framework) which I can re-run in isolation easily enough. So screen caps aren't essential very often at all.
You could try isolating it down so that it's only enabled in areas you know you'll find it useful?
You can switch it on and off during runs ....