I do have visualizer turned off. And there were only 8 errors, so there were only a few images for those errors. As for the events, I had considered that, but I hesitate to remove useful debug info like that should something go wrong. In conjunction with testing a large number of individual test cases we are also using the long test to test performance and memory leaks over time, so having the events in the log has proved useful, and given the runtime of the test, we don't necessarily have the resources to simply turn the events back on and rerun when something does fail. And only saving the last x number of events before an error hasn't always proved sufficient either.
But thank you for the response.
cshukusky wrote:
As for the events, I had considered that, but I hesitate to remove useful debug info like that should something go wrong. I
This is why the following option exists under Tools -> Current Project Properties -> Playback:
Basically, what this does is will "lock" the events on the project so they won't write out to the log for every click or keystroke. However, whenever a warning or error is logged, the last X number of events preceeding that warning or error are logged. This provides the desired debug info to determine why the warning/error appeared. If there are no warnings or errors, there are no events in the log.
