Manfred_F
9 years agoRegular Contributor
log postprocessing
does anybody use log postprocessing?
- remove unwanted entries?
- remove unnecessary Pictures?
- some clever comparison with previous results?
- ...?
does anybody use log postprocessing?
- remove unwanted entries?
- remove unnecessary Pictures?
- some clever comparison with previous results?
- ...?
For the pictures, I would just turn them off in the project properties until the time comes that you need them for debugging.
What other unwanted entries are there?
There are lots of entrries in the log useless for me. An example are the "The window got Focus" Events, but also others
I do use Event handling to get the log I want.
So I could suppress anything I do not really want to have by Event processing, even Pictures. I also take TC Event items and put in my application data there as controltype and caption.
The Problem is, that TC 11 messes up the Picture logging sequence when I apply my test libraries. The Support was not able to reproduce the error, and I was not allowed to let them have our application.
The test libraries are based on ODT.
As a Workaround, when I Keep the unwanted Event items, the Picture sequence is resynched again.
So, I can't turn off the Picture logging. :-(
You Can try this. it may help you.
log.LockEvents 
' here is your statements which is generate log like - Window got focus/Window was click/Keyboard input
log.UnlockEvents