Forum Discussion

Manfred_F's avatar
Manfred_F
Regular Contributor
8 years ago
Solved

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 goin...
  • Colin_McCrae's avatar
    Colin_McCrae
    8 years ago

    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?

     

    https://support.smartbear.com/viewarticle/80695/

     

    You can switch it on and off during runs ....

tristaanogre's avatar
tristaanogre
Esteemed Contributor

Question: Do you always need to have the visualizer log images to your log file? In my experience, only in cases where I'm trying to see what went wrong do I need those images. So, it might be to your advantage to simply turn off the visualizer for your regular runs but then turn it back on temporarily for your "debugging" runs.

Manfred_F's avatar
Manfred_F
Regular Contributor
8 years ago

well, turning off Visualizer Image capturing during test run does reduce the amount of disk space used by more than 90%.

 

But it leaves me sort of blind with the log. I have to trust in the pure text info, I only get Pictures from log.Warning, .Error, .Message.

In case of Problems, I'd have to repeat the test with Pictures enabled - but - will the Problems Show again?

 

I would prefer other Approaches.

Is it possible to do post-processing of the log, e. g. iterate the items and delete the Picture for any item "The window got Focus"? This would reduce the disk space used by Pictures by 25%.

One idea was to simply suppress unwanted Log Events by Event handling, but if I do so, TC 11 messes up the Picture sequence.

  • Colin_McCrae's avatar
    Colin_McCrae
    Community Hero
    8 years ago

    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?

     

    https://support.smartbear.com/viewarticle/80695/

     

    You can switch it on and off during runs ....

    • Manfred_F's avatar
      Manfred_F
      Regular Contributor
      8 years ago

      Yes, I also do my own logging with some very useful Features.

      I write own log items, and I intercept TCs logging to Change or suppress Information.

      Turning off Visualizer could be an Option, but I doubt that it will makt the direct hits..

      I ' ll give it a try.

      But what about log postprocessing?

      • Colin_McCrae's avatar
        Colin_McCrae
        Community Hero
        8 years ago

        "But what about log postprocessing?"

         

        No idea I'm afraid. I don't use the built in log for anything except occasional debugging.