Triaged Tester

February 4, 2009

Logging – Do’s & Don’ts

Filed under: Automation,Checklist,Guidelines — Triaged Tester @ 7:22 am
Tags: , ,

Logging is imperative for the successful release of any product. It is required for ensuring that enough test cases are passing and release criteria is being met with. Without proper logging, there is no way of determining, if a component meets the QA needs as prescribed. The logging infrastructure has to be robust.

 Error reporting is one of the crucial aspects of logging required for test cases. Errors, Warnings and informational messages should be context sensitive and be able to point to the source of the problem in the test code. They should also be as much unique as possible so that a result from a wild card search should be able to point the test suite and the test Case the error message belongs to.




  • Use custom logging only in conjunction with logging provided by operations team.
  • Do not log multiple passes/failures per test case.
  • Do not instantiate your own version of the Logging object provided by operations team.
  • No “No repro on rerun” explanations.
  • Do not log a failure in place of warnings. A failing Test caseshould report only one failure.




  • Do use the logging infrastructure provided by the operations team.
  • Do use only one Pass or one Fail per test case.
  • Tests should always log a result per test case.
  • Do Use multiple warnings instead of failures.
  • Log as much information needed for easier troubleshooting.
  • Log the state of your objects for easier troubleshooting.

Leave a Comment »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Blog at

%d bloggers like this: