Forum Discussion

Aurore's avatar
Aurore
New Contributor
5 years ago

Log functions

Hello,   Can we define another Log function than existing ones (Checkpoint, Error, Event, Message and Warning) which could be displayed in Test results ?   Aurore
Log class
TechCorner
Test Results
TestComplete facilities
Visualizer
  • Aurore's avatar
    Aurore
    5 years ago

    Thanks for the fast response.

    What we need is a way to log the failure of some steps of the functions with a special marking like "Requirement Failure" which can be filtered out in the log. Today the available functions are mixed with checkpoints, messages etc.. and we are looking for ways to mark specific steps as in a different way in the log than marking them in one of the available categories.
     
  • tristaanogre's avatar
    tristaanogre
    5 years ago

    You can still use Log.Message, Log.Warning, or Log.Error for that.  What you would need to do, though, to distinguish it is change the Log Attributes of your message.  Things like priority, color, etc., will make those items stand out.

     

    As a tester, I would use Log.Warning to warn that, while the automation completed, there was something that was incorrect in the completion.  The fourth parameter in the Log.Warning method is where you would pass in a LogAttributes object with the different settings.  You can also set the priority (3rd parameter) to distinguish it from other warnings.

tristaanogre's avatar
tristaanogre
Esteemed Contributor

No.  Log is an object in TestComplete and is not something that you can alter to add additional functions.  TestComplete does not allow for modification of such objects.

 

What do you need in the way of logging that is not provided?  What are you wanting to achieve in an output?  Perhaps there are ways of doing what you want that don't involve creating new log functions.

Aurore's avatar
Aurore
New Contributor
5 years ago

Thanks for the fast response.

What we need is a way to log the failure of some steps of the functions with a special marking like "Requirement Failure" which can be filtered out in the log. Today the available functions are mixed with checkpoints, messages etc.. and we are looking for ways to mark specific steps as in a different way in the log than marking them in one of the available categories.
 
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    5 years ago

    You can still use Log.Message, Log.Warning, or Log.Error for that.  What you would need to do, though, to distinguish it is change the Log Attributes of your message.  Things like priority, color, etc., will make those items stand out.

     

    As a tester, I would use Log.Warning to warn that, while the automation completed, there was something that was incorrect in the completion.  The fourth parameter in the Log.Warning method is where you would pass in a LogAttributes object with the different settings.  You can also set the priority (3rd parameter) to distinguish it from other warnings.