Configure Test Log to see only failures

[nisgupta]

Can We configure the TestComplete in such a manner that after running the project suite we only wan to see the Test Log which has failure only ?

Please update 

Thanks

Nishchal

[Marsha_R]

You can use this setting to limit the number of posts to the log.  I would suggest keeping at least 2 or 3 before an error for troubleshooting purposes.

https://support.smartbear.com/testcomplete/docs/working-with/managing-projects/properties/playback.h...

Store last … events - Specifies the number of the last event messages that must be posted to the test log before an error message is posted to the log. 0 means that all event messages must be stored.

Use this option to remove unnecessary event messages from the log and reduce its overall size.

[nisgupta]

@Marsha_R 

Thanks for the updates .

How about the Log Option Under the Engines as attached the ss ?

Thanks

Nishchal

[Marsha_R]

What about it?  I don't understand your question.

[nisgupta]

In this Log option if we uncheck the store all log and put Number of recent logs to Keep as 5 , will reduce the size of test log ?

Also the Playback that was mentioned also applies to the tests under CrossbrowserTesting?

Thanks

Nishchal

[Marsha_R]

No, as it says, it will reduce the *number* of test logs that TC saves at one time.  

The best thing to do is change some of the log settings and run your tests and see if the result is what you want and adjust things from there.

[tristaanogre]

The number of logs to store doesn't have to do with the types of messages but the "history" of test runs to keep.

Basically... you control what gets written to the log.  If you don't want it in the log, don't write it out to the log.  This is actually a practice that I encourage in my team.  If the log doesn't say anything, assume it passed.  Only if a Warning or Error appears do we have to worry about anything. 

[nisgupta]

thanks @Marsha_R and @tristaanogre 

There are only 4 scripts but we are running on different OS and the last 3 version of browsers So total tests reach almost 150. I want the MHT report uploaded to our wiki style page . Out Wiki which is confluence has the max size limit 100 MB. MHT report is almost 200 MB.

For e.g.

Window 10 

     FF 64 bit - latest 3 versions 

     FF 32 bit lastest 3 versions

     Chrome 64 bit - latest 3 versions

     Chrome 32 bit  - latest 3 versions

     Edge - 18, 17, 16

Window 7 64-bit

     FF 64 bit - latest 3 versions 

     FF 32 bit lastest 3 versions

     Chrome 64 bit - latest 3 versions

     Chrome 32 bit  - latest 3 versions

Window 8.1     

 FF 64 bit - latest 3 versions 

     FF 32 bit lastest 3 versions

     Chrome 64 bit - latest 3 versions

     Chrome 32 bit  - latest 3 versions

We are looking for ways how we can have the size of MHT report less than 100 MB .

Thanks

Nishchal

[Marsha_R]

You can use the setting that I mentioned at the very top of this thread.  It will limit the entries to the log that are just comments that you really only need when you have an error.  That will cut the file size down, but I don't know if it will be as much as you want.

If you go and try the things that @tristaanogre and I have suggested, it will give you a better idea of what is possible.  We can't tell you exactly how it is going to work because we don't know your tests.  You are the best judge of that.  Try it and let us know what happens.  

[tristaanogre]

Really, it comes down to how much you're logging and what you're logging.  The size of the MHT file is determine, entirely, but what the log contains.  @Marsha_R will reduce the number of "Event" logs that are automatically generated when you "click" or "keys" or such things.  There is a setting to determine if you're going to take a screenshot when an error is generated.  If you turn that off, that will reduce the log by some size.  

If you are using a lot of Log.Message or Checkpoints or things like that, they will be written to the log all the time.  It you really want to reduce your log size, then you should go through your project and remove any unnecessary logging.