If we expect our tests to act as a documentation then we need to put some effort into their readability.

Recently my team is moving towards Big Data (or rather it is data coming at us with the speed of light), and this is how we learned about brontobytes. This brought some associations with dinosaurs (not very creative, I know). During some boring meeting ;) I tried to visualize a brontobyte.

For unit tests a rule of thumb is to keep them independent from each other. It is not so bad if we introduce a dependency on purpose (and explicitly declare it e.g. using TestNG dependsOnMethod feature). A worse scenario is when we are not aware of the dependency ourselves. This can bring serious problems on our heads.

Code reviews. Very helpful if done right, completely useless if done recklessly.

This post is a dump of my "stream of conscious" (or to put it differently - my emotional mumblings) about the way we waste our time writing clickable GUI tools to run testing scenarios so we can verify the correctness of the software we write.

Recently I was happy to see some new ideas discussed on Mockito and TestNG mailing lists. It is always nice to see plans for improvement, especially in such mature and features-rich projects.

This is a continuation of my mumblings about useful Jenkins plugins (see previous posts here and here). As we progress towards continuous delivery I learn a lot about new plugins.

This is a continuation of my mumblings about useful Jenkins plugins (see the first post here: http://kaczanowscy.pl/tomek/2012-05/recommended-jenkins-plugins). As we progress towards continuous delivery I learn a lot about new plugins.

My relation from Confitura 2012 event.

No fluff, just stuff, so let us get to the point. And the point is, that there were many really good talks this year!

Some comments I'd like to share with you after self-publishing my book Practical Unit Testing with TestNG and Mockito.