Comments on: Testing logging behaviour sans Mockito

By: pveentjer

pveentjer — Wed, 18 Apr 2012 07:03:25 +0000

Even for the log levels warn and higher, I would ask myself the question at least 2 times if some form of testing is really needed to verify that the exception is logged.

By: slackhack

slackhack — Tue, 17 Apr 2012 21:11:40 +0000

I think the main problem in the context of this post is that many applications log to much (and on a far too high severity level). Logging on WARNING level (and above) should only be applied to actionable events that are likely to warrant immediate attention, e.g uncaught runtime exceptions (i.e. probable software defects), possible malicious user activity, integration point down time etc. Failure to log such events constitutes a significant risk to a production system and could render attempts to reproduce bug reports impossible. Hence – log less but when you do log, make sure (test!) that it’s really done!

By: pveentjer

pveentjer — Tue, 17 Apr 2012 13:23:54 +0000

Some things should not be tested and one of those things is logging.

Too much testing can slow you down on the short term, because you need to spend more resourced on writing tests instead of realizing value that is important to the business.

But it can also be damaging on the long term, because refactoring lead to a lot of changes in the tests, making them a drain on your resources instead of an asset.

My personal believe is that mocking frameworks are being overused in a lot of company. Focus more on writing integration tests to see that the system really works instead of a lot of lower level unit tests (relying on mocking).

By: Testing logging behaviour in four code lines flat « Slackhacker

Testing logging behaviour in four code lines flat « Slackhacker — Mon, 16 Apr 2012 22:03:48 +0000

[...] on April 16, 2012 at 22:54 | Reply Testing logging behaviour sans Mockito « Slackhacker [...]