Comments for Slackhacker

Comment on Testing logging behaviour in four code lines flat by www.seoorganics.net/

www.seoorganics.net/ — Tue, 07 May 2013 12:01:05 +0000

Hi! I know this is somewhat off topic but I was
wondering which blog platform are you using for this website?

I’m getting fed up of WordPress because I’ve had
problems with hackers and I’m looking at alternatives for another platform. I would be great if you could point me in the direction of a good platform.

Comment on Restoring PC keyboard sanity on OS X by Mass Effect 3 Key Generator

Mass Effect 3 Key Generator — Thu, 02 May 2013 17:20:34 +0000

What a information of un-ambiguity and preserveness of valuable
knowledge concerning unexpected feelings.

Comment on Restoring PC keyboard sanity on OS X by istappar

istappar — Mon, 22 Apr 2013 14:20:03 +0000

It doesn’t work on 10.5.8.

Comment on Review: Agile Project Management with Scrum by Wrike.com

Wrike.com — Fri, 21 Sep 2012 08:17:35 +0000

Speaking of Scrum, I am interested in open source information ( i.e. list of tools, features, specifications). Where can I find it?

Comment on Review: Agile Project Management with Scrum by justin

justin — Thu, 20 Sep 2012 19:56:51 +0000

Somebody essentially assist to make critically posts I would state. That is the very first time I frequented your web page and thus far? I amazed with the analysis you made to make this particular put up incredible. Great activity!

Comment 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.

Comment on Testing logging behaviour sans Mockito 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!

Comment on Testing logging behaviour sans Mockito 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).

Comment on Testing logging behaviour sans Mockito 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 [...]

Comment on Testing logging behaviour in four code lines flat by Testing logging behaviour sans Mockito « Slackhacker

Testing logging behaviour sans Mockito « Slackhacker — Mon, 16 Apr 2012 21:54:25 +0000

[...] most popular post in this somewhat dormant blog is Testing logging behaviour in four code lines flat. The approach described there relies on everyones favourite unit testing mocking swiss army knife [...]